<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:denostatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://denostatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://denostatus.com/history.atom"/>
  <title>Deno Status - Incident history</title>
  <updated>2026-09-07T12:13:26.899+00:00</updated>
  <author>
    <name>Deno</name>
  </author>
  
<entry>
  <id>tag:denostatus.com,2005:Incident/cmtr7c46h000u13p8zfrx3qth</id>
  <published>2026-09-07T12:13:26.899+00:00</published>
  <updated>2026-09-07T12:13:26.899+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmtr7c46h000u13p8zfrx3qth"/>
  <title>Deno Deploy request failures in ord</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 9 minutes</p>
    <p><strong>Affected Components:</strong> Managed Network</p>
    <p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>12:13:26</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have identified increased failures in serving requests from our ord region. We are currently investigating this incident..</p>
<p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>12:24:36</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The service is recovered and we are currently monitoring the recovery..</p>
<p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>13:22:06</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved.

The root cause was a service incident on one of our datacenter providers. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmr46orl100gl0rmgud0sd3k2</id>
  <published>2026-07-03T00:07:00.000+00:00</published>
  <updated>2026-07-03T00:07:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmr46orl100gl0rmgud0sd3k2"/>
  <title>Deno Deploy Chicago cluster outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 53 minutes</p>
    <p><strong>Affected Components:</strong> Managed Network, deno.land, deno.com</p>
    <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>00:07:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  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..</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>00:23:08</var> GMT+0</small><br /><strong>Investigating</strong> -
  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..</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>00:53:15</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The infrastructure problem at one of our cloud providers has been mitigated, and affected services are recovering. We are monitoring for any remaining issues..</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>00:34:39</var> GMT+0</small><br /><strong>Identified</strong> -
  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..</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>03:00:06</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved. deno.com, deno.land, and Deno Deploy managed network traffic have recovered and we are no longer seeing impact..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmr2b5mjh00xa0kpyhdeblv3y</id>
  <published>2026-07-01T16:25:00.000+00:00</published>
  <updated>2026-07-01T16:25:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmr2b5mjh00xa0kpyhdeblv3y"/>
  <title>Deno Deploy Chicago cluster outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 50 minutes</p>
    <p><strong>Affected Components:</strong> deno.land, Managed Network, deno.com</p>
    <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>16:25:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Starting around 09:25 PDT, the Deno Deploy Chicago cluster experienced an outage. This affected 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 were affected as well. The Deno Deploy console remained available, but builds triggered via GitHub integration, CLI, or API were failing because builds run in Chicago. Sandbox creation in Chicago was also failing..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>17:15:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The Chicago cluster outage was resolved around 10:15 PDT and affected services have recovered. We are continuing to monitor..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>17:15:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmqmvv5y102v52jqex8grybvl</id>
  <published>2026-06-20T21:42:08.649+00:00</published>
  <updated>2026-06-20T21:42:08.649+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmqmvv5y102v52jqex8grybvl"/>
  <title>Deno Deploy Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 31 minutes</p>
    <p><strong>Affected Components:</strong> deno.land/std import, Managed Network, deno.land/x import, Console, cdn.deno.land, deno.land, deno.com</p>
    <p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>21:42:08</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>21:59:59</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>22:13:27</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmqfccesi079l2jqj9jq9235j</id>
  <published>2026-06-15T15:01:17.666+00:00</published>
  <updated>2026-06-15T15:01:17.666+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmqfccesi079l2jqj9jq9235j"/>
  <title>Deno Deploy Console - Slow to respond</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 minutes</p>
    <p><strong>Affected Components:</strong> Console</p>
    <p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>15:01:17</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>15:15:04</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmpxvkty902bgqulxcwq4c55c</id>
  <published>2026-06-03T09:39:51.818+00:00</published>
  <updated>2026-06-03T12:54:37.106+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmpxvkty902bgqulxcwq4c55c"/>
  <title>Registering new and renew existing custom domains</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> Console</p>
    <p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>12:54:37</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>09:39:51</var> GMT+0</small><br /><strong>Identified</strong> -
  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..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmovrz1s7065icessbsqvfgl3</id>
  <published>2026-05-07T17:43:42.271+00:00</published>
  <updated>2026-05-07T17:43:42.271+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmovrz1s7065icessbsqvfgl3"/>
  <title>Intermittent Request Failures</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 32 minutes</p>
    <p><strong>Affected Components:</strong> Managed Network</p>
    <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&#039;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&#039;re investigating the root cause for a final fix..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmovmgzfn049erm9xh8f4jzyl</id>
  <published>2026-05-07T10:20:00.000+00:00</published>
  <updated>2026-05-07T10:20:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmovmgzfn049erm9xh8f4jzyl"/>
  <title>Intermittent Request Failures</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> Managed Network</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmodffb1u02rlx9plzuy5dfvd</id>
  <published>2026-04-24T21:32:34.172+00:00</published>
  <updated>2026-04-24T21:32:34.172+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmodffb1u02rlx9plzuy5dfvd"/>
  <title>Degraded performance on Deno Deploy</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 2 minutes</p>
    <p><strong>Affected Components:</strong> deno.land/std import, Console, deno.land/x import, cdn.deno.land, deno.land, deno.com, Managed Network</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmogyd6cw19ucsu8ac6xdpyl9</id>
  <published>2026-04-24T10:00:00.000+00:00</published>
  <updated>2026-04-24T10:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmogyd6cw19ucsu8ac6xdpyl9"/>
  <title>New builds might take longer to start serving traffic</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 2 hours and 24 minutes</p>
    <p><strong>Affected Components:</strong> Console, Managed Network</p>
    <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&#039;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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmm53uxkf15fvg3s91b3jpa7h</id>
  <published>2026-02-27T16:27:14.151+00:00</published>
  <updated>2026-02-27T16:27:14.151+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmm53uxkf15fvg3s91b3jpa7h"/>
  <title>Deno Deploy deployments, app creations, org creations seeing increased error rate</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 33 minutes</p>
    <p><strong>Affected Components:</strong> Console</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cml0o933w1hevytjosotqmamw</id>
  <published>2026-01-30T08:10:00.000+00:00</published>
  <updated>2026-01-30T14:13:24.686+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cml0o933w1hevytjosotqmamw"/>
  <title>Deno Deploy is down in Chicago</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 3 minutes</p>
    
    <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 &quot;Queued&quot; 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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmkx38kqo000cfj1ihv7uhsjx</id>
  <published>2026-01-27T21:07:59.439+00:00</published>
  <updated>2026-01-27T21:07:59.439+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmkx38kqo000cfj1ihv7uhsjx"/>
  <title>Deno Deploy is down in the Amsterdam region</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 31 minutes</p>
    <p><strong>Affected Components:</strong> , Console, Managed Network, 
