Cloudflare Outage History

Cloudflare partial outage View live status →

Cloudflare had 335 outages in the last 2 years totaling 71h 0m of downtime — averaging 14 incidents per month.

There were 335 Cloudflare outages since April 3, 2026 totaling 71h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.cloudflarestatus.com

Minor August 5, 2026

Web Analytics Configuration issues

Detected by Pingoru
Aug 05, 2026, 03:09 PM UTC
Resolved
Aug 05, 2026, 05:12 PM UTC
Duration
2h 2m
Affected: Web Analytics
Timeline · 3 updates
  1. investigating Aug 05, 2026, 03:09 PM UTC

    Cloudflare is investigating issues with configuration changes for Cloudflare Web Analytics and rum beacon not taking effect or showing errors. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.

  2. monitoring Aug 05, 2026, 04:57 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 05, 2026, 05:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 5, 2026

Cloudflare Gateway Email List policy issues

Detected by Pingoru
Aug 05, 2026, 02:28 PM UTC
Resolved
Aug 05, 2026, 04:20 PM UTC
Duration
1h 52m
Affected: Gateway
Timeline · 5 updates
  1. investigating Aug 05, 2026, 02:28 PM UTC

    Cloudflare is aware of and investigating an issue whereby customers using Gateway email lists in their DNS policies are not being enforced. No other impact is implied. More updates to follow shortly.

  2. identified Aug 05, 2026, 02:28 PM UTC

    The issue has been identified and a fix is being implemented.

  3. investigating Aug 05, 2026, 03:24 PM UTC

    We are currently investigating this issue.

  4. monitoring Aug 05, 2026, 03:36 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Aug 05, 2026, 04:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 5, 2026

Cloudflare Workers and Pages Assets Uploads issues

Detected by Pingoru
Aug 05, 2026, 08:02 AM UTC
Resolved
Aug 05, 2026, 08:42 AM UTC
Duration
39m
Affected: PagesWorkers Assets
Timeline · 4 updates
  1. investigating Aug 05, 2026, 08:02 AM UTC

    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.

  2. identified Aug 05, 2026, 08:15 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 05, 2026, 08:26 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 05, 2026, 08:42 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 5, 2026

Managed Challenge Issues for China Network

Detected by Pingoru
Aug 05, 2026, 04:17 AM UTC
Resolved
Aug 05, 2026, 06:06 AM UTC
Duration
1h 48m
Affected: Challenge PlatformFirewall
Timeline · 5 updates
  1. investigating Aug 05, 2026, 04:17 AM UTC

    Cloudflare is investigating an increased Managed Challenge errors in China. Other regions are unaffected. We are working to analyse and mitigate this problem. More updates to follow shortly.

  2. investigating Aug 05, 2026, 04:34 AM UTC

    We are continuing to investigate this issue. This may impact customers using China Network outside of China.

  3. identified Aug 05, 2026, 04:51 AM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Aug 05, 2026, 05:54 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Aug 05, 2026, 06:06 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 4, 2026

Elevated R2 error rates and latency

Detected by Pingoru
Aug 04, 2026, 08:51 PM UTC
Resolved
Aug 04, 2026, 10:58 PM UTC
Duration
2h 6m
Affected: R2
Timeline · 3 updates
  1. investigating Aug 04, 2026, 08:51 PM UTC

    Cloudflare is aware of, and investigating an issue with elevated R2 error rates and latency for R2 buckets located in Oceania

  2. identified Aug 04, 2026, 10:14 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Aug 04, 2026, 10:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 4, 2026

502 errors observed around Singapore, Jakarta and Bangkok

Detected by Pingoru
Aug 04, 2026, 06:38 PM UTC
Resolved
Aug 04, 2026, 07:53 PM UTC
Duration
1h 14m
Affected: CDN/Cache
Timeline · 4 updates
  1. investigating Aug 04, 2026, 06:38 PM UTC

    Cloudflare is investigating elevated 502 errors around Singapore, Jakarta and Bangkok. Further detail will be provided as more information becomes available.

  2. identified Aug 04, 2026, 07:23 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 04, 2026, 07:46 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 04, 2026, 07:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 4, 2026

