tag:denostatus.com,2005:/history Deno Status - Incident history 2026-05-07T17:43:42.271+00:00 Deno tag:denostatus.com,2005:Incident/cmovrz1s7065icessbsqvfgl3 2026-05-07T17:43:42.271+00:00 2026-05-07T17:43:42.271+00:00 Intermittent Request Failures Type: Incident

Duration: 32 minutes

Affected Components: Managed Network

May 7, 17:43:42 GMT+0
Investigating - We are currently investigating this incident. We're seeing again some requests failing with 503 errors with the message \`NO\_VALID\_CLUSTER\`.

May 7, 18:15:45 GMT+0
Resolved - 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..

]]> tag:denostatus.com,2005:Incident/cmovmgzfn049erm9xh8f4jzyl 2026-05-07T10:20:00.000+00:00 2026-05-07T10:20:00.000+00:00 Intermittent Request Failures Type: Incident

Duration: 4 hours and 10 minutes

Affected Components: Managed Network

May 7, 10:20:00 GMT+0
Investigating - Some requests failed to be served with 500 errors and a NO\_VALID\_CLUSTER error message..

May 7, 14:30:00 GMT+0
Resolved - This incident has been resolved. It was caused by some networking changes being rolled out that caused peering instability..

]]> tag:denostatus.com,2005:Incident/cmodffb1u02rlx9plzuy5dfvd 2026-04-24T21:32:34.172+00:00 2026-04-24T21:32:34.172+00:00 Degraded performance on Deno Deploy 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..

]]> tag:denostatus.com,2005:Incident/cmogyd6cw19ucsu8ac6xdpyl9 2026-04-24T10:00:00.000+00:00 2026-04-24T10:00:00.000+00:00 New builds might take longer to start serving traffic 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..

]]> tag:denostatus.com,2005:Incident/cmm53uxkf15fvg3s91b3jpa7h 2026-02-27T16:27:14.151+00:00 2026-02-27T16:27:14.151+00:00 Deno Deploy deployments, app creations, org creations seeing increased error rate 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..

]]> tag:denostatus.com,2005:Incident/cml0o933w1hevytjosotqmamw 2026-01-30T08:10:00.000+00:00 2026-01-30T14:13:24.686+00:00 Deno Deploy is down in Chicago 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..

]]> tag:denostatus.com,2005:Incident/cmkx38kqo000cfj1ihv7uhsjx 2026-01-27T21:07:59.439+00:00 2026-01-27T21:07:59.439+00:00 Deno Deploy is down in the Amsterdam region 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..

]]> tag:denostatus.com,2005:Incident/cmkuuomle04c4boz7b715zr8q 2026-01-26T00:15:00.000+00:00 2026-01-26T00:15:00.000+00:00 Deployments are failing 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..

]]> tag:denostatus.com,2005:Incident/cmjc3noin02ueyjvo2w7b60ox 2025-12-18T22:25:00.000+00:00 2025-12-18T22:25:00.000+00:00 KV operations are failing 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..

]]> tag:denostatus.com,2005:Incident/cmj030yss00i92lv892h17rwz 2025-12-10T14:05:58.207+00:00 2025-12-10T14:05:58.207+00:00 console.deno.com currently down 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..

]]> tag:denostatus.com,2005:Incident/cmipsjkt9066wij9nt93qxpuq 2025-12-03T09:14:48.711+00:00 2025-12-03T09:14:48.711+00:00 Deno Deploy Classic - Intermittent Failures on Edge Network 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..

]]> tag:denostatus.com,2005:Incident/cmhqspm1p024m94xhj4tllutl 2025-11-08T18:00:00.000+00:00 2025-11-10T09:59:11.572+00:00 Deno Deploy Deployment Failures 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..

]]> tag:denostatus.com,2005:Incident/cmhkkj6wm00qwdv94f9h0hpnl 2025-11-04T12:52:00.791+00:00 2025-11-04T12:52:00.791+00:00 Database maintenance Type: Incident

Duration: 2 hours and 56 minutes

Affected Components: API, Console, Dashboard

Nov 4, 12:52:00 GMT+0
Identified - We're continuing a database maintenance operation which which can result in a brief disruption of the console/dashboard and API services..

Nov 4, 15:48:28 GMT+0
Resolved - The maintenance operation has been completed..

]]> tag:denostatus.com,2005:Incident/cmhj8lk4g00stwiwwnqhm5hep 2025-11-03T14:30:08.835+00:00 2025-11-03T14:30:08.835+00:00 Database maintenance Type: Incident

Duration: 1 hour and 57 minutes

Affected Components: API, Console, Dashboard

Nov 3, 14:30:08 GMT+0
Investigating - We're performing a database maintenance operation which can result in a brief disruption of the console/dashboard and API services..

Nov 3, 14:30:45 GMT+0
Identified - Maintenance operation in progress..

