WhoSubscribed Status - Incident history https://whosubscribed.instatus.com WhoSubscribed Thu, 17 Sep 2026 23:37:18 +0000 Increased Errors for Durable Objects and Downstream Services in Asia Pacific (APAC) Region Type: Incident Duration: 3 days, 4 hours and 45 minutes Affected Components: Database Sep 17, 23:37:18 GMT+0 - Investigating - Cloudflare is investigating an issue causing elevated error rates for Durable Objects and downstream services in the Asia Pacific region. We are working to mitigate this issue and will provide additional updates shortly. Sep 18, 00:45:48 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Sep 18, 00:54:03 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 days, 4 hours and 45 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>23:37:18</var> GMT+0</small><br><strong>Investigating</strong> - Cloudflare is investigating an issue causing elevated error rates for Durable Objects and downstream services in the Asia Pacific region. We are working to mitigate this issue and will provide additional updates shortly..</p> <p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>00:45:48</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results..</p> <p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>00:54:03</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 17 Sep 2026 23:37:18 +0000 https://whosubscribed.instatus.com/incident/cmu668bip8yd80kmhsbnr4sq4 https://whosubscribed.instatus.com/incident/cmu668bip8yd80kmhsbnr4sq4 Workers Cron Triggers degraded Type: Incident Affected Components: Workers Sep 12, 02:25:01 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Sep 9, 19:17:26 GMT+0 - Investigating - Workers Cron Triggers may not execute or may be delayed in executing. Updates to Workers Cron Triggers may take some time to take effect. Sep 9, 19:18:25 GMT+0 - Identified - The issue has been identified and a fix is being implemented. Sep 12, 03:34:16 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components:

<p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>02:25:01</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results..</p> <p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>19:17:26</var> GMT+0</small><br><strong>Investigating</strong> - Workers Cron Triggers may not execute or may be delayed in executing. Updates to Workers Cron Triggers may take some time to take effect..</p> <p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>19:18:25</var> GMT+0</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented..</p> <p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>03:34:16</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 9 Sep 2026 19:17:26 +0000 https://whosubscribed.instatus.com/incident/cmtuhf5am6xhf0rqjuovliqrp https://whosubscribed.instatus.com/incident/cmtuhf5am6xhf0rqjuovliqrp Cloudflare Workers Issues in Narita Type: Incident Duration: 3 days, 9 hours and 44 minutes Affected Components: Workers Sep 2, 01:02:41 GMT+0 - Investigating - Cloudflare is investigating an increased level of errors for customers running Workers scripts in Narita. We are working to analyse and mitigate this problem. More updates to follow shortly. Sep 2, 02:10:36 GMT+0 - Identified - The issue has been identified and a fix is being implemented. Sep 2, 02:24:25 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 days, 9 hours and 44 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>01:02:41</var> GMT+0</small><br><strong>Investigating</strong> - Cloudflare is investigating an increased level of errors for customers running Workers scripts in Narita. We are working to analyse and mitigate this problem. More updates to follow shortly..</p> <p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>02:10:36</var> GMT+0</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented..</p> <p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>02:24:25</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 2 Sep 2026 01:02:41 +0000 https://whosubscribed.instatus.com/incident/cmtje827yb4dk0kpwuawi8al5 https://whosubscribed.instatus.com/incident/cmtje827yb4dk0kpwuawi8al5 Requests from wrangler or other OAuth clients may experience elevated errors Type: Incident Duration: 8 days, 15 hours and 1 minute Affected Components: Database Sep 1, 08:38:51 GMT+0 - Investigating - We are currently investigating this issue. Sep 1, 08:42:47 GMT+0 - Investigating - We are continuing to investigate this issue. Sep 1, 09:41:17 GMT+0 - Identified - The issue has been identified and a fix is being implemented. Sep 1, 12:05:52 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 8 days, 15 hours and 1 minute

Affected Components:

<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>08:38:51</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this issue..</p> <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>08:42:47</var> GMT+0</small><br><strong>Investigating</strong> - We are continuing to investigate this issue..</p> <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>09:41:17</var> GMT+0</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented..</p> <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>12:05:52</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 1 Sep 2026 08:38:51 +0000 https://whosubscribed.instatus.com/incident/cmtif7sbt9f190kpwqm9zg14i https://whosubscribed.instatus.com/incident/cmtif7sbt9f190kpwqm9zg14i Durable Objects and Downstream Service Errors Type: Incident Duration: 3 days, 9 hours and 59 minutes Affected Components: Database Aug 26, 20:50:07 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Aug 26, 21:30:32 GMT+0 - Resolved - This incident has been resolved. Aug 26, 20:08:32 GMT+0 - Investigating - Cloudflare is investigating issues causing an increase of errors for Durable Objects and downstream services in ENAM region. We are working to analyze and mitigate this problem. More updates to follow shortly. Type: Incident

