Site: finbound.org (site ID b8c7a11e-5b16-425c-93ef-0ea9ecbe6498), also finbound.netlify.app. Next.js 16 via @netlify/plugin-nextjs@5.14.5. Functions region lhr.
Since ~06:00 UTC today, every request routed through the edge function returns “this edge function has crashed”:
uncaught exception during edge function invocation
HTTP 500 on IPv4 and IPv6. Same result for /, /blog, /favicon.ico, /.netlify/functions/*, and Identity. Apex finbound.org still 301s to www.
Measured against the eu-central / Frankfurt endpoints:
35.157.26.135→ 50063.176.8.218→ 5002a05:d014:58f:6200::258→ 5002a05:d014:58f:6200::259→ 500
Already tried, no effect: same-commit rebuild (6a7d74a9fff3cdd06c74d8f8, published 07:43 UTC) and hitting older deploys, including 2026-08-11 6a7b5a658c0b3b00081fc457 and yesterday 11:00 UTC 6a7c518419ee920008fe48ef. GA still had pageviews after last night’s deploys until 05:59 UTC. The Netlify deploy screenshot for the retry shows a healthy homepage, so some of the network can still render it.
Request IDs:
01KZX1WE6PN1K0TYW837RQVWN101KZX1WEP8BB39QYXT76QF5RFP01KZX1WET8VNAGNJE7Z61E39GB
netlifystatus.com shows no active incident. Looks like the same eu-central Next.js 16 edge crash as All edge function invocations return 502/"edge function has crashed" on IPv4 edge endpoints same deploy healthy over IPv6 (eu-central) , except both IPv4 and IPv6 fail here.
Edge logs aren’t loading in dashboard.