Deno Deploy: New builds might take longer to start serving traffic

What to do

Check whether you use Deno Deploy Console, Managed Network. 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 10:00 UTC and 2026-04-24 10: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.

resolvedApr 24, 2026, 10:00 AM UTC
Type: Incident Duration: 3 days, 2 hours and 24 minutes Affected Components: Console, Managed Network Apr 27, 12:23:32 GMT+0 - Resolved - This incident has been resolved. Apr 24, 10:00:00 GMT+0 - Identified - Users are experiencing that new builds are not immediately serving traffic after deployment and that traffic continues being served by the previous build. We're currently working on a fix for this issue.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Deno Deploy still down?

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

How long did it last?

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

What was affected?

Deno Deploy named Console, Managed Network.

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.