Deno Status - Incident history https://denostatus.com Deno Thu, 7 May 2026 17:43:42 +0000 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. Type: Incident

Duration: 32 minutes

Affected Components:

<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>17:43:42</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. We're seeing again some requests failing with 503 errors with the message \`NO\_VALID\_CLUSTER\`.</p> <p><small>May <var data-var='date'> 7</var>, <var data-var='time'>18:15:45</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Thu, 7 May 2026 17:43:42 +0000 https://denostatus.com/incident/cmovrz1s7065icessbsqvfgl3 https://denostatus.com/incident/cmovrz1s7065icessbsqvfgl3 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. Type: Incident

Duration: 4 hours and 10 minutes

Affected Components:

<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>10:20:00</var> GMT+0</small><br><strong>Investigating</strong> - Some requests failed to be served with 500 errors and a NO\_VALID\_CLUSTER error message..</p> <p><small>May <var data-var='date'> 7</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. It was caused by some networking changes being rolled out that caused peering instability..</p> ]]> Thu, 7 May 2026 10:20:00 +0000 https://denostatus.com/incident/cmovmgzfn049erm9xh8f4jzyl https://denostatus.com/incident/cmovmgzfn049erm9xh8f4jzyl 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. Type: Incident

Duration: 2 hours and 2 minutes

Affected Components: , , , , , ,

<p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>21:32:34</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>21:41:54</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>21:54:27</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>23:35:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 24 Apr 2026 21:32:34 +0000 https://denostatus.com/incident/cmodffb1u02rlx9plzuy5dfvd https://denostatus.com/incident/cmodffb1u02rlx9plzuy5dfvd 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. Type: Incident

Duration: 3 days, 2 hours and 24 minutes

Affected Components: ,

<p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>12:23:32</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 24 Apr 2026 10:00:00 +0000 https://denostatus.com/incident/cmogyd6cw19ucsu8ac6xdpyl9 https://denostatus.com/incident/cmogyd6cw19ucsu8ac6xdpyl9 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. Type: Incident

Duration: 1 hour and 33 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>16:27:14</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>16:46:37</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>17:12:44</var> GMT+0</small><br><strong>Monitoring</strong> - The job queues are back to normal. We are still monitoring..</p> <p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 27 Feb 2026 16:27:14 +0000 https://denostatus.com/incident/cmm53uxkf15fvg3s91b3jpa7h https://denostatus.com/incident/cmm53uxkf15fvg3s91b3jpa7h 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. Type: Incident

Duration: 6 hours and 3 minutes

<p><small>Jan <var data-var='date'> 30</var>, <var data-var='time'>14:13:24</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jan <var data-var='date'> 30</var>, <var data-var='time'>08:10:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Jan <var data-var='date'> 30</var>, <var data-var='time'>09:32:45</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Jan <var data-var='date'> 30</var>, <var data-var='time'>09:59:33</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> ]]> Fri, 30 Jan 2026 08:10:00 +0000 https://denostatus.com/incident/cml0o933w1hevytjosotqmamw https://denostatus.com/incident/cml0o933w1hevytjosotqmamw 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. Type: Incident

Duration: 1 hour and 31 minutes

Affected Components: , ,

<p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>21:07:59</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>21:33:39</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. Sites are loading, but builds are still not operational..</p> <p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>21:51:52</var> GMT+0</small><br><strong>Identified</strong> - Most console operations are failing..</p> <p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>22:39:05</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 27 Jan 2026 21:07:59 +0000 https://denostatus.com/incident/cmkx38kqo000cfj1ihv7uhsjx https://denostatus.com/incident/cmkx38kqo000cfj1ihv7uhsjx 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. Type: Incident

Duration: 1 day, 22 hours and 9 minutes

Affected Components: ,

<p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>00:15:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>08:28:58</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>22:24:07</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 26 Jan 2026 00:15:00 +0000 https://denostatus.com/incident/cmkuuomle04c4boz7b715zr8q https://denostatus.com/incident/cmkuuomle04c4boz7b715zr8q 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. Type: Incident

Duration: 3 hours and 11 minutes