Cloudflare Workers deployment Issues

Detected by Pingoru
Aug 04, 2026, 01:56 AM UTC
Resolved
Aug 04, 2026, 03:03 AM UTC
Duration
1h 6m
Affected: Workers
Timeline · 3 updates
  1. investigating Aug 04, 2026, 01:56 AM UTC

    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.

  2. identified Aug 04, 2026, 02:30 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Aug 04, 2026, 03:03 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 4, 2026

Network Performance Issues in Istanbul

Detected by Pingoru
Aug 04, 2026, 01:07 AM UTC
Resolved
Aug 03, 2026, 10:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Aug 04, 2026, 01:07 AM UTC

    Cloudflare identified and resolved an issue causing an increased level of network errors in Istanbul, Turkey (IST) from 3rd August 2026 21:13 UTC to 21:32 UTC.

Read the full incident report →

Notice August 4, 2026

Network Performance Issues in Bangalore, India

Detected by Pingoru
Aug 04, 2026, 12:58 AM UTC
Resolved
Aug 04, 2026, 01:02 AM UTC
Duration
3m
Affected: Bangalore, India - (BLR)Network
Timeline · 3 updates
  1. investigating Aug 04, 2026, 12:58 AM UTC

    Cloudflare is investigating issues with network performance in Bangalore, India (BLR). Customers routing through this location may experience request errors or failures. We are working to analyze and mitigate this problem. More updates to follow shortly.

  2. monitoring Aug 04, 2026, 12:59 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 04, 2026, 01:02 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 3, 2026

Cloudflare Workers Runtime API issues

Detected by Pingoru
Aug 03, 2026, 03:13 PM UTC
Resolved
Aug 04, 2026, 07:12 AM UTC
Duration
15h 59m
Affected: Workers
Timeline · 4 updates
  1. investigating Aug 03, 2026, 03:13 PM UTC

    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.

  2. identified Aug 03, 2026, 03:21 PM UTC

    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.

  3. monitoring Aug 04, 2026, 07:00 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 04, 2026, 07:12 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 3, 2026

Cloudflare Workers build failures

Detected by Pingoru
Aug 03, 2026, 02:20 PM UTC
Resolved
Aug 03, 2026, 04:12 PM UTC
Duration
1h 51m
Affected: Workers Builds
Timeline · 5 updates
  1. investigating Aug 03, 2026, 02:20 PM UTC

    Cloudflare is aware of and investigating an issue with Cloudflare Workers build failures which potentially impacts multiple customers. Further detail will be provided as more information becomes available.

  2. identified Aug 03, 2026, 03:22 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Aug 03, 2026, 03:38 PM UTC

    Wrokers builds are no longer failing, users may experience delays with builds.

  4. monitoring Aug 03, 2026, 04:02 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Aug 03, 2026, 04:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 3, 2026

Cloudflare Dedicated Egress in London

Detected by Pingoru
Aug 03, 2026, 11:05 AM UTC
Resolved
Aug 03, 2026, 01:23 PM UTC
Duration
2h 17m
Affected: Gateway
Timeline · 4 updates
  1. investigating Aug 03, 2026, 11:05 AM UTC

    Cloudflare is aware of, and investigating, reports that customers who have dedicated IPv4 egress IPs homed in London may be unable to reach out to the public Internet.

  2. identified Aug 03, 2026, 11:25 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 03, 2026, 01:10 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 03, 2026, 01:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 1, 2026

RealtimeKit socket connection slowness and failed meeting joins