Duration: 3 days, 9 hours and 59 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>20:50:07</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results..</p> <p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>21:30:32</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>20:08:32</var> GMT+0</small><br><strong>Investigating</strong> - Cloudflare is investigating issues causing an increase of errors for Durable Objects and downstream services in ENAM region. We are working to analyze and mitigate this problem. More updates to follow shortly..</p> ]]> Wed, 26 Aug 2026 20:08:32 +0000 https://whosubscribed.instatus.com/incident/cmtaj1iy5jf790kmg1fx2qovm https://whosubscribed.instatus.com/incident/cmtaj1iy5jf790kmg1fx2qovm Increased Latency Type: Incident Duration: 14 days, 14 hours and 14 minutes Affected Components: Cache Aug 24, 20:38:27 GMT+0 - Investigating - Cloudflare is investigating an issue which may result in latency increases for a subset of requests. Aug 24, 22:24:02 GMT+0 - Identified - We have identified the cause of this issue and are implementing a fix. Aug 25, 08:50:16 GMT+0 - Identified - We are continuing to work on a fix for this issue. Aug 25, 14:37:40 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Aug 25, 14:52:41 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 14 days, 14 hours and 14 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>20:38:27</var> GMT+0</small><br><strong>Investigating</strong> - Cloudflare is investigating an issue which may result in latency increases for a subset of requests..</p> <p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>22:24:02</var> GMT+0</small><br><strong>Identified</strong> - We have identified the cause of this issue and are implementing a fix..</p> <p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>08:50:16</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this issue..</p> <p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>14:37:40</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results..</p> <p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>14:52:41</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 24 Aug 2026 20:38:27 +0000 https://whosubscribed.instatus.com/incident/cmt7pew51dpza0kmg7j8ygh1w https://whosubscribed.instatus.com/incident/cmt7pew51dpza0kmg7j8ygh1w Increased HTTP 5xx Errors in Chicago Type: Incident Duration: 2 days, 18 hours and 2 minutes Affected Components: Cache Aug 24, 05:47:34 GMT+0 - Investigating - Cloudflare is investigating an increased level of HTTP 5xx errors in Chicago. We are working to analyze and mitigate this problem. More updates to follow shortly. Aug 24, 06:53:37 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 days, 18 hours and 2 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>05:47:34</var> GMT+0</small><br><strong>Investigating</strong> - Cloudflare is investigating an increased level of HTTP 5xx errors in Chicago. We are working to analyze and mitigate this problem. More updates to follow shortly..</p> <p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>06:53:37</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 24 Aug 2026 05:47:34 +0000 https://whosubscribed.instatus.com/incident/cmt6tfulzf11z0rmgyrida5yt https://whosubscribed.instatus.com/incident/cmt6tfulzf11z0rmgyrida5yt DO and D1 are degraded in Hong Kong and Singapore Type: Incident Duration: 11 days, 10 hours and 24 minutes Affected Components: Database Aug 24, 03:53:58 GMT+0 - Investigating - Some DOs and D1 databases may be experiencing issues in Hong Kong and Singapore. We are working to analyse and mitigate this problem. More updates to follow shortly. Aug 24, 06:42:39 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Aug 24, 08:28:22 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 11 days, 10 hours and 24 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>03:53:58</var> GMT+0</small><br><strong>Investigating</strong> - Some DOs and D1 databases may be experiencing issues in Hong Kong and Singapore. We are working to analyse and mitigate this problem. More updates to follow shortly..</p> <p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>06:42:39</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results..</p> <p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>08:28:22</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 24 Aug 2026 03:53:58 +0000 https://whosubscribed.instatus.com/incident/cmt6piea1et050rmg70iyving https://whosubscribed.instatus.com/incident/cmt6piea1et050rmg70iyving Durable Objects and Downstream Service Errors Type: Incident Duration: 2 days, 11 hours and 43 minutes Affected Components: Database Aug 20, 16:48:25 GMT+0 - Investigating - Cloudflare is investigating issues causing an increase of errors for Durable Objects and downstream services in ENAM region. We are working to analyse and mitigate this problem. More updates to follow shortly. Aug 20, 16:56:11 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Aug 20, 17:48:08 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 days, 11 hours and 43 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 20</var>, <var data-var='time'>16:48:25</var> GMT+0</small><br><strong>Investigating</strong> - Cloudflare is investigating issues causing an increase of errors for Durable Objects and downstream services in ENAM region. We are working to analyse and mitigate this problem. More updates to follow shortly..</p> <p><small>Aug <var data-var='date'> 20</var>, <var data-var='time'>16:56:11</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results..</p> <p><small>Aug <var data-var='date'> 20</var>, <var data-var='time'>17:48:08</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 20 Aug 2026 16:48:25 +0000 https://whosubscribed.instatus.com/incident/cmt1rfnef2zzl0kmgk390ciym https://whosubscribed.instatus.com/incident/cmt1rfnef2zzl0kmgk390ciym Cloudflare Workers and Pages Assets Uploads issues Type: Incident Duration: 1 day, 15 hours and 42 minutes Affected Components: Static Website Servers Aug 5, 08:42:17 GMT+0 - Resolved - This incident has been resolved. Aug 5, 08:26:18 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Aug 5, 08:02:34 GMT+0 - Investigating - Cloudflare is investigating an issue where uploads for Pages and Workers Assets have reduced availability. We are working to analyse and mitigate this problem. More updates to follow shortly. Aug 5, 08:15:03 GMT+0 - Identified - The issue has been identified and a fix is being implemented. Type: Incident

