- Level
- confirmed
- Worst impact
- Degraded
- Components
- High-Performance Edge Network, Standard Edge Network, Agent Runners
- Down Index
- 18of 100
What to do
Check whether you use Netlify High-Performance Edge Network, Standard Edge Network, Agent Runners. 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 1h 2m it lasted.
Anything that failed between 2026-03-24 00:30 UTC and 2026-03-24 01:32 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 2
- monitoring
We experienced an increased number of delayed cache purges on both the Standard and HP Edge Networks between 22:30 and 0:10 UTC. We have deployed a fix and are currently 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-572a05f93a
Is Netlify still down?
No, this incident was resolved 2026-03-24 01:32 UTC. For Netlify's live state, see https://down.guide/netlify.
How long did it last?
1h 2m, from 2026-03-24 00:30 UTC to 2026-03-24 01:32 UTC, by the times Netlify posted.
What was affected?
Netlify named High-Performance Edge Network, Standard Edge Network, Agent Runners.
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.