<?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-02-27T16:27:14.151+00:00</updated>
  <author>
    <name>Deno</name>
  </author>
  
<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>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmeblk077000pfb7tc0kso5ck</id>
  <published>2025-08-14T16:11:35.583+00:00</published>
  <updated>2025-08-14T16:11:35.583+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmeblk077000pfb7tc0kso5ck"/>
  <title>Database maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 minutes</p>
    <p><strong>Affected Components:</strong> , Dashboard, GitHub Integration, API, 
Deno Deploy Classic →</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmct24jpi005shyq8m1dsn394</id>
  <published>2025-07-07T11:00:46.374+00:00</published>
  <updated>2025-07-07T12:21:47.837+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmct24jpi005shyq8m1dsn394"/>
  <title>Issues with API calls</title>

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

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmcevwyc8017hc5r0r77bm0v5</id>
  <published>2025-06-26T12:30:00.000+00:00</published>
  <updated>2025-06-26T12:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmcevwyc8017hc5r0r77bm0v5"/>
  <title>Connectivity issues from AT&amp;T networks to IPv4 </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 2 hours and 29 minutes</p>
    <p><strong>Affected Components:</strong> Edge Network</p>
    <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&amp;T networks when connecting via IPv4.

  
We are in contact with AT&amp;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&amp;T to resolve the issue.

AT&amp;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&amp;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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmbtp8l3n001a75yry9y7fhzd</id>
  <published>2025-06-12T18:15:25.694+00:00</published>
  <updated>2025-06-12T18:15:25.694+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmbtp8l3n001a75yry9y7fhzd"/>
  <title>Deno Deploy - Dash degradation</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 38 minutes</p>
    <p><strong>Affected Components:</strong> API, Edge Network, deno.land/std import, cdn.deno.land, deno.land/x import, Dashboard</p>
    <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 &lt;https://dash.deno.com/&gt;

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&#039;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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cmb896g1j000sjb2lddecoppf</id>
  <published>2025-05-28T18:02:42.192+00:00</published>
  <updated>2025-05-28T18:02:42.192+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cmb896g1j000sjb2lddecoppf"/>
  <title>Deno Deploy - Dash unavailable</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 36 minutes</p>
    <p><strong>Affected Components:</strong> Dashboard</p>
    <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&#039;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&#039;ve identified the root cause and will be patching the service soon to prevent re-occurrence. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cm5qhqm6d0004wcq981n94qqe</id>
  <published>2025-01-09T12:20:00.000+00:00</published>
  <updated>2025-01-10T08:47:23.469+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cm5qhqm6d0004wcq981n94qqe"/>
  <title>Deno KV writes are failing for Subhosting organizations</title>

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

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cm4cx9xst00ejs470t3oq1ase</id>
  <published>2024-12-06T15:38:00.000+00:00</published>
  <updated>2024-12-06T16:10:37.920+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cm4cx9xst00ejs470t3oq1ase"/>
  <title>dash.deno.com is unavailable for some users</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 33 minutes</p>
    <p><strong>Affected Components:</strong> API, Dashboard</p>
    <p><small>Dec <var data-var='date'> 6</var>, <var data-var='time'>16:10:37</var> GMT+0</small><br /><strong>Resolved</strong> -
  The issue has been resolved..</p>
<p><small>Dec <var data-var='date'> 6</var>, <var data-var='time'>15:38:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating reports that some users are unable to access deno.com..</p>
<p><small>Dec <var data-var='date'> 6</var>, <var data-var='time'>16:02:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The system is recovering, and we are actively monitoring for further issues..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/cm2svhgu000351kabsvgajs10</id>
  <published>2024-10-28T09:10:00.000+00:00</published>
  <updated>2024-10-28T09:10:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/cm2svhgu000351kabsvgajs10"/>
  <title>502 Bad Gateway errors on Deno Deploy</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 19 minutes</p>
    <p><strong>Affected Components:</strong> Edge Network</p>
    <p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>09:10:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We started to see an increase of 502 Bad Gateway errors in the Deno Deploy system at 2024-10-28 09:10 UTC.

We already applied a fix to this issue around 2024-10-28 10:00 UTC, now monitoring if the issue is resolved..</p>
<p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>10:28:53</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/clx1sfg8r190502bkoddkx6h1pi</id>
  <published>2024-06-05T10:59:00.000+00:00</published>
  <updated>2024-06-05T10:59:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/clx1sfg8r190502bkoddkx6h1pi"/>
  <title>Degraded service on Deploy</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 53 minutes</p>
    <p><strong>Affected Components:</strong> deno.land, deno.com, Edge Network</p>
    <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>10:59:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  There was some service degradation on Deploy between 10:59 and 11:23 UTC causing intermittent 502 HTTP errors and longer load times. The issue was caused by some instability on the runtime infrastructure during a production rollout. The root cause is currently under investigation..</p>
<p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>17:51:31</var> GMT+0</small><br /><strong>Resolved</strong> -
  The service degradation of Deploy impacted the following two regions:

* Southeastern Asia between 10:59 and 11:03 UTC with less than 8% of traffic affected
* Eastern South America between 11:05 and 11:21 UTC with less than 17% of traffic affected

This occurrence did not impact any of the other global regions.

The impact was felt during a service transition period into a new release that was being deployed at the time. This type of impact is not expected and we continue investigating the root cause at this stage. We will be implementing system improvements to ensure that similar situations in the future are prevented..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:denostatus.com,2005:Incident/clx04xzii13653bon1jqmtwblj</id>
  <published>2024-06-04T08:26:04.290+00:00</published>
  <updated>2024-06-04T08:26:04.290+00:00</updated>
  <link rel="alternate" type="text/html" href="https://denostatus.com/incident/clx04xzii13653bon1jqmtwblj"/>
  <title>TLS certificates are not automatically renewed for some custom domains</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 39 minutes</p>
    <p><strong>Affected Components:</strong> Edge Network</p>
    <p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>08:26:04</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>13:56:02</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and all custom domain services are recovering. At peak, 200 domains were temporarily impacted. A full recovery is expected within 10 to 15 minutes..</p>
<p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>14:04:38</var> GMT+0</small><br /><strong>Resolved</strong> -
  The service has now been fully restored..</p>

        ]]>
  </content>
</entry>

</feed>