- Level
- confirmed
- Worst impact
- Degraded
- Components
- API, GitHub Integration
- Down Index
- 10of 100
What to do
Check whether you use Deno Deploy API, GitHub Integration. 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-26 00:15 UTC and 2026-01-26 00:15 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
- resolved
Type: Incident Duration: 1 day, 22 hours and 9 minutes Affected Components: API, GitHub Integration Jan 27, 22:24:07 GMT+0 - Resolved - This incident has been resolved. Jan 26, 08:28:58 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jan 26, 00:15:00 GMT+0 - Investigating - We are currently investigating this incident.
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-c7209ee005
Is Deno Deploy still down?
No, this incident was resolved 2026-01-26 00:15 UTC. For Deno Deploy's live state, see https://down.guide/deno-deploy.
How long did it last?
0m, from 2026-01-26 00:15 UTC to 2026-01-26 00:15 UTC, by the times Deno Deploy posted.
What was affected?
Deno Deploy named API, GitHub Integration.
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.