Site: yontaworks.com (site ID c1f62198-7bca-41ef-9f7b-f1318c48be0f),
also yontaworks.netlify.app. Next.js 16 via @netlify/plugin-nextjs
(middleware runs as an edge function).
Since 2026-07-17, every page routed through the edge function returns
“this edge function has crashed” (HTTP 502) — but only when the request
lands on the IPv4 edge endpoints. Measured with 10 fresh connections per
endpoint, same deploy:
63.176.8.218 → 0/10 success (all 502)
35.157.26.135 → 0/10 success (all 502)
2a05:d014:58f:6200::258 → 10/10 success
2a05:d014:58f:6200::259 → 8/10 success
On the same failing IPv4 endpoint, matcher-excluded paths
(/robots.txt, /favicon.ico) return 200 — CDN/static serving is healthy;
only edge-function invocation fails.
Already tried, no effect (expected, since the same deploy works over
IPv6): CI redeploy, CLI redeploy, restoring a previously-healthy deploy,
removing and re-adding the custom domain. We enabled IPv6 on the domain
as partial mitigation, but IPv4-selecting clients still get 502 on every
page.
Request IDs from crashed responses:
01KXTJ0Z0WW5D1RYK8KMT6W1K1
01KXTJY3DX796EWRCF7TJB07SB
01KXTM5XVJK9CZ3QEFTYK5AM5E
netlifystatus.com shows no active incident. Could you check the
edge-function runtime on the IPv4 load-balancer pool serving our site
(eu-central / AWS Frankfurt IPs)?