Duration: 1 day, 15 hours and 42 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>08:42:17</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>08:26:18</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results..</p> <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>08:02:34</var> GMT+0</small><br><strong>Investigating</strong> - Cloudflare is investigating an issue where uploads for Pages and Workers Assets have reduced availability. We are working to analyse and mitigate this problem. More updates to follow shortly..</p> <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>08:15:03</var> GMT+0</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented..</p> ]]> Wed, 5 Aug 2026 08:02:34 +0000 https://whosubscribed.instatus.com/incident/cmt0ri3jf0v250rmgar3vvgh7 https://whosubscribed.instatus.com/incident/cmt0ri3jf0v250rmgar3vvgh7 502 errors observed around Singapore, Jakarta and Bangkok Type: Incident Duration: 3 days, 2 hours and 16 minutes Affected Components: Cache Aug 4, 19:46:36 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Aug 4, 19:23:49 GMT+0 - Identified - The issue has been identified and a fix is being implemented. Aug 4, 18:38:43 GMT+0 - Investigating - Cloudflare is investigating elevated 502 errors around Singapore, Jakarta and Bangkok. Further detail will be provided as more information becomes available. Aug 4, 19:53:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 days, 2 hours and 16 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>19:46:36</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>19:23:49</var> GMT+0</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>18:38:43</var> GMT+0</small><br><strong>Investigating</strong> - Cloudflare is investigating elevated 502 errors around Singapore, Jakarta and Bangkok. Further detail will be provided as more information becomes available..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>19:53:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 4 Aug 2026 18:38:43 +0000 https://whosubscribed.instatus.com/incident/cmt0ri3jg0v280rmgl8btj78m https://whosubscribed.instatus.com/incident/cmt0ri3jg0v280rmgl8btj78m Cloudflare Workers deployment Issues Type: Incident Duration: 2 days, 18 hours and 40 minutes Affected Components: Workers Aug 4, 02:30:22 GMT+0 - Identified - The issue has been identified and a fix is being implemented. Aug 4, 01:56:19 GMT+0 - Investigating - Cloudflare is aware that deploying Workers that the nodejs_compat compatibility flag and a compatibility date on or after 2026-08-04 is being disallowed. This is impacting Workers and Workers for Platforms. We are working on relaxing this assertion. To avoid this error, remove the nodejs_compat compatibility flag from your Worker. Aug 4, 03:03:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 days, 18 hours and 40 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>02:30:22</var> GMT+0</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>01:56:19</var> GMT+0</small><br><strong>Investigating</strong> - Cloudflare is aware that deploying Workers that the nodejs_compat compatibility flag and a compatibility date on or after 2026-08-04 is being disallowed. This is impacting Workers and Workers for Platforms. We are working on relaxing this assertion. To avoid this error, remove the nodejs_compat compatibility flag from your Worker..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>03:03:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 4 Aug 2026 01:56:19 +0000 https://whosubscribed.instatus.com/incident/cmt0ri3jf0v260rmgs10xx5kd https://whosubscribed.instatus.com/incident/cmt0ri3jf0v260rmgs10xx5kd Cloudflare Workers Runtime API issues Type: Incident Duration: 8 days, 23 hours and 7 minutes Affected Components: Workers Aug 3, 15:21:54 GMT+0 - Identified - Workers runtime: Temporal global exposed with an incorrect clock Since 2026-07-30, the Workers runtime has exposed a global Temporal object that was not intended to be available. Its clock is wrong: Temporal.Now reports 1970-01-01 rather than the current time. Date and Date.now() are unaffected and report the correct time. This can affect Workers that install a Temporal polyfill only when no native Temporal is detected. On those Workers, the polyfill stopped being installed and time-dependent logic began computing against 1970 — for example, tokens minted with an issue time of 0 and an expiry in 1970, incorrect TTLs, or incorrect date arithmetic. No error is raised when this happens. Aug 4, 07:00:12 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Aug 4, 07:12:40 GMT+0 - Resolved - This incident has been resolved. Aug 3, 15:13:33 GMT+0 - Investigating - Cloudflare is aware of an issue with the latest Workers Runtime API release that exposes native Temporal with clock stuck at epoch 0. Updates to follow. Type: Incident