<p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>22:25:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>23:26:06</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>23:26:07</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Dec <var data-var='date'> 19</var>, <var data-var='time'>01:35:34</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Dec <var data-var='date'> 19</var>, <var data-var='time'>01:35:35</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 18 Dec 2025 22:25:00 +0000 https://denostatus.com/incident/cmjc3noin02ueyjvo2w7b60ox https://denostatus.com/incident/cmjc3noin02ueyjvo2w7b60ox 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. Type: Incident

Duration: 15 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 10</var>, <var data-var='time'>14:05:58</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Dec <var data-var='date'> 10</var>, <var data-var='time'>14:21:10</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 10 Dec 2025 14:05:58 +0000 https://denostatus.com/incident/cmj030yss00i92lv892h17rwz https://denostatus.com/incident/cmj030yss00i92lv892h17rwz 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. Type: Incident

Duration: 14 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>09:14:48</var> GMT+0</small><br><strong>Identified</strong> - A fix is already being applied to address the issue..</p> <p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>09:28:37</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 3 Dec 2025 09:14:48 +0000 https://denostatus.com/incident/cmipsjkt9066wij9nt93qxpuq https://denostatus.com/incident/cmipsjkt9066wij9nt93qxpuq 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. Type: Incident

Duration: 1 day, 15 hours and 59 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>09:59:11</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> ]]> Sat, 8 Nov 2025 18:00:00 +0000 https://denostatus.com/incident/cmhqspm1p024m94xhj4tllutl https://denostatus.com/incident/cmhqspm1p024m94xhj4tllutl 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. Type: Incident

Duration: 2 hours and 56 minutes

Affected Components: , ,

<p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>12:52:00</var> GMT+0</small><br><strong>Identified</strong> - We're continuing a database maintenance operation which which can result in a brief disruption of the console/dashboard and API services..</p> <p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>15:48:28</var> GMT+0</small><br><strong>Resolved</strong> - The maintenance operation has been completed..</p> ]]> Tue, 4 Nov 2025 12:52:00 +0000 https://denostatus.com/incident/cmhkkj6wm00qwdv94f9h0hpnl https://denostatus.com/incident/cmhkkj6wm00qwdv94f9h0hpnl 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. Type: Incident

Duration: 1 hour and 57 minutes

Affected Components: , ,

<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>14:30:08</var> GMT+0</small><br><strong>Investigating</strong> - We're performing a database maintenance operation which can result in a brief disruption of the console/dashboard and API services..</p> <p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>14:30:45</var> GMT+0</small><br><strong>Identified</strong> - Maintenance operation in progress..</p> <p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>16:26:42</var> GMT+0</small><br><strong>Resolved</strong> - The maintenance operation has been completed..</p> ]]> Mon, 3 Nov 2025 14:30:08 +0000 https://denostatus.com/incident/cmhj8lk4g00stwiwwnqhm5hep https://denostatus.com/incident/cmhj8lk4g00stwiwwnqhm5hep 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. Type: Incident

Duration: 2 days, 19 hours and 40 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>12:38:22</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Nov <var data-var='date'> 2</var>, <var data-var='time'>17:09:45</var> GMT+0</small><br><strong>Investigating</strong> - Some users are experiencing issues with delayed or failing builds in Deploy EA. We are currently investigating this incident..</p> <p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>12:49:31</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 2 Nov 2025 17:09:45 +0000 https://denostatus.com/incident/cmhhyuya802h9r7mexgb7q6vv https://denostatus.com/incident/cmhhyuya802h9r7mexgb7q6vv 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. Type: Incident

Duration: 4 days, 12 hours and 10 minutes

Affected Components: , , , , , , , , , , ,

<p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>22:21:56</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>22:23:02</var> GMT+0</small><br><strong>Identified</strong> - We are still tracking down issues with builds. We expect the situation to persistent until tomorrow, October 23rd..</p> <p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>13:50:13</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>10:31:26</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. If you encounter any build failures or slow builds, please reach out to deploy@deno.com..</p> ]]> Wed, 22 Oct 2025 22:21:56 +0000 https://denostatus.com/incident/cmh2k61xe00bm5aha0y1tq9qp https://denostatus.com/incident/cmh2k61xe00bm5aha0y1tq9qp 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. Type: Incident

Duration: 3 hours and 23 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>18:55:58</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>19:52:08</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>22:19:13</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 22 Oct 2025 18:55:58 +0000 https://denostatus.com/incident/cmh2ct61901639fixytg95mmk https://denostatus.com/incident/cmh2ct61901639fixytg95mmk 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. Type: Incident

