- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Netlify. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-03-10 17:18 UTC and 2026-03-10 16:43 UTC may need a replay.Subscribe to Netlify's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=netlify works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Netlify 1
- 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-6404bbbe30
Is Netlify still down?
No, this incident was resolved 2026-03-10 16:43 UTC. For Netlify's live state, see https://down.guide/netlify.
How long did it last?
0m, from 2026-03-10 17:18 UTC to 2026-03-10 16:43 UTC, by the times Netlify posted.
What caused it?
Netlify hasn't published a root cause. If it does, it shows here.
Where does this come from?
Netlify's official status page, https://www.netlifystatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.