Detected by Pingoru
Aug 01, 2026, 01:10 PM UTC
Resolved
Aug 01, 2026, 01:10 PM UTC
Duration
Timeline · 1 update
  1. resolved Aug 01, 2026, 02:44 PM UTC

    We have identified and mitigated an issue affecting RealtimeKit socket connections, which caused slowness and meeting join failures for some users. Customers were impacted from 13:10 UTC to 14:15 UTC All services have been restored, and we are continuing to monitor system performance to ensure stability.

Read the full incident report →

Notice July 31, 2026

Increased HTTP 5XX Errors in IAD

Detected by Pingoru
Jul 31, 2026, 11:00 PM UTC
Resolved
Jul 31, 2026, 11:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Aug 01, 2026, 01:05 AM UTC

    Cloudflare identified and resolved an issue causing an increased level of 5XX errors in Ashburn, US (IAD) from 31st July 2026 18:45 UTC to 23:01 UTC.

Read the full incident report →

Minor July 31, 2026

Increased HTTP Errors in London

Detected by Pingoru
Jul 31, 2026, 07:06 PM UTC
Resolved
Jul 31, 2026, 08:40 PM UTC
Duration
1h 34m
Affected: CDN/CacheLondon, United Kingdom - (LHR)
Timeline · 4 updates
  1. investigating Jul 31, 2026, 07:06 PM UTC

    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.

  2. identified Jul 31, 2026, 07:53 PM UTC

    The cause of this issue has been identified and a fix is being implemented.

  3. monitoring Jul 31, 2026, 08:22 PM UTC

    A fix has been implemented and we are currently monitoring the results.

  4. resolved Jul 31, 2026, 08:40 PM UTC

    This incident is now resolved.

Read the full incident report →

Notice July 31, 2026

Email Routing Delivery Failures to Outlook

Detected by Pingoru
Jul 31, 2026, 03:36 PM UTC
Resolved
Jul 20, 2026, 06:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Jul 31, 2026, 03:36 PM UTC

    Cloudflare is aware of email delivery failures from Email Routing to Outlook destinations during the period 20th Jul 18:02 to 31th July 14:38 UTC. This has now been resolved.

Read the full incident report →

Minor July 31, 2026

Network Performance Issues in Hamburg, Germany

Detected by Pingoru
Jul 31, 2026, 03:20 PM UTC
Resolved
Aug 01, 2026, 03:18 PM UTC
Duration
23h 58m
Affected: Hamburg, Germany - (HAM)
Timeline · 3 updates
  1. identified Jul 31, 2026, 03:20 PM UTC

    Cloudflare is investigating issues with network performance in Hamburg, Germany (HAM). Customers routing through this location may experience request errors or failures. We have identified the problem and are working on a fix.

  2. monitoring Jul 31, 2026, 04:58 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 01, 2026, 03:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 31, 2026

Cloudflare API Availability Reduced Availability

Detected by Pingoru
Jul 31, 2026, 11:51 AM UTC
Resolved
Jul 31, 2026, 01:01 PM UTC
Duration
1h 10m
Affected: AnalyticsAPIDashboardPagesWorkers
Timeline · 6 updates
  1. investigating Jul 31, 2026, 11:51 AM UTC

    Cloudflare is aware that the Analytics API Availability is experiencing reduced availability . This affects timely delivery of customer data.

  2. investigating Jul 31, 2026, 12:25 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 31, 2026, 12:37 PM UTC

    Cloudflare is aware that this is also impacting on Pages and Worker builds. We are continuing to investigate.

  4. monitoring Jul 31, 2026, 12:43 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. monitoring Jul 31, 2026, 12:46 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Jul 31, 2026, 01:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 31, 2026

Increased HTTP 5xx Errors for us-east-1-aws

