Incidentsby GlyphIncreased errors for Edge Functions on Standard Edge Network
Mar 10, 16:43 UTCMar 10, 16:43 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
Netlify, 90 days
20 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 historyElevated build and deploy failureslasted 6mDelays in build logs appearing in the UIlasted 8h 57mElevated Build Errors and Agent Runner failureslasted 57mDelays in build logs appearing in the UIlasted 11h 16mDelayed Edge Functions and Functions logslasted 3h 51mDelays in build logs appearing in the UIlasted 22h 26m