Deno Deploy Outage History

There were 3 Deno Deploy outages since February 27, 2026 totaling 2h 2m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://denostatus.com

Major April 24, 2026

Degraded performance on Deno Deploy

Detected by Pingoru: Apr 24, 2026, 09:32 PM UTC
Resolved: Apr 24, 2026, 11:35 PM UTC
Duration: 2h 2m

Affected: DenoDeno Deploy (Console)Deno Deploy (Managed Network)Module Registry (cdn.deno.land)Module Registry (deno.land/std import)Websites (deno.land)Module Registry (deno.land/x import)Websites (deno.com)

Timeline · 4 updates

investigating Apr 24, 2026, 09:32 PM UTC

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.
identified Apr 24, 2026, 09:41 PM UTC

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.
monitoring Apr 24, 2026, 09:54 PM UTC

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.
resolved Apr 24, 2026, 11:35 PM UTC

This incident has been resolved.

Read the full incident report →

Minor April 24, 2026

New builds might take longer to start serving traffic

Detected by Pingoru: Apr 24, 2026, 10:00 AM UTC
Resolved: Apr 24, 2026, 10:00 AM UTC
Duration: —

Timeline · 1 update

resolved Apr 24, 2026, 10:00 AM UTC

Type: Incident Duration: 3 days, 2 hours and 24 minutes Affected Components: Console, Managed Network 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. Apr 27, 12:23:32 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor February 27, 2026

Deno Deploy deployments, app creations, org creations seeing increased error rate

Detected by Pingoru: Feb 27, 2026, 04:27 PM UTC
Resolved: Feb 27, 2026, 04:27 PM UTC
Duration: —

Timeline · 1 update

resolved Feb 27, 2026, 04:27 PM UTC

Type: Incident Duration: 1 hour and 33 minutes Affected Components: Console Feb 27, 16:27:14 GMT+0 - Investigating - We are seeing increased error rates for deployments, app creations, organizations creations, and various other write operations on Deno Deploy, both through the console at https://console.deno.com, and through `deno deploy`. Running of existing deployed applications, and starting of sandboxes is not affected. Feb 27, 16:46:37 GMT+0 - Identified - We have applied a preliminary fix for the underlying trigger of this issue and are monitoring the results. The job backlog, particularly for deployments will take some time to clear up. Feb 27, 17:12:44 GMT+0 - Monitoring - The job queues are back to normal. We are still monitoring. Feb 27, 18:00:00 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Looking to track Deno Deploy downtime and outages?

Pingoru polls Deno Deploy's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

Real-time alerts when Deno Deploy reports an incident
Email, Slack, Discord, Microsoft Teams, and webhook notifications
Track Deno Deploy alongside 5,000+ providers in one dashboard
Component-level filtering
Notification groups + maintenance calendar

Start monitoring Deno Deploy for free

5 free monitors · No credit card required