Deno Deploy Outage History

Deno Deploy degraded View live status →

Deno Deploy had 22 outages in the last 2 years totaling 410h 32m of downtime, averaging 0.9 incidents per month.

There were 22 Deno Deploy outages since September 30, 2025 totaling 410h 32m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: denostatus.com

Major September 7, 2026

Deno Deploy request failures in ord

Detected by Pingoru
Sep 07, 2026, 12:13 PM UTC
Resolved
Sep 07, 2026, 01:22 PM UTC
Duration
1h 8m
Affected: Deno Deploy (Managed Network)
Timeline · 3 updates
  1. investigating Sep 07, 2026, 12:13 PM UTC

    We have identified increased failures in serving requests from our ord region. We are currently investigating this incident.

  2. monitoring Sep 07, 2026, 12:24 PM UTC

    The service is recovered and we are currently monitoring the recovery.

  3. resolved Sep 07, 2026, 01:22 PM UTC

    This incident has been resolved. The root cause was a service incident on one of our datacenter providers.

Read the full incident report →

Major July 3, 2026

Deno Deploy Chicago cluster outage

Detected by Pingoru
Jul 03, 2026, 12:07 AM UTC
Resolved
Jul 03, 2026, 03:00 AM UTC
Duration
2h 53m
Timeline · 5 updates
  1. investigating Jul 03, 2026, 12:07 AM UTC

    Starting around 00:07 UTC, the Deno Deploy Chicago cluster is unreachable. This affects the Deno Deploy managed edge network for visitors routed through that region, impacting a significant portion of global traffic. Because deno.land and deno.com are hosted on Deno Deploy, they may be affected as well. The Deno Deploy console remains available, but builds triggered via GitHub integration, CLI, or API may fail because builds run in Chicago. Sandbox creation in Chicago may also fail. We are investigating..

  2. investigating Jul 03, 2026, 12:23 AM UTC

    We are continuing to investigate a major outage affecting deno.com, deno.land, and Deno Deploy managed network traffic. Builds triggered via GitHub integration, CLI, or API may also fail because builds run in Chicago. Sandbox creation in Chicago may also fail..

  3. identified Jul 03, 2026, 12:34 AM UTC

    We have identified the cause as an infrastructure problem at one of our cloud providers. deno.com, deno.land, and Deno Deploy managed network traffic remain impacted while recovery work continues..

  4. monitoring Jul 03, 2026, 12:53 AM UTC

    The infrastructure problem at one of our cloud providers has been mitigated, and affected services are recovering. We are monitoring for any remaining issues..

  5. resolved Jul 03, 2026, 03:00 AM UTC

    The incident has been resolved. deno.com, deno.land, and Deno Deploy managed network traffic have recovered and we are no longer seeing impact..

Read the full incident report →

Major June 20, 2026

Deno Deploy Outage

Detected by Pingoru
Jun 20, 2026, 09:42 PM UTC
Resolved
Jun 20, 2026, 10:13 PM UTC
Duration
31m
Affected: Deno 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 · 3 updates
  1. investigating Jun 20, 2026, 09:42 PM UTC

    We are currently investigating this incident.

  2. monitoring Jun 20, 2026, 09:59 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Jun 20, 2026, 10:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 15, 2026

Deno Deploy Console - Slow to respond

Detected by Pingoru
Jun 15, 2026, 03:01 PM UTC
Resolved
Jun 15, 2026, 03:15 PM UTC
Duration
13m
Affected: Deno Deploy (Console)
Timeline · 2 updates
  1. investigating Jun 15, 2026, 03:01 PM UTC

    We are currently investigating this incident.

  2. resolved Jun 15, 2026, 03:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 3, 2026

Registering new and renew existing custom domains

Detected by Pingoru
Jun 03, 2026, 09:39 AM UTC
Resolved
Jun 03, 2026, 12:54 PM UTC
Duration
3h 14m
Affected: Deno Deploy (Console)
Timeline · 2 updates
  1. identified Jun 03, 2026, 09:39 AM UTC

    Register new domains and renewing existing ones is failing on certificate validation. We are currently investigating this incident. It looks like other people using the same certificate provider are also having issues the same issues.

  2. resolved Jun 03, 2026, 12:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 7, 2026

Intermittent Request Failures

