- Level
- confirmed
- Worst impact
- Degraded
- Components
- Managed Network
- Down Index
- 9of 100
What to do
Check whether you use Deno Deploy Managed 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 0m it lasted.
Anything that failed between 2026-05-07 10:20 UTC and 2026-05-07 10:20 UTC may need a replay.Subscribe to Deno Deploy's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=deno-deploy works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Deno Deploy 1
- resolved
Type: Incident Duration: 4 hours and 10 minutes Affected Components: Managed Network May 7, 14:30:00 GMT+0 - Resolved - This incident has been resolved. It was caused by some networking changes being rolled out that caused peering instability. May 7, 10:20:00 GMT+0 - Investigating - Some requests failed to be served with 500 errors and a NO\_VALID\_CLUSTER error message.
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-b40b310bc6
Is Deno Deploy still down?
No, this incident was resolved 2026-05-07 10:20 UTC. For Deno Deploy's live state, see https://down.guide/deno-deploy.
How long did it last?
0m, from 2026-05-07 10:20 UTC to 2026-05-07 10:20 UTC, by the times Deno Deploy posted.
What was affected?
Deno Deploy named Managed Network.
What caused it?
Deno Deploy hasn't published a root cause. If it does, it shows here.
Where does this come from?
Deno Deploy's official status page, https://denostatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.