- Level
- confirmed
- Worst impact
- Maintenance
- Components
- Console
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.Check that everything you run on Deno Deploy came back after the window closed 2025-10-20 12:30 UTC.
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: Maintenance Duration: 2 hours Affected Components: Console Oct 20, 14:30:00 GMT+0 - Completed - Maintenance has completed successfully Oct 20, 12:30:01 GMT+0 - Identified - Maintenance is now in progress Oct 20, 12:30:00 GMT+0 - Identified - We are working to upgrade our managed network. As part of the preparatory work for this, some write operations such as creating an organization, creating or updating an app, or starting a new deployment may take longer than usual. Traffic on the managed network will continue to be served as normal.
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-cb725240d3
Is this Deno Deploy maintenance still going on?
No, it ended 2025-10-20 12:30 UTC.
How long did it last?
0m, from 2025-10-20 12:30 UTC to 2025-10-20 12:30 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.