Deno Deploy is down in Chicago

What to do

• Check whether you use Deno Deploy in eu. 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-01-30 08:10 UTC and 2026-01-30 08:10 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. resolvedJan 30, 2026, 8:10 AM UTC

   Type: Incident Duration: 6 hours and 3 minutes Jan 30, 14:13:24 GMT+0 - Resolved - This incident has been resolved. Jan 30, 09:59:33 GMT+0 - Monitoring - The Chicago datacenter is back in operation, and the managed network is serving from there again. The console has recovered, and write operations are succeeding again. Jan 30, 09:32:45 GMT+0 - Identified - We have now stabilized the managed network - all traffic is now being routed away from our Chicago datacenter, to healthy datacenters. We are continuing to see (build) failures on the console. Jan 30, 08:10:00 GMT+0 - Identified - The managed network is down in Chicago. We are seeing most requests fall back to Amsterdam, as expected. The majority of write calls to the console are currently timing out or failing. Builds are currently stuck in the "Queued" step.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.