Deno Deploy incident

Degraded performance on Deno Deploy

Minor Resolved View vendor source →

Deno Deploy experienced a minor incident on April 24, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Apr 24, 2026, 09:32 PM UTC
Resolved
Apr 24, 2026, 09:32 PM UTC
Duration
Detected by Pingoru
Apr 24, 2026, 09:32 PM UTC

Update timeline

  1. resolved Apr 24, 2026, 09:32 PM UTC

    Type: Incident Duration: 2 hours and 2 minutes Affected Components: deno.land/std import, Console, deno.land/x import, cdn.deno.land, deno.land, deno.com, Managed Network Apr 24, 21:32:34 GMT+0 - Investigating - 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. Apr 24, 21:41:54 GMT+0 - Identified - 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. Apr 24, 21:54:27 GMT+0 - Monitoring - 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. Apr 24, 23:35:00 GMT+0 - Resolved - This incident has been resolved.