Duration: 8 days, 23 hours and 7 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>15:21:54</var> GMT+0</small><br><strong>Identified</strong> - Workers runtime: Temporal global exposed with an incorrect clock Since 2026-07-30, the Workers runtime has exposed a global Temporal object that was not intended to be available. Its clock is wrong: Temporal.Now reports 1970-01-01 rather than the current time. Date and Date.now() are unaffected and report the correct time. This can affect Workers that install a Temporal polyfill only when no native Temporal is detected. On those Workers, the polyfill stopped being installed and time-dependent logic began computing against 1970 — for example, tokens minted with an issue time of 0 and an expiry in 1970, incorrect TTLs, or incorrect date arithmetic. No error is raised when this happens..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>07:00:12</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>07:12:40</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>15:13:33</var> GMT+0</small><br><strong>Investigating</strong> - Cloudflare is aware of an issue with the latest Workers Runtime API release that exposes native Temporal with clock stuck at epoch 0. Updates to follow..</p> ]]> Mon, 3 Aug 2026 15:13:33 +0000 https://whosubscribed.instatus.com/incident/cmt0ri3jl0v2a0rmglo704ye8 https://whosubscribed.instatus.com/incident/cmt0ri3jl0v2a0rmglo704ye8 Increased HTTP Errors in London Type: Incident Duration: 3 days, 22 hours and 24 minutes Affected Components: Cache Jul 31, 19:53:13 GMT+0 - Identified - The cause of this issue has been identified and a fix is being implemented. Jul 31, 20:40:43 GMT+0 - Resolved - This incident is now resolved. Jul 31, 19:06:19 GMT+0 - Investigating - Cloudflare is investigating an increased level of HTTP errors affecting a subset of customers. We are working to analyze and mitigate this problem. More updates to follow shortly. Jul 31, 20:22:27 GMT+0 - Monitoring - A fix has been implemented and we are currently monitoring the results. Type: Incident

Duration: 3 days, 22 hours and 24 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>19:53:13</var> GMT+0</small><br><strong>Identified</strong> - The cause of this issue has been identified and a fix is being implemented..</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>20:40:43</var> GMT+0</small><br><strong>Resolved</strong> - This incident is now resolved..</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>19:06:19</var> GMT+0</small><br><strong>Investigating</strong> - Cloudflare is investigating an increased level of HTTP errors affecting a subset of customers. We are working to analyze and mitigate this problem. More updates to follow shortly..</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>20:22:27</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been implemented and we are currently monitoring the results..</p> ]]> Fri, 31 Jul 2026 19:06:19 +0000 https://whosubscribed.instatus.com/incident/cmt0ri3ww0v3y0rmgt4j39pfs https://whosubscribed.instatus.com/incident/cmt0ri3ww0v3y0rmgt4j39pfs Cloudflare API Availability Reduced Availability Type: Incident Duration: 2 days, 22 hours and 52 minutes Affected Components: Static Website Servers, Workers Jul 31, 12:46:20 GMT+0 - Monitoring - We are continuing to monitor for any further issues. Jul 31, 12:25:44 GMT+0 - Investigating - We are continuing to investigate this issue. Jul 31, 11:51:07 GMT+0 - Investigating - Cloudflare is investigating reduced availability with Cloudflare Dashboard and related APIs. These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge. Customers using the Dashboard / Cloudflare APIs are impacted as requests might fail and/or errors may be displayed. Jul 31, 12:43:57 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Jul 31, 12:37:35 GMT+0 - Investigating - Cloudflare is aware that this is also impacting on Pages and Worker builds. We are continuing to investigate. Jul 31, 13:01:59 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 days, 22 hours and 52 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>12:46:20</var> GMT+0</small><br><strong>Monitoring</strong> - We are continuing to monitor for any further issues..</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>12:25:44</var> GMT+0</small><br><strong>Investigating</strong> - We are continuing to investigate this issue..</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>11:51:07</var> GMT+0</small><br><strong>Investigating</strong> - Cloudflare is investigating reduced availability with Cloudflare Dashboard and related APIs. These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge. Customers using the Dashboard / Cloudflare APIs are impacted as requests might fail and/or errors may be displayed..</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>12:43:57</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results..</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>12:37:35</var> GMT+0</small><br><strong>Investigating</strong> - Cloudflare is aware that this is also impacting on Pages and Worker builds. We are continuing to investigate..</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>13:01:59</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 31 Jul 2026 11:51:07 +0000 https://whosubscribed.instatus.com/incident/cmt0ri3x40v420rmgzmjmtf51 https://whosubscribed.instatus.com/incident/cmt0ri3x40v420rmgzmjmtf51