Skip to main content
Deno Deploy

Deno Deploy Deployment Failures

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

Level
confirmed
Worst impact
Degraded
Components
Console
Down Index
9of 100

What to do

  • Check whether you use Deno Deploy Console. 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 2025-11-08 18:00 UTC and 2025-11-08 18:00 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: 1 day, 15 hours and 59 minutes Affected Components: Console Nov 10, 09:59:11 GMT+0 - Resolved - This incident has been resolved. Nov 8, 18:00:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.

    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-2808f4534e

Is Deno Deploy still down?

No, this incident was resolved 2025-11-08 18:00 UTC. For Deno Deploy's live state, see https://down.guide/deno-deploy.

How long did it last?

0m, from 2025-11-08 18:00 UTC to 2025-11-08 18:00 UTC, by the times Deno Deploy posted.

What was affected?

Deno Deploy named Console.

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.