- Level
- confirmed
- Worst impact
- Degraded
- Components
- Standard Edge Network
- Down Index
- 20of 100
What to do
Check whether you use Netlify Standard Edge Network. 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 2h 36m it lasted.
Anything that failed between 2026-05-15 16:23 UTC and 2026-05-15 18:58 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 3
- identified
We are currently experiencing a delay in cache purges, and some sites on our Standard Edge Network may be serving stale content. The issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented, and we are monitoring the results.
provider
- resolved
This incident has 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-a2ff530dd8
Is Netlify still down?
No, this incident was resolved 2026-05-15 18:58 UTC. For Netlify's live state, see https://down.guide/netlify.
How long did it last?
2h 36m, from 2026-05-15 16:23 UTC to 2026-05-15 18:58 UTC, by the times Netlify posted.
What was affected?
Netlify named Standard Edge Network.
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.