Increased errors for Edge Functions on Standard Edge Network
Mar 10, 17:18 UTCMar 10, 16:43 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
Netlify, 90 days
11 incidents
Affected
Not listed by the vendor.
Final update
From 16:43 UTC to 16:58 UTC, we served HTTP 500 for paths invoking Edge Functions (including framework-generated ones like Next.js Middleware/Proxy). This affected the Free/Starter as well as some part of the Pro tier users on the Standard Edge Network. The issue has since been resolved.
Timeline
- Resolved · Mar 10, 16:43 UTC
From 16:43 UTC to 16:58 UTC, we served HTTP 500 for paths invoking Edge Functions (including framework-generated ones like Next.js Middleware/Proxy). This affected the Free/Starter as well as some part of the Pro tier users on the Standard Edge Network. The issue has since been resolved.
More from Netlify
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2419:01 UTC | Error accessing Netlify-hosted sites | major | 24m |
| Sep 2323:26 UTC | Elevated CDN Errors | minor | 34m |
| Sep 2115:12 UTC | Errors accessing Netlify-hosted sites | major | 1h 25m |
| Sep 1612:58 UTC | Elevated Image CDN Errors | minor | 51m |
| Sep 818:32 UTC | Elevated Errors and Latency in IAD Region | none | 0m |
| Sep 410:57 UTC | Increased errors on High Performance Edge Network - FRA Region | minor | 0m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.