Detected by Pingoru
May 07, 2026, 05:43 PM UTC
Resolved
May 07, 2026, 06:15 PM UTC
Duration
32m
Affected: Deno Deploy (Managed Network)
Timeline · 2 updates
  1. investigating May 07, 2026, 05:43 PM UTC

    We are currently investigating this incident. We're seeing again some requests failing with 503 errors with the message \`NO\_VALID\_CLUSTER\`

  2. resolved May 07, 2026, 06:15 PM UTC

    This incident has been resolved. The internal service mesh has seen handshake failures between some nodes and we have implemented mitigation measures. We're investigating the root cause for a final fix.

Read the full incident report →

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

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 27, 2026, 12:23 PM UTC
Duration
3d 2h
Timeline · 2 updates
  1. identified Apr 24, 2026, 10:00 AM UTC

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

  2. resolved Apr 27, 2026, 12:23 PM UTC

    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, 06:00 PM UTC
Duration
1h 32m
Timeline · 4 updates
  1. investigating Feb 27, 2026, 04:27 PM UTC

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

  2. identified Feb 27, 2026, 04:46 PM UTC

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

  3. monitoring Feb 27, 2026, 05:12 PM UTC

    The job queues are back to normal. We are still monitoring..

  4. resolved Feb 27, 2026, 06:00 PM UTC

    This incident has been resolved..

Read the full incident report →

Major January 30, 2026

Deno Deploy is down in Chicago

Detected by Pingoru
Jan 30, 2026, 08:10 AM UTC
Resolved
Jan 30, 2026, 02:13 PM UTC
Duration
6h 3m
Timeline · 4 updates
  1. identified Jan 30, 2026, 08:10 AM UTC

    The managed network is down in Chicago. We are seeing most requests fall back to Amsterdam, as expected. The majority of write calls to the console are currently timing out or failing. Builds are currently stuck in the "Queued" step..

  2. identified Jan 30, 2026, 09:32 AM UTC

    We have now stabilized the managed network - all traffic is now being routed away from our Chicago datacenter, to healthy datacenters. We are continuing to see (build) failures on the console..

  3. monitoring Jan 30, 2026, 09:59 AM UTC

    The Chicago datacenter is back in operation, and the managed network is serving from there again. The console has recovered, and write operations are succeeding again..

  4. resolved Jan 30, 2026, 02:13 PM UTC

    This incident has been resolved..

Read the full incident report →

Major January 27, 2026

Deno Deploy is down in the Amsterdam region

Detected by Pingoru
Jan 27, 2026, 09:07 PM UTC
Resolved
Jan 27, 2026, 10:39 PM UTC
Duration
1h 31m
Timeline · 4 updates
  1. investigating Jan 27, 2026, 09:07 PM UTC

    We are currently investigating this incident..

  2. identified Jan 27, 2026, 09:33 PM UTC

    We are continuing to work on a fix for this incident. Sites are loading, but builds are still not operational..

  3. identified Jan 27, 2026, 09:51 PM UTC

    Most console operations are failing..

  4. resolved Jan 27, 2026, 10:39 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor January 26, 2026

Deployments are failing

Detected by Pingoru
Jan 26, 2026, 12:15 AM UTC
Resolved
Jan 27, 2026, 10:24 PM UTC
Duration
1d 22h
Timeline · 3 updates
  1. investigating Jan 26, 2026, 12:15 AM UTC

    We are currently investigating this incident..

  2. monitoring Jan 26, 2026, 08:28 AM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Jan 27, 2026, 10:24 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor December 18, 2025

KV operations are failing

Detected by Pingoru
Dec 18, 2025, 10:25 PM UTC
Resolved
Dec 19, 2025, 01:35 AM UTC
Duration
3h 10m
Timeline · 5 updates
  1. investigating Dec 18, 2025, 10:25 PM UTC

    We are currently investigating this incident..

  2. resolved Dec 18, 2025, 11:26 PM UTC

    This incident has been resolved..

  3. investigating Dec 18, 2025, 11:26 PM UTC

    We are currently investigating this incident..

  4. monitoring Dec 19, 2025, 01:35 AM UTC

    We implemented a fix and are currently monitoring the result..

  5. resolved Dec 19, 2025, 01:35 AM UTC

    This incident has been resolved..

Read the full incident report →

Major December 10, 2025

console.deno.com currently down

