Cloudflare Outage History

Cloudflare resolved an issue with network performance for our Sofia (SOF) facility which occurred today, 2026-10-08, from approximately 21:35 to 21:50 UTC. Customers may have observed elevated latency and/or error rates from this facility during this period.

Cloudflare resolved an issue with network performance for our Sofia (SOF) facility which occurred today, 2026-10-08, from approximately 21:35 to 21:50 UTC. Customers may have observed elevated latency and/or error rates from this facility during this period.

Cloudflare resolved an issue with network performance for our Kochi (COK) facility which occurred today, 2026-10-08, between approximately 14:00 and 17:00 UTC. Customers may have observed elevated latency and/or error rates from this facility during this period.

This incident has been resolved.

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

Cloudflare is investigating issues with Cloudflare Dashboard 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 Cloudflare APIs are impacted as requests might fail and/or errors may be displayed.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

Cloudflare is aware of an issue with network routing to Microsoft Azure, which is causing errors for requests directed to origins hosted on that service. The team is actively working on remediation.

This incident has been resolved.

We are continuing to monitor for any further issues.

Cloudflare is aware of and is investigating an issue with Keyless SSL, which results in TLS handshake failures, only affecting RSA Keyless SSL with specific key backend configurations. We are working to resolve this. Updates to follow.

This incident has been resolved.

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

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

Cloudflare is investigating an issue affecting API Shield JWT validation for customers using symmetric keying material. Our team is actively working on restoring normal service.

This incident has been resolved.

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

We are investigating an issue leading to decreased availability for Durable Objects and dependent services in the Eastern North America region. Our engineering team is actively working to mitigate the impact, and further updates will be provided as soon as more information becomes available.

Cloudflare investigated reports of increased latency affecting requests for cacheable assets across multiple locations between 09:30 and 11:10 UTC. The issue is now resolved.

This incident has been resolved.

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

Cloudflare is aware of and investigating an issue with Cloudflare Workers build failing to start. We are working to analyse and mitigate this problem. More updates to follow shortly.

This incident has been resolved.

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

Cloudflare is investigating issues causing an increase of errors for Durable Objects and R2 as a result in Amsterdam. We are working to analyse and mitigate this problem. More updates to follow shortly.

This incident has been resolved.

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

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

Cloudflare is investigating issues with network performance in Madrid (MAD). We are working to analyse and mitigate this problem. More updates to follow shortly.

This incident has been resolved.

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

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

This incident has been resolved.

We are continuing to investigate this issue.

Cloudflare is investigating possible network congestion in Los Angeles (LAX) affecting Vectorize, Durable Objects, R2, Hyperdrive, Stream, and Cloudchamber. We are working to mitigate the impact to Internet users in the region.

This incident has been resolved.

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

Cloudflare is investigating delays in applying changes to account member roles and permissions. Recently updated permissions may not be immediately reflected in some Cloudflare services. We are working to mitigate this issue.

Between 00:45- 01:35 UTC, Cloudflare WARP and Zero Trust users in Newark, NJ, may have experienced connectivity issues or a degraded Internet experience.

This incident has been resolved.

Cloudflare continues to mitigate intermittent connectivity degradation for a small subset of customers caused by significant degradation of capacity in the region.

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

Since September 21, 2026 at 02:20 UTC, multiple subsea cable outages have caused congestion between Tokyo and Singapore datacenters. We have rerouted traffic to reduce impact and are working with third-party vendors to restore capacity.

Cloudflare engineering determined that customers didn't actually experience elevated levels of OTP failures. The rise in failures was an isolated incident without widespread impact.

We are investigating an issue causing a high percentage of Access One Time Pin emails to fail. All other authentication methods are operating as normal.

This incident has been resolved.

We are investigating Flux hotswap models that haven't made progress since last Thursday, 2026-09-24.

This incident has been resolved.

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

We are continuing to investigate this issue.

Cloudflare is investigating degraded availability impacting Cloudflare CASB and policy sharing between accounts in Cloudflare Organizations. CASB findings may be delayed, and changes to shared policies may take longer to propagate to destination accounts.

This incident has been resolved.

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

Cloudflare is investigating issues causing an increase of errors for Durable Objects .We are working to analyse and mitigate this problem. More updates to follow shortly.

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

