- Level
- confirmed
- Worst impact
- Partial outage
- Components
- deno.land, Managed Network, deno.com
What to do
Check whether you use Deno Deploy deno.land, Managed Network, deno.com. 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-07-01 16:25 UTC and 2026-07-01 16:25 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: 50 minutes Affected Components: deno.land, Managed Network, deno.com Jul 1, 17:15:00 GMT+0 - Monitoring - The Chicago cluster outage was resolved around 10:15 PDT and affected services have recovered. We are continuing to monitor. Jul 1, 17:15:00 GMT+0 - Resolved - This incident has been resolved. Jul 1, 16:25:00 GMT+0 - Investigating - Starting around 09:25 PDT, the Deno Deploy Chicago cluster experienced an outage. This affected the Deno Deploy managed edge network for visitors routed through that region, impacting a significant portion of global traffic. Because deno.land and deno.com are hosted on Deno Deploy, they were affected as well. The Deno Deploy console remained available, but builds triggered via GitHub integration, CLI, or API were failing because builds run in Chicago. Sandbox creation in Chicago was also failing.
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-ccedb9991a
Is Deno Deploy still down?
No, this incident was resolved 2026-07-01 16:25 UTC. For Deno Deploy's live state, see https://down.guide/deno-deploy.
How long did it last?
0m, from 2026-07-01 16:25 UTC to 2026-07-01 16:25 UTC, by the times Deno Deploy posted.
What was affected?
Deno Deploy named deno.land, Managed Network, deno.com.
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.