Detected by Pingoru
Dec 10, 2025, 02:05 PM UTC
Resolved
Dec 10, 2025, 02:21 PM UTC
Duration
15m
Timeline · 2 updates
  1. investigating Dec 10, 2025, 02:05 PM UTC

    We are currently investigating this incident..

  2. resolved Dec 10, 2025, 02:21 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor November 8, 2025

Deno Deploy Deployment Failures

Detected by Pingoru
Nov 08, 2025, 06:00 PM UTC
Resolved
Nov 10, 2025, 09:59 AM UTC
Duration
1d 15h
Timeline · 2 updates
  1. monitoring Nov 08, 2025, 06:00 PM UTC

    We implemented a fix and are currently monitoring the result..

  2. resolved Nov 10, 2025, 09:59 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor November 2, 2025

Job queue processing backlog in Deno Deploy EA

Detected by Pingoru
Nov 02, 2025, 05:09 PM UTC
Resolved
Nov 05, 2025, 12:49 PM UTC
Duration
2d 19h
Timeline · 3 updates
  1. investigating Nov 02, 2025, 05:09 PM UTC

    Some users are experiencing issues with delayed or failing builds in Deploy EA. We are currently investigating this incident..

  2. monitoring Nov 03, 2025, 12:38 PM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Nov 05, 2025, 12:49 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor October 22, 2025

Intermittent Build Failures on Early Access

Detected by Pingoru
Oct 22, 2025, 10:21 PM UTC
Resolved
Oct 27, 2025, 10:31 AM UTC
Duration
4d 12h
Timeline · 4 updates
  1. investigating Oct 22, 2025, 10:21 PM UTC

    We are currently investigating this incident..

  2. identified Oct 22, 2025, 10:23 PM UTC

    We are still tracking down issues with builds. We expect the situation to persistent until tomorrow, October 23rd..

  3. monitoring Oct 23, 2025, 01:50 PM UTC

    Deno Deploy continues to see failed builds, slow response times, and occasional 500 errors. These are the result of an ongoing maintenance project aimed at improving the long-term reliability of Deno Deploy. Our team is actively working to stabilize the system..

  4. resolved Oct 27, 2025, 10:31 AM UTC

    This incident has been resolved. If you encounter any build failures or slow builds, please reach out to [email protected]..

Read the full incident report →

Minor October 22, 2025

docs.deno.com unreachable

Detected by Pingoru
Oct 22, 2025, 06:55 PM UTC
Resolved
Oct 22, 2025, 10:19 PM UTC
Duration
3h 23m
Timeline · 3 updates
  1. investigating Oct 22, 2025, 06:55 PM UTC

    We are currently investigating this incident..

  2. monitoring Oct 22, 2025, 07:52 PM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Oct 22, 2025, 10:19 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor October 20, 2025

Warm up failures with architecture specific packages

Detected by Pingoru
Oct 20, 2025, 03:00 PM UTC
Resolved
Oct 20, 2025, 05:24 PM UTC
Duration
2h 24m
Timeline · 2 updates
  1. identified Oct 20, 2025, 03:00 PM UTC

    We are seeing some failures in the "Warmup" step of builds for some projects. The error message is generally along the lines of `npm package not found in cache, ..., --cached-only is specified.` Please report any failures you are seeing to us at [email protected], or on Discord. We have identified the underlying issue and are rolling out a fix shortly..

  2. resolved Oct 20, 2025, 05:24 PM UTC

    This incident has been resolved. If you are still seeing issues, please reach out to [[email protected]](mailto:[email protected]) or get help on the Deno Discord..

Read the full incident report →

Minor September 30, 2025

Deno Deploy - Intermittent Service Degradation

Detected by Pingoru
Sep 30, 2025, 05:48 PM UTC
Resolved
Oct 02, 2025, 02:49 PM UTC
Duration
1d 21h
Timeline · 2 updates
  1. investigating Sep 30, 2025, 05:48 PM UTC

    We are currently investigating an incident that is impacting intermittently a subset of apps running in the Deno Deploy platform. The issue is restricted to apps that are using the Web Cache API. This incident is not impacting apps running in Deno Deploy Classic. .

  2. resolved Oct 02, 2025, 02:49 PM UTC

    This incident has been confirmed to be resolved since yesterday, October 1st, 2025 at around 18:00 UTC after an infrastructure patch has been rolled out..

Read the full incident report →