Cloudflare Outage History

Between 14:55 - 15:24 UTC customers reaching Karachi (KHI), Pakistan would have experienced an elevated latency and increased HTTP 5xx errors

This incident has been resolved.

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

Customers leveraging R2 in the Western North American region may experience increase latency and/or error rates.

This incident has been resolved.

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

Cloudflare is investigating issues when transforming images from R2 buckets. Customers may see errors when serving transformations on free zones. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.

An issue in the Dashboard's Session Management systems resulted in a subset of users not being able to log into the Dashboard or being unexpectedly logged out.

Between 20:00 and 20:36 UTC, R2 buckets in the APAC region experienced elevated latency and timeouts.

This incident is now resolved.

We have identified the cause of this issue and implemented a fix. We are currently monitoring the results.

Cloudflare is aware of and investigating an issue impacting the Analytics Engine API. Users may be experiencing an increase of 500 errors when querying. We are working to analyze and mitigate this problem. More updates to follow shortly.

This incident has been resolved.

Cloudflare is investigating issues with our Bot Management feature. Customers may experience a decrease in the percentage of traffic detected as automated since JSD detections have been turned off due to false positives since Feb 18 2026. We are working to mitigate this problem. More updates to follow shortly.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

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

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

Users might experience higher 429 errors

This incident has been resolved.

Cloudflare has enabled the remaining IP prefixes to their previous state. We are continuing to monitor for additional impact.

Cloudflare continues working to mitigate impact from the last subset of prefixes which were withdrawn and were unable to be mitigated through toggling advertisement on the dashboard.

Cloudflare is working to mitigate impact from the last subset of prefixes which were withdrawn and were unable to be mitigated through toggling advertisement on the dashboard.

Cloudflare is continuing to restore prefixes to their previous state. Any customer who withdrew their IPs as a result of this incident will see their IPs withdrawn upon full impact mitigation. Customers are still able to restore service from the dashboard by readvertising their IPs. Cloudflare is aware that some customers are unable to reload their IPs through the dashboard and are working on a fix.

Cloudflare is continuing to restore prefixes to their previous state. Customers are still able to restore service from the dashboard by readvertising their IPs. Refer to: https://developers.cloudflare.com/magic-transit/how-to/advertise-prefixes/#advertise-or-withdraw-a-bgp-prefix Cloudflare is aware that some customers are unable to reload their IPs through the dashboard and are working on a fix.

Cloudflare is continuing to work on restoring service for impacted customers to what it was before the outage. Customers can self-mitigate by readvertising their prefixes in the dashboard. Refer to: https://developers.cloudflare.com/magic-transit/how-to/advertise-prefixes/#advertise-or-withdraw-a-bgp-prefix for details on how to advertise a prefix.

Cloudflare is continuing to restore service to customers. Cloudflare has also identified a way for impacted customers to self-resolve impact by readvertising prefixes via the Cloudflare dashboard. Refer to: https://developers.cloudflare.com/magic-transit/how-to/advertise-prefixes/#advertise-or-withdraw-a-bgp-prefix for details on how to advertise a prefix.

Cloudflare has identified impact to a subset of BYOIP prefixes. Cloudflare has identified and mitigated the underlying issue and is working to restore availability to impacted advertisements.

Cloudflare is investigating issues with our services and/or network. Users may experience errors or timeouts reaching Cloudflare’s network or services. We will update this status page to clarify the scope of impact as we continue the investigation.

This incident has been resolved.

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

Customers are experiencing elevated 403 errors on 1.1.1.1 landing page. DNS resolution using Public DNS resolver 1.1.1.1 is not impacted. Cache purge and Debugging page is impacted.

This incident has been resolved.

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

Cloudflare is experiencing intermittent issues with select Durable Object invocations. This is currently only impacting our free tier customers.

This incident has been resolved.

A fix has been implemented in version 1.12.1. Customers can update via the Apple App Store.

Cloudflare has identified an issue with WARP connectivity on iOS and a fix is being implemented. Cloudflare is currently working on a new release through the App Store to fix the issue. A workaround the issue is to uninstall and reinstall the app again.

Cloudflare has identified an issue with WARP connectivity on iOS and a fix is being implemented.

Cloudflare has identified an issue with WARP connectivity on iOS and a fix is being implemented. It is possible for the latest version of the Cloudflare One Agent app on iOS to end up in a bad state where it cannot connect to Cloudflare's edge network. When the app is open and this issue is occurring, the on/off toggle will be rapidly changing between states endlessly. This is caused by a bug in app version 1.12.0. A fix has been developed, and we are working on deploying a new app version that includes it. For now, a known workaround is to uninstall then reinstall the app.

This incident has been resolved.

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

Cloudflare is investigating an increased level of HTTP 5xx errors for content served by cdnjs.cloudflare.com We are working to analyze and mitigate this problem. More updates to follow shortly.

This incident has been resolved.

Engineering have moved pending certificate orders to another certificate authority where appropriate and are closely monitoring the third party incident.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

Google Trust Services is experiencing an unplanned outage: https://status.pki.goog

This incident has been resolved.

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

We are aware of an issue where newly enabled R2 accounts encounter SSL errors when making requests via the S3-compatible API.

This incident has been resolved. Reinstalling the Cloudflare One Agent app after uninstalling and removing the VPN profile resolves the issue as a workaround.

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

Cloudflare is investigating issues with Cloudflare WARP and Cloudflare Zero Trust. Cloudflare WARP and Zero Trust users using iOS may experience connectivity issues or a degraded Internet experience.