Deno Deploy →</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmkuuomle04c4boz7b715zr8q</id>
  <published>2026-01-26T00:15:00.000+00:00</published>
  <updated>2026-01-26T00:15:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmkuuomle04c4boz7b715zr8q"/>
  <title>Deployments are failing</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 22 hours and 9 minutes</p>
    <p><strong>Affected Components:</strong> API, GitHub Integration</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmjc3noin02ueyjvo2w7b60ox</id>
  <published>2025-12-18T22:25:00.000+00:00</published>
  <updated>2025-12-18T22:25:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmjc3noin02ueyjvo2w7b60ox"/>
  <title>KV operations are failing</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 11 minutes</p>
    
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmj030yss00i92lv892h17rwz</id>
  <published>2025-12-10T14:05:58.207+00:00</published>
  <updated>2025-12-10T14:05:58.207+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmj030yss00i92lv892h17rwz"/>
  <title>console.deno.com currently down</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> Console</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmipsjkt9066wij9nt93qxpuq</id>
  <published>2025-12-03T09:14:48.711+00:00</published>
  <updated>2025-12-03T09:14:48.711+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmipsjkt9066wij9nt93qxpuq"/>
  <title>Deno Deploy Classic - Intermittent Failures on Edge Network</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 minutes</p>
    <p><strong>Affected Components:</strong> Edge Network</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmhqspm1p024m94xhj4tllutl</id>
  <published>2025-11-08T18:00:00.000+00:00</published>
  <updated>2025-11-10T09:59:11.572+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmhqspm1p024m94xhj4tllutl"/>
  <title>Deno Deploy Deployment Failures</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 15 hours and 59 minutes</p>
    <p><strong>Affected Components:</strong> Console</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmhkkj6wm00qwdv94f9h0hpnl</id>
  <published>2025-11-04T12:52:00.791+00:00</published>
  <updated>2025-11-04T12:52:00.791+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmhkkj6wm00qwdv94f9h0hpnl"/>
  <title>Database maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 56 minutes</p>
    <p><strong>Affected Components:</strong> API, Console, Dashboard</p>
    <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&#039;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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmhj8lk4g00stwiwwnqhm5hep</id>
  <published>2025-11-03T14:30:08.835+00:00</published>
  <updated>2025-11-03T14:30:08.835+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmhj8lk4g00stwiwwnqhm5hep"/>
  <title>Database maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 57 minutes</p>
    <p><strong>Affected Components:</strong> API, Console, Dashboard</p>
    <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&#039;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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmhhyuya802h9r7mexgb7q6vv</id>
  <published>2025-11-02T17:09:45.142+00:00</published>
  <updated>2025-11-03T12:38:22.922+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmhhyuya802h9r7mexgb7q6vv"/>
  <title>Job queue processing backlog in Deno Deploy EA</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 19 hours and 40 minutes</p>
    <p><strong>Affected Components:</strong> Console</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmh2k61xe00bm5aha0y1tq9qp</id>
  <published>2025-10-22T22:21:56.490+00:00</published>
  <updated>2025-10-22T22:21:56.490+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmh2k61xe00bm5aha0y1tq9qp"/>
  <title>Intermittent Build Failures on Early Access</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 12 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> 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</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmh2ct61901639fixytg95mmk</id>
  <published>2025-10-22T18:55:58.139+00:00</published>
  <updated>2025-10-22T18:55:58.139+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmh2ct61901639fixytg95mmk"/>
  <title>docs.deno.com unreachable</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 23 minutes</p>
    <p><strong>Affected Components:</strong> deno.com</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmgzciul702qqftk46ugywhrm</id>
  <published>2025-10-20T15:00:05.112+00:00</published>
  <updated>2025-10-20T15:00:05.112+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmgzciul702qqftk46ugywhrm"/>
  <title>Warm up failures with architecture specific packages</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 24 minutes</p>
    <p><strong>Affected Components:</strong> Console</p>
    <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 &quot;Warmup&quot; 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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Maintenance/cmgz37yad0221yjk0cstpfcam</id>
  <published>2025-10-20T12:30:00.000+00:00</published>
  <updated>2025-10-20T12:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/maintenance/cmgz37yad0221yjk0cstpfcam"/>
  <title>Preparation for managed network upgrades</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> Console</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmg6uppy2016jrhkvuvhjzpqm</id>
  <published>2025-09-30T17:48:32.850+00:00</published>
  <updated>2025-10-02T14:49:50.103+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmg6uppy2016jrhkvuvhjzpqm"/>
  <title>Deno Deploy - Intermittent Service Degradation</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 21 hours and 1 minute</p>
    <p><strong>Affected Components:</strong> Edge Network</p>
    <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>

        ]]>
  </content>
</entry>

</feed>