Duration: 2 hours and 24 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>15:00:05</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>17:24:16</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Mon, 20 Oct 2025 15:00:05 +0000 https://denostatus.com/incident/cmgzciul702qqftk46ugywhrm https://denostatus.com/incident/cmgzciul702qqftk46ugywhrm 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 Type: Maintenance

Duration: 2 hours

Affected Components:

<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>12:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Mon, 20 Oct 2025 12:30:00 +0000 https://denostatus.com/maintenance/cmgz37yad0221yjk0cstpfcam https://denostatus.com/maintenance/cmgz37yad0221yjk0cstpfcam 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. Type: Incident

Duration: 1 day, 21 hours and 1 minute

Affected Components:

<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>14:49:50</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>17:48:32</var> GMT+0</small><br><strong>Investigating</strong> - 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. .</p> ]]> Tue, 30 Sep 2025 17:48:32 +0000 https://denostatus.com/incident/cmg6uppy2016jrhkvuvhjzpqm https://denostatus.com/incident/cmg6uppy2016jrhkvuvhjzpqm 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. Type: Incident

Duration: 8 minutes

Affected Components: , , ,

<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>16:11:35</var> GMT+0</small><br><strong>Identified</strong> - We expect brief disruption of the dashboard and API due to database maintenance..</p> <p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>16:19:47</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 14 Aug 2025 16:11:35 +0000 https://denostatus.com/incident/cmeblk077000pfb7tc0kso5ck https://denostatus.com/incident/cmeblk077000pfb7tc0kso5ck 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. Type: Incident

Duration: 2 hours and 20 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>12:21:47</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>11:00:46</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>13:20:46</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 7 Jul 2025 11:00:46 +0000 https://denostatus.com/incident/cmct24jpi005shyq8m1dsn394 https://denostatus.com/incident/cmct24jpi005shyq8m1dsn394 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). Type: Incident

Duration: 6 days, 2 hours and 29 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Jun <var data-var='date'> 28</var>, <var data-var='time'>12:52:03</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>14:58:35</var> GMT+0</small><br><strong>Resolved</strong> - 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)..</p> ]]> Thu, 26 Jun 2025 12:30:00 +0000 https://denostatus.com/incident/cmcevwyc8017hc5r0r77bm0v5 https://denostatus.com/incident/cmcevwyc8017hc5r0r77bm0v5 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. Type: Incident

Duration: 2 hours and 38 minutes

Affected Components: , , , , ,

<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>18:15:25</var> GMT+0</small><br><strong>Investigating</strong> - We have noticed intermittent failures when accessing <https://dash.deno.com/> We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>18:40:16</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>20:53:29</var> GMT+0</small><br><strong>Resolved</strong> - GCP Cloud seems to have recovered and all services seem to be back to normal. .</p> ]]> Thu, 12 Jun 2025 18:15:25 +0000 https://denostatus.com/incident/cmbtp8l3n001a75yry9y7fhzd https://denostatus.com/incident/cmbtp8l3n001a75yry9y7fhzd 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. Type: Incident

Duration: 36 minutes

Affected Components:

<p><small>May <var data-var='date'> 28</var>, <var data-var='time'>18:02:42</var> GMT+0</small><br><strong>Identified</strong> - 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.</p> <p><small>May <var data-var='date'> 28</var>, <var data-var='time'>18:07:27</var> GMT+0</small><br><strong>Monitoring</strong> - The service has recovered. We'll continue monitoring its stability and work on preventive mechanisms..</p> <p><small>May <var data-var='date'> 28</var>, <var data-var='time'>18:38:45</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. We've identified the root cause and will be patching the service soon to prevent re-occurrence. .</p> ]]> Wed, 28 May 2025 18:02:42 +0000 https://denostatus.com/incident/cmb896g1j000sjb2lddecoppf https://denostatus.com/incident/cmb896g1j000sjb2lddecoppf 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. Type: Incident

Duration: 20 hours and 49 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>08:47:23</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Jan <var data-var='date'> 9</var>, <var data-var='time'>12:20:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>09:09:11</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 9 Jan 2025 12:20:00 +0000 https://denostatus.com/incident/cm5qhqm6d0004wcq981n94qqe https://denostatus.com/incident/cm5qhqm6d0004wcq981n94qqe