Deno Deploy had 22 outages in the last 2 years totaling 5h 49m of downtime — averaging 0.9 incidents per month.
There were 22 Deno Deploy outages since May 28, 2025 totaling 5h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
This incident has been resolved.
We are currently investigating this incident. We're seeing again some requests failing with 503 errors with the message \`NO\_VALID\_CLUSTER\`
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.
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.
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.
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.
This incident has been resolved.
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.
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.
Type: Incident Duration: 6 hours and 3 minutes Jan 30, 14:13:24 GMT+0 - Resolved - This incident has been resolved. Jan 30, 08:10:00 GMT+0 - Identified - 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. Jan 30, 09:32:45 GMT+0 - Identified - 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. Jan 30, 09:59:33 GMT+0 - Monitoring - 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.
Type: Incident Duration: 1 hour and 31 minutes Affected Components: , Console, Managed Network, Deno Deploy → Jan 27, 21:07:59 GMT+0 - Investigating - We are currently investigating this incident. Jan 27, 21:33:39 GMT+0 - Identified - We are continuing to work on a fix for this incident. Sites are loading, but builds are still not operational. Jan 27, 21:51:52 GMT+0 - Identified - Most console operations are failing. Jan 27, 22:39:05 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 day, 22 hours and 9 minutes Affected Components: API, GitHub Integration Jan 26, 00:15:00 GMT+0 - Investigating - We are currently investigating this incident. Jan 26, 08:28:58 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jan 27, 22:24:07 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 3 hours and 11 minutes Dec 18, 22:25:00 GMT+0 - Investigating - We are currently investigating this incident. Dec 18, 23:26:06 GMT+0 - Resolved - This incident has been resolved. Dec 18, 23:26:07 GMT+0 - Investigating - We are currently investigating this incident. Dec 19, 01:35:34 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Dec 19, 01:35:35 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 15 minutes Affected Components: Console Dec 10, 14:05:58 GMT+0 - Investigating - We are currently investigating this incident. Dec 10, 14:21:10 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 14 minutes Affected Components: Edge Network Dec 3, 09:14:48 GMT+0 - Identified - A fix is already being applied to address the issue. Dec 3, 09:28:37 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 day, 15 hours and 59 minutes Affected Components: Console Nov 10, 09:59:11 GMT+0 - Resolved - This incident has been resolved. Nov 8, 18:00:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.
Type: Incident Duration: 2 days, 19 hours and 40 minutes Affected Components: Console Nov 3, 12:38:22 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Nov 2, 17:09:45 GMT+0 - Investigating - Some users are experiencing issues with delayed or failing builds in Deploy EA. We are currently investigating this incident. Nov 5, 12:49:31 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 4 days, 12 hours and 10 minutes Affected Components: GitHub Integration, Edge Network, deno.land/x import, cdn.deno.land, deno.land, deno.com, KV, deno.land/std import, API, Console, Managed Network, Dashboard Oct 22, 22:21:56 GMT+0 - Investigating - We are currently investigating this incident. Oct 22, 22:23:02 GMT+0 - Identified - We are still tracking down issues with builds. We expect the situation to persistent until tomorrow, October 23rd. Oct 23, 13:50:13 GMT+0 - Monitoring - 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. Oct 27, 10:31:26 GMT+0 - Resolved - This incident has been resolved. If you encounter any build failures or slow builds, please reach out to [email protected].
Type: Incident Duration: 3 hours and 23 minutes Affected Components: deno.com Oct 22, 18:55:58 GMT+0 - Investigating - We are currently investigating this incident. Oct 22, 19:52:08 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Oct 22, 22:19:13 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 2 hours and 24 minutes Affected Components: Console Oct 20, 15:00:05 GMT+0 - Identified - 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. Oct 20, 17:24:16 GMT+0 - Resolved - 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.
Type: Maintenance Duration: 2 hours Affected Components: Console Oct 20, 12:30:00 GMT+0 - Identified - We are working to upgrade our managed network. As part of the preparatory work for this, some write operations such as creating an organization, creating or updating an app, or starting a new deployment may take longer than usual. Traffic on the managed network will continue to be served as normal. Oct 20, 12:30:01 GMT+0 - Identified - Maintenance is now in progress Oct 20, 14:30:00 GMT+0 - Completed - Maintenance has completed successfully
Type: Incident Duration: 1 day, 21 hours and 1 minute Affected Components: Edge Network Oct 2, 14:49:50 GMT+0 - Resolved - 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. Sep 30, 17:48:32 GMT+0 - Investigating - 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.
Type: Incident Duration: 2 hours and 20 minutes Affected Components: GitHub Integration, API Jul 7, 12:21:47 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 7, 11:00:46 GMT+0 - Identified - Due to sporadic failures in our API service, many API calls are spuriously failing. Particularly long running API calls are affected, such as builds triggered from GitHub Actions. We have found the root cause, and are working on a fix. Jul 7, 13:20:46 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 2 hours and 38 minutes Affected Components: API, Edge Network, deno.land/std import, cdn.deno.land, deno.land/x import, Dashboard Jun 12, 18:15:25 GMT+0 - Investigating - We have noticed intermittent failures when accessing We are currently investigating this incident. Jun 12, 18:40:16 GMT+0 - Investigating - The impact seems to be related with a wider issue at GCP where some of our infrastructure is hosted. We're starting to see impact on the Edge Network as well. Jun 12, 20:53:29 GMT+0 - Resolved - GCP Cloud seems to have recovered and all services seem to be back to normal.
Type: Incident Duration: 36 minutes Affected Components: Dashboard May 28, 18:02:42 GMT+0 - Identified - Deno Deploy dash is down returning a 500 Internal Error due to one of its dependencies having a service disruption. We expect the service to recover shortly May 28, 18:07:27 GMT+0 - Monitoring - The service has recovered. We'll continue monitoring its stability and work on preventive mechanisms. May 28, 18:38:45 GMT+0 - Resolved - This incident has been resolved. We've identified the root cause and will be patching the service soon to prevent re-occurrence.