This incident has been resolved.

After more investigation, the team has determined there was no impact to customers after all.

Users may be experiencing issues solving Turnstile challenges. The team is investigating.

This incident has been resolved.

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

Cloudflare is investigating issues with our Bot Management feature. Customers may experience an increase in the percentage of traffic detected as automated with JSD detections since Feb 12 2026. We are working to mitigate this problem. More updates to follow shortly.

Between the two following periods, there was Hyperdrive degradation in IAD which resulted in increased rates of failed queries for some customers. 2026-02-17 05:20 UTC to 2026-02-17 05:43 UTC 2026-02-19 07:22 UTC to 2026-02-19 07:42 UTC

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 increased level of HTTP errors in the Mumbai region. We are working to analyze 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.

We are currently investigating an issue where users accessing R2 and dependent services from APAC will see an increase in HTTP 5xx error responses. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.

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

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

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

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

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

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

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

We are continuing to investigate this issue.

Cloudflare has detected an issue regarding elevated latency affecting a subset of HTTP requests in Newark, NJ. We are actively investigating this region. Some customers using Cloudflare Data Loss Prevention (DLP) suite may see intermittent errors for traffic in this datacenter.

This incident is now resolved.

We have identified and implemented a fix for this issue and we are currently monitoring the results.

Cloudflare is investigating buffering and stalling in playback for Stream Live broadcasts. On-demand videos and Media Transformations are unaffected.

This incident has been resolved.

429 errors started around 20:52

This incident has been resolved.

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

Unified Billing users may see elevated 500 error rates when attempting to load credits

This incident has been resolved.

We are continuing to monitor for any further issues.

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

Analytics for some Load Balancing health monitoring events are delayed. the impact is limited to analytics and Load Balancing steering and notifications are fully functional.

Cloudflare has resolved an issue regarding network performance in Delhi, India. The incident occurred between 14:38 and 14:40UTC. Performance has returned to baseline levels, and we are continuing to monitor the region to ensure stability.

This incident has been resolved.

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

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are investigating an issue where AI Search instances are failing to index new documents. This is likely caused by elevated 4xx error rates from Vectorize.

This incident has been resolved.

Users with R2 buckets in the FedRAMP jurisdiction may be experiencing high error rates.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

Cloudflare is investigating reports of Sippy returning 404 on objects which do exist at the upstream provider. We are working to understand the full impact and mitigate this problem. Updates will be posted as they become available.

Cloudflare is investigating reports that posture checks are not appearing in the zero trust dashboard. Currently believe there are no impact to running posture checks.

This incident has been resolved.

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

Cloudflare is investigating an issue which potentially impacts multiple customers when trying to add new Turnstile Widgets. An error invalid-input-response on validation can be observed. Further detail will be provided as more information becomes available.

This incident has been resolved.

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

Cloudflare is investigating issues with the dashboard SSO connector. Customer may be unable to make changes to dashboard SSO configuration. We will update as we continue our investigation.

After a thorough investigation, our engineering team has determined that there is no customer impact, and as such this incident is now canceled.

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

Zone Versioning customers may see inaccurate data on their Cloudflare HTTP Traffic Analytics UIs. We are currently investigating this issue

This incident has been resolved.

Users with R2 buckets in the FedRAMP jurisdiction may be experiencing high error rates

This incident has been resolved.

We are continuing to monitor for any further issues.

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

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

Team is investigating reports of elevated errors related to free allocations. Dependent products are also affected. Impacted services - Workers AI, Stream, Images, Firewall for AI, AI Search Overall Impact: Minor

Between 15:13 UTC and 18:25 UTC on February 10, 2026, a subset of users routing through Cleveland, Ohio experienced connectivity errors caused by network timeouts. A fix has been implemented, and all traffic has returned to normal levels.

This incident has been resolved.

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

Cloudflare is aware of, and investigating an issue which potentially impacts multiple customers: using Cloudflare WARP while browsing msn.com domains might present an "Untrusted SSL Certificate" error. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.

This incident has been resolved, minimal impact found.

Cloudflare is aware of, and investigating an issue which potentially impacts multiple Workers KV customers related to an increase in cache hit latency. Further detail will be provided as more information becomes available

Between 2/7/2026 10:30 - 2/9/2026 03:20 UTC some customers may have experienced elevated timeouts using some GraphQL datasets. This issue does not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge.

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 has identified an issue with DNS resolution for `.co` and `.xyz` TLDs in Dallas, US. We are working to analyze and mitigate this problem. More updates to follow shortly.

This incident has been resolved.

Cloudflare has detected an issue regarding elevated latency affecting a subset of HTTP requests in Newark, NJ. we are investigating this region actively. Some customers using Cloudflare Data Loss Prevention (DLP) suite may see intermittent errors for traffic in this datacenter.

This incident has been resolved.

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

A subset of customers are experiencing issues when attempting to add new DNS Records. These issues do not affect the serving of cached files via the Cloudflare CDN or other DNS and security features at the Cloudflare Edge. More updates to follow shortly.

This incident has been resolved. If your site is still experiencing 404s/500s a redeployment will resolve the issue.

A fix has been implemented and we are monitoring the results. If your site is still experiencing 404s/500s a redeployment will resolve the issue.

Cloudflare is aware of and investigating an issue impacting some Pages projects where they may return an increase of 404s of 500s. We are working to analyze and mitigate this problem. More updates to follow shortly.