Nov 3, 16:26:42 GMT+0
Resolved - The maintenance operation has been completed..

]]> tag:denostatus.com,2005:Incident/cmhhyuya802h9r7mexgb7q6vv 2025-11-02T17:09:45.142+00:00 2025-11-03T12:38:22.922+00:00 Job queue processing backlog in Deno Deploy EA 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..

]]> tag:denostatus.com,2005:Incident/cmh2k61xe00bm5aha0y1tq9qp 2025-10-22T22:21:56.490+00:00 2025-10-22T22:21:56.490+00:00 Intermittent Build Failures on Early Access 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 deploy@deno.com..

]]> tag:denostatus.com,2005:Incident/cmh2ct61901639fixytg95mmk 2025-10-22T18:55:58.139+00:00 2025-10-22T18:55:58.139+00:00 docs.deno.com unreachable 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..

]]> tag:denostatus.com,2005:Incident/cmgzciul702qqftk46ugywhrm 2025-10-20T15:00:05.112+00:00 2025-10-20T15:00:05.112+00:00 Warm up failures with architecture specific packages 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 deploy@deno.com, 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 [deploy@deno.com](mailto:deploy@deno.com) or get help on the Deno Discord..

]]> tag:denostatus.com,2005:Maintenance/cmgz37yad0221yjk0cstpfcam 2025-10-20T12:30:00.000+00:00 2025-10-20T12:30:00.000+00:00 Preparation for managed network upgrades 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.

]]> tag:denostatus.com,2005:Incident/cmg6uppy2016jrhkvuvhjzpqm 2025-09-30T17:48:32.850+00:00 2025-10-02T14:49:50.103+00:00 Deno Deploy - Intermittent Service Degradation 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. .

]]> tag:denostatus.com,2005:Incident/cmeblk077000pfb7tc0kso5ck 2025-08-14T16:11:35.583+00:00 2025-08-14T16:11:35.583+00:00 Database maintenance Type: Incident

Duration: 8 minutes

Affected Components: , Dashboard, GitHub Integration, API, Deno Deploy Classic →

Aug 14, 16:11:35 GMT+0
Identified - We expect brief disruption of the dashboard and API due to database maintenance..

Aug 14, 16:19:47 GMT+0
Resolved - This incident has been resolved..

]]> tag:denostatus.com,2005:Incident/cmct24jpi005shyq8m1dsn394 2025-07-07T11:00:46.374+00:00 2025-07-07T12:21:47.837+00:00 Issues with API calls 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..

]]> tag:denostatus.com,2005:Incident/cmcevwyc8017hc5r0r77bm0v5 2025-06-26T12:30:00.000+00:00 2025-06-26T12:30:00.000+00:00 Connectivity issues from AT&T networks to IPv4 Type: Incident

Duration: 6 days, 2 hours and 29 minutes

Affected Components: Edge Network

Jun 26, 12:30:00 GMT+0
Identified - We are getting customer reports regarding connectivity issues to Deno Deploy from AT&T networks when connecting via IPv4. We are in contact with AT&T to resolve the issue as quickly as possible. IPv6 traffic is unaffected. If you are a Deno Deploy customer with a custom domain and are affected by this issue, please contact support@deno.com..

Jun 28, 12:52:03 GMT+0
Identified - The issue is still ongoing. We continue chasing AT&T to resolve the issue. AT&T users are not able to reach custom domains hosted on Deno Deploy over IPv4..

Jul 2, 14:58:35 GMT+0
Resolved - This incident has been resolved. All AT&T customers should now be able to access all Deno Deploy services over IPv4 once again. If you are still seeing issues, please reach out to us directly at [support@deno.com](mailto:support@deno.com). IPv6 traffic was unaffected during the course of the incident. If you were affected by this outage and would like to talk, please email us at [support@deno.com](mailto:support@deno.com)..

]]> tag:denostatus.com,2005:Incident/cmbtp8l3n001a75yry9y7fhzd 2025-06-12T18:15:25.694+00:00 2025-06-12T18:15:25.694+00:00 Deno Deploy - Dash degradation 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 <https://dash.deno.com/> 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. .

]]> tag:denostatus.com,2005:Incident/cmb896g1j000sjb2lddecoppf 2025-05-28T18:02:42.192+00:00 2025-05-28T18:02:42.192+00:00 Deno Deploy - Dash unavailable 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. .

]]> tag:denostatus.com,2005:Incident/cm5qhqm6d0004wcq981n94qqe 2025-01-09T12:20:00.000+00:00 2025-01-10T08:47:23.469+00:00 Deno KV writes are failing for Subhosting organizations Type: Incident

Duration: 20 hours and 49 minutes

Affected Components: KV

Jan 10, 08:47:23 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Jan 9, 12:20:00 GMT+0
Identified - We are continuing to work on a fix for this incident..

Jan 10, 09:09:11 GMT+0
Resolved - This incident has been resolved..

]]>