Cloudflare is aware of and investigating an issue impacting some customers where new Workflows instances may be stuck in a Queued state. More updates to follow shortly.

This incident has been resolved.

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

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

Cloudflare is investigating an issue with editing rules in the Dashboard. Customers may see errors when trying to edit or create a Compression rule. Existing Compression rules are unaffected. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.

Cloudflare observed and resolved delays with Secondary DNS zone transfers. Customers may have experienced delays when record updates made on primary nameservers propagate to Cloudflare Secondary DNS as well as in the other direction. DNS resolution and edge proxying remain unaffected and continue to function normally. Impact on DNS transfers may have been observed today, from 00:05:10 UTC to 01:52:54.

This incident has been resolved.

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

Cloudflare is investigating issues with Browser Isolation's session data sync. Customers that use Browser Isolation may observe errors on acquiring a browser stating that browser storage is unavailable, and they will need to sign into web apps again. They will continue to be able to use browsers during this time.

The impacted backend has been redeployed, and all related services should now be back up and running. There may be some increased latency as they continue to come online.

We have a backend component that entered an unexpected reboot, causing issues for services downstream.

This incident has been resolved.

Queue levels & latency are returning to normal

Customers may experience delays starting Cloudflare Workers builds.

This incident has been resolved.

We have applied a fix and are actively monitoring.

Cloudflare engineering is investigating an issue causing a delay in configuration updates. This includes applications and policy updates. Authentication and policy enforcement are not impacted.

This incident has now been resolved - Customers with BYOIP addresses were unable to update their BGP prefixes, including advertising or withdrawing prefixes. Customers making changes to their address maps may also have experienced delays.

We are currently investigating an issue where customers with BYOIP addresses will be unable to update their BGP prefixes, including advertising or withdrawing prefixes.

This incident has been resolved.

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

A known issue affected authentication for a small percentage of requests to the API and R2. The issue was identified on Sep 22 at 13:30 UTC, and major impact was mitigated at 19:00 UTC. Our team is actively working to resolve the residual impact.

This incident has been resolved.

We have identified an issue causing unexpected errors when creating or updating configurations using any or all expressions in the http_response_cache_settings. This issue strictly affects API operations; existing active configurations and live traffic are not impacted. A fix is currently being deployed, and we will provide an update once the rollout is complete.

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

Cloudflare is investigating an issue where Cloudflare One Client customers are incorrectly challenged while visiting some websites.

This incident has been resolved.

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

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

Cloudflare is aware of, and investigating an issue with Durable Objects which potentially impacts a subset of customers. Durable Objects are experiencing an elevated level of errors. We are currently investigating this issue.

This incident has been resolved.

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

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

Cloudflare is investigating issues with R2 buckets in the Australian Eastern Coast region.

This incident has been resolved.

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

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

Cloudflare is aware of, and investigating, an issue which impacts DNS over HTTPS requests to 1.1.1.1 for Families (1.1.1.2 and 1.1.1.3) Authoritative DNS provided by Cloudflare is unaffected. Further detail will be provided as more information becomes available.

We have identified and applied an effective fix for this issue. This incident is now resolved.

We are currently investigating an issue where Bot Management configuration updates are not propagating to the edge. Our engineering team is aware of the issue and is actively working on a resolution. The running Bot Configuration at the Edge is not impacted. We will provide further updates as soon as we have more information.

This incident has been resolved.

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

We are investigating an issue where some Stream Live customers are receiving errors when playing back live broadcasts with LL-HLS enabled.

We investigated and resolved reports of connectivity issues in Los Angeles. Traffic congestion between in our Los Angeles (LAX) colo, which resulted in intermittent packet drops between 13:37 UTC and 14:49 UTC today. The capacity constraint has been addressed and traffic flow has returned to normal.

This incident has been resolved.

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

Cloudflare is monitoring the restoration of Workers and Durable Objects analytics visibility for all Fedramp High customers. While the underlying data remains intact, affected datasets were not being correctly returned by our analytics dashboard and GraphQL API since June 11th. Services are currently recovering as we propagate the fix.

Cloudflare verified and resolved performance issues in our San Jose (SJC-A) data center. Users in the region may have experienced increased latency or connectivity issues between 07:20 and 08:20 UTC today.

This incident has been resolved.

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

Cloudflare is observing network connectivity issues in LHR, London. We are working to analyse and mitigate this problem. More updates to follow shortly