Detected by Pingoru
Jul 31, 2026, 02:01 AM UTC
Resolved
Jul 31, 2026, 04:19 AM UTC
Duration
2h 18m
Affected: Network
Timeline · 4 updates
  1. investigating Jul 31, 2026, 02:01 AM UTC

    Cloudflare is investigating an increased level of intermittent HTTP 5xx errors for customers using AWS region us-east-1-aws. We are working to analyse and mitigate this problem. More updates to follow shortly.

  2. identified Jul 31, 2026, 02:34 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 31, 2026, 04:08 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 31, 2026, 04:19 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 30, 2026

Page Shield Email Notification Issues

Detected by Pingoru
Jul 30, 2026, 01:16 PM UTC
Resolved
Jul 30, 2026, 02:52 PM UTC
Duration
1h 36m
Affected: NotificationsPage Shield
Timeline · 3 updates
  1. investigating Jul 30, 2026, 01:16 PM UTC

    We are investigating an issue where Page Shield email notifications are not containing the correct data for some customers. Our engineering team is currently working on a fix to restore accurate alert delivery. We will provide updates as soon as more information is available.

  2. monitoring Jul 30, 2026, 02:23 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 30, 2026, 02:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 30, 2026

Possible Network Congestion in North America region

Detected by Pingoru
Jul 30, 2026, 05:48 AM UTC
Resolved
Jul 30, 2026, 10:08 AM UTC
Duration
4h 20m
Affected: Network
Timeline · 4 updates
  1. investigating Jul 30, 2026, 05:48 AM UTC

    Cloudflare is observing possible network congestion in the North America region. Customers may see elevated latency and connectivity issues. We are working to mitigate impact to Internet users in this region.

  2. monitoring Jul 30, 2026, 07:51 AM UTC

    Cloudflare identified that the Network degradation was due to maintenance conducted by fiber providers. The congestion has been alleviated by rerouting traffic. We are currently monitoring the situation and will follow up with more updates shortly.

  3. monitoring Jul 30, 2026, 07:57 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jul 30, 2026, 10:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 29, 2026

Cloudflare Workers — Errors Deploying Workers Scripts

Detected by Pingoru
Jul 29, 2026, 08:03 PM UTC
Resolved
Jul 29, 2026, 08:31 PM UTC
Duration
27m
Affected: Workers
Timeline · 3 updates
  1. identified Jul 29, 2026, 08:03 PM UTC

    Cloudflare is investigating an issue where a subset of Workers script deployments are failing with errors. Customers may experience failures when attempting to deploy a Worker script via Wrangler or the Workers API. Workers that are already deployed and running in production are not affected. A fix is being prepared.

  2. identified Jul 29, 2026, 08:04 PM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Jul 29, 2026, 08:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 29, 2026

Sensitive Data Detection Configuration Issue

Detected by Pingoru
Jul 29, 2026, 03:09 PM UTC
Resolved
Jul 29, 2026, 04:23 PM UTC
Duration
1h 14m
Affected: Dashboard
Timeline · 4 updates
  1. investigating Jul 29, 2026, 03:09 PM UTC

    Cloudflare is investigating an issue with the Sensitive Data Detection feature in the Cloudflare Dashboard. Customers may be unable to enable Sensitive Data Detection via the Security settings toggle. Other dashboard features and security services remain unaffected. We are working to identify and mitigate this problem. More updates to follow shortly.

  2. identified Jul 29, 2026, 03:32 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 29, 2026, 04:15 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 29, 2026, 04:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 29, 2026

Possible Network Congestion between Singapore and Tokyo

Detected by Pingoru
Jul 29, 2026, 08:29 AM UTC
Resolved
Jul 29, 2026, 11:45 AM UTC
Duration
3h 16m
Timeline · 4 updates
  1. investigating Jul 29, 2026, 08:29 AM UTC

    Cloudflare is observing possible network congestion between Singapore and Tokyo. We are working to mitigate impact to Internet users in this region.

  2. identified Jul 29, 2026, 10:29 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 29, 2026, 11:44 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 29, 2026, 11:45 AM UTC

    This incident has been resolved.

Read the full incident report →