Netlify: Increased errors for Edge Functions on Standard Edge Network
Timeline of updates
- resolved
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.
From Netlify’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.netlifystatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Netlify, started 2026-03-10 16:43 UTC, resolved after 0 min, 1 update(s).
- Title
- Increased errors for Edge Functions on Standard Edge Network
- Vendor
- Netlify
- Date
- URL
- https://rewindex.com/company/netlify/incidents/21c4nsgh0hg1
Netlify profileRecent Netlify incidentsAll outages on March 10, 2026Netlify in March 2026MarkdownJSON