Skip to main content
Deno Deploy

Deno Deploy Chicago cluster outage

Major outage Lasted 0m · started · Deno Deploy's page

Level
confirmed
Worst impact
Major outage
Components
Managed Network, deno.land, deno.com

What to do

  • Check whether you use Deno Deploy Managed Network, deno.land, 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-03 00:07 UTC and 2026-07-03 00:07 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

  1. resolved

    Type: Incident Duration: 2 hours and 53 minutes Affected Components: Managed Network, deno.land, deno.com Jul 3, 03:00:06 GMT+0 - Resolved - The incident has been resolved. deno.com, deno.land, and Deno Deploy managed network traffic have recovered and we are no longer seeing impact. Jul 3, 00:53:15 GMT+0 - Monitoring - The infrastructure problem at one of our cloud providers has been mitigated, and affected services are recovering. We are monitoring for any remaining issues. Jul 3, 00:34:39 GMT+0 - Identified - We have identified the cause as an infrastructure problem at one of our cloud providers. deno.com, deno.land, and Deno Deploy managed network traffic remain impacted while recovery work continues. Jul 3, 00:23:08 GMT+0 - Investigating - We are continuing to investigate a major outage affecting deno.com, deno.land, and Deno Deploy managed network traffic. Builds triggered via GitHub integration, CLI, or API may also fail because builds run in Chicago. Sandbox creation in Chicago may also fail. Jul 3, 00:07:00 GMT+0 - Investigating - Starting around 00:07 UTC, the Deno Deploy Chicago cluster is unreachable. This affects 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 may be affected as well. The Deno Deploy console remains available, but builds triggered via GitHub integration, CLI, or API may fail because builds run in Chicago. Sandbox creation in Chicago may also fail. We are investigating.

    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-d785d271c2

Is Deno Deploy still down?

No, this incident was resolved 2026-07-03 00:07 UTC. For Deno Deploy's live state, see https://down.guide/deno-deploy.

How long did it last?

0m, from 2026-07-03 00:07 UTC to 2026-07-03 00:07 UTC, by the times Deno Deploy posted.

What was affected?

Deno Deploy named Managed Network, deno.land, 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.