Skip to main content
Deno Deploy

Degraded performance on Deno Deploy

Degraded Lasted 0m · started · Deno Deploy's page

Level
confirmed
Worst impact
Degraded
Components
deno.land/std import, Console, deno.land/x import, cdn.deno.land, deno.land, deno.com, Managed Network
Regions
eu
Down Index
15of 100

What to do

  • Check whether you use Deno Deploy deno.land/std import, Console, deno.land/x import, cdn.deno.land and 3 more 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-04-24 21:32 UTC and 2026-04-24 21:32 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 2 minutes Affected Components: deno.land/std import, Console, deno.land/x import, cdn.deno.land, deno.land, deno.com, Managed Network Apr 24, 23:35:00 GMT+0 - Resolved - This incident has been resolved. Apr 24, 21:54:27 GMT+0 - Monitoring - The storage connectivity issue in our Chicago (ord) region has resolved. Traffic has been restored to ord and requests are being served normally. Builds are operational. We are monitoring the cluster for any remaining issues. Apr 24, 21:41:54 GMT+0 - Identified - We have identified the issue as a storage connectivity problem in our Chicago (ord) region. Traffic has been rerouted to our Amsterdam (ams) region and requests are now being served successfully. Builds may still be affected. We are continuing to work with our infrastructure provider on the underlying issue. Apr 24, 21:32:34 GMT+0 - Investigating - We are investigating degraded performance affecting Deno Deploy. Some deployments routed through our Chicago (ord) region are experiencing boot failures and elevated error rates due to an upstream storage connectivity issue. Deployments served by other regions are unaffected. We are working with our infrastructure provider to resolve the issue and will post updates as they become available.

    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-0a6033d9bf

Is Deno Deploy still down?

No, this incident was resolved 2026-04-24 21:32 UTC. For Deno Deploy's live state, see https://down.guide/deno-deploy.

How long did it last?

0m, from 2026-04-24 21:32 UTC to 2026-04-24 21:32 UTC, by the times Deno Deploy posted.

What was affected?

Deno Deploy named deno.land/std import, Console, deno.land/x import, cdn.deno.land and 3 more in eu.

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.