Deno Deploy incident

Degraded performance on Deno Deploy

Major Resolved

Deno Deploy experienced a major incident on April 24, 2026 affecting Deno and Deno Deploy (Console) and 1 more component, lasting 2h 2m. The incident has been resolved; the full update timeline is below.

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

Affected components

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)

Update timeline

  1. 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.

  2. 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.

  3. 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.

  4. resolved Apr 24, 2026, 11:35 PM UTC

    This incident has been resolved.