Cloudflare Status

We are continuing to investigate this issue.

Cloudflare Secrets Store users may see increased errors when accessing secrets

Reporting and analytics for HTTP requests rollups is delayed. Edge services are still fully operational, just analytics are delayed. We are working to mitigate this problem. More updates to follow shortly.

This incident has been resolved.

Cloudflare is investigating issues with the Cloudflare Notifications product. Some alerts might be temporarily delayed. Impact is restricted to the notification functionality and it does not affect any connectivity, security, CDN or Area1 functionality. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.

Cloudflare is aware of and investigating an issue impacting a subset of Pages uploads. Some customers may experience their uploads returning a 502 error. We are working to analyse and mitigate this problem. More updates to follow shortly.

Between May 14th and May 28th, 2026, an issue with network routing impacted a subset of Cloudflare Tunnel connections routing through our Anchorage, AK (ANC) point of presence. This issue has been fully mitigated by rerouting traffic to the nearest healthy data centers, and all services are now operating normally. During this time frame, customers with traffic routing through Anchorage may have experienced intermittent or persistent connection failures, manifesting primarily as HTTP 522 errors or connection timeouts. This problem specifically impacted Cloudflare Tunnels routing back to origin servers via this path. Because internal path-optimization systems incorrectly perceived the degraded path as functional, automated failover did not immediately trigger for this specific traffic profile. Traffic routing through all other Cloudflare regions remained entirely unaffected. We sincerely apologize for the duration of this disruption and the impact on our customers. We are actively prioritizing updates to our automated detection and mitigation systems to ensure similar infrastructure and transit anomalies are automatically identified and mitigated moving forward.

Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

Customers might have seen intermittent unavailability with the container managed registry

Cloudflare Analytics is degraded and customers might experience elevated rate of errors, and or increased latency while reading data via Cloudflare API.

Cloudflare is investigating issues about not correctly scanning certain AI gateway prompts for DLP

Workers Builds are experiencing increased queue times. 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.

We are investigating elevated error rates for API requests. Customers may experience failures when making API calls.

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 the DNS resolver component within Gateway for customers in the FedRAMP High environment. Affected customers using WARP may experience DNS lookup failures and be unable to reach sites through Gateway. This issue is limited to the FedRAMP High environment and does not affect commercial Cloudflare Gateway customers. We are working to mitigate this problem. More updates to follow shortly.

We are investigating an issue where some customers are experiencing 5xx errors after a Pages deployment completes.

Cloudflare Audit Log processing is running behind, causing a delay in timely delivery of audit data. This impacts v2 audit logs. v1 is unaffected.

Cloudflare is investigating issues 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.

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

We are investigating issues with Cloudflare One (Client and WAN) where DNS resolutions are failing for .internal zones when they are served by private DNS resolvers reachable via Cloudflare One only.

Cloudflare is investigating an increased level of HTTP 5xx errors in us-east-1. We are working to analyse and mitigate this problem. More updates to follow shortly.

Cloudflare is investigating issues with starting new containers. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.

Cloudflare saw an Increased 5XX errors in Porto Alegre and Curitiba, Brazil from 06:28 AM - 07:02 AM UTC. Issue has now been resolved

Between 15:00-15:20 UTC Customer traffic in Europe region may have experienced an increased rate of 520 errors

An issue with delay audit logs for Access has been identified. A fix is being prepared to resolve the delayed logs.

We have identified the problem and working to resolve.

Cloudflare is aware of and investigating customer reports of some Workers subrequests returning 1006 errors. We are working to analyse and mitigate this problem. More updates to follow shortly.

Cloudflare is investigating an increased level of HTTP 502 errors in Buenos Aires. We are working to analyse and mitigate this problem. More updates to follow shortly.

Customers may experience issue adding new MCP Servers or authenticating existing ones through the Zero Trust Dash

Cloudflare is investigating reports of intermittent authentication failures when logging into the Cloudflare Dashboard using SSO with Okta as the identity provider. Affected users may see a "failed to fetch" error during the login process. Dashboard access via other identity providers and direct username/password login are not currently reported as affected. Cloudflare Access application authentication is not currently reported as affected. Cloudflare Engineering is actively investigating the issue and will provide updates as more information becomes available.

Cloudflare is investigating issues 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.

Actions related to Digital Experience are delayed, Cloudflare is aware and investigating.

Cloudflare is investigating availability issues with several workers AI models.

We are continuing to investigate this issue.

Durable Objects and R2 buckets in our WNAM buckets may see increased latency, reduced throughput and slightly increased error rates.

Cloudflare identified an issue affecting the remote preview feature between 15:00 and 19:46 UTC. Workers configured with both a remote binding and a Durable Object failed to launch, throwing error code 10375.

Cloudflare is aware of and investigating an issue with Cloudflare Log Explorer. Affected customers may see delays with Cloudflare logs in their dashboard and api. We are currently working on a resolution. More updates to follow shortly.

Cloudflare is aware of and investigating issues paying for products with PayPal. Customers may experience an error when attempting to purchase or renew a product using PayPal. We are working to mitigate this problem. More updates to follow shortly.

Cloudflare is aware of and investigating an increase of R2 and Durable Object errors in Eastern North America. We are working to analyse and mitigate this problem. More updates to follow shortly.