Cloudflare Status

Cloudflare has identified an issue where some customers may experience latency or errors using Hyperdrive over Tunnels or the Workers KV API. We are working to analyze and mitigate this problem. More updates to follow shortly.

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

Cloudflare identified an issue where some customers may have experienced latency querying the GraphQL API between 07:15 and 09:30 UTC. This has been resolved.

Users in Dubai would have observed an increase in HTTP 5xx errors between 07:20 - 07:35 UTC 2026-06-09. This issue is now resolved.

Connectivity errors (HTTP 500s) and elevated latency observed due to a hardware failure between 01:32 - 01:36 UTC 2026-06-09. Cloudflare has mitigated the issue.

Some Cloudflare R2 users may have seen increased errors when using R2

Cloudflare One's SaaS integrations page has reported elevated HTTP 500 errors on API requests impacting ability to create, view, and manage integrations.

Some RealtimeKit users may not join meetings, team is investigating.

Cloudflare R2 users may have seen increased errors when reading data from buckets stored in WEUR.

Cloudflare has identified an issue where some customers may experience latency querying the GraphQL API. We are working to analyze and mitigate this problem. More updates to follow shortly.

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.

Starting June 5, 2026 (~12:00 UTC), users adding R2 and Teams products see "An unexpected error occurred while processing your payment." blocking them from creating subscriptions.

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

Connectivity errors (HTTP 500s) and elevated latency observed due to a hardware failure between 20:45 - 21:05 UTC 2026-06-06. Cloudflare have mitigated the issue.

Cloudflare has identified an issue affecting a subset of Let's Encrypt certificates, in which unsupported CA bundling may result in TLS connectivity issues for some visitors.

Cloudflare is investigating issues with Cloudflare related APIs. These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge. Some customers using the Cloudflare APIs might have requests fail and/or errors may be displayed.

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

Cloudflare is investigating latency issues with Cloudflare Analytics API, specifically affecting the Amsterdam (AMS) region. These issues do not affect other API services nor the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge.

Cloudflare is investigating latency issues with Cloudflare Analytics API, specifically affecting the Amsterdam (AMS) region. These issues do not affect other API services nor the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge.

Cloudflare observed network congestion in Frankfurt from 05:53 UTC to 06:08 UTC. The issue is now resolved.

Cloudflare is investigating issues with our Bot Management feature. Customers may observe a limited number of verified bots incorrectly identified as automated traffic.

We are investigating an issue where Cloudflare Audit Log processing is running behind, causing a delay in timely delivery of audit data. These delays do not impact analytics for DNS or Rate Limiting.

We are currently investigating this issue.

We are currently investigating this issue.

Cloudflare is investigating reports of some legitimate requests being incorrectly assigned a high bot score. Customers using Bot Management rules to challenge or block traffic based on bot score may see legitimate visitors incorrectly actioned. We are actively investigating and will provide updates as we learn more.

Cloudflare is investigating issues with network performance in TLV colos. We are working to analyze and mitigate this problem. More updates to follow shortly.

Cloudflare is investigating an increased level of errors for customers of Browser Run API. We are working to analyze and mitigate this problem. More updates to follow shortly.

Between 13:39 and 14:06 on June 2nd, 2026 Cloudflare identified and mitigated a network performance issue specifically affecting the US Eastern region. Users may have experienced increased latency or intermittent connectivity.

Cloudflare is aware of and investigating issues with Cloudflare Access. Customers may observe delays when making configuration changes. We are currently working on a resolution. More updates to follow shortly.

Cloudflare is aware that some customers may see an increased in Challenge failures within the China network. We are currently investigating the issue.

Cloudflare is investigating an increased level of HTTP 5xx errors between Miami and Bogota. We are working to analyse and mitigate this problem. More updates to follow shortly.

Cloudflare saw an Increased HTTP errors in Miami and Bogota from 01:50 to 02:55 UTC. This issue is now resolved

Cloudflare has identified an issue affecting a subset of Let's Encrypt certificates, in which unsupported CA bundling may result in TLS connectivity issues for some visitors. Customers requiring immediate resolution may order a replacement certificate; re-issuance from the same Certificate Authority will resolve the issue. Customer action is not required for a permanent fix — Cloudflare engineering is rebuilding all impacted certificate chains, and affected certificates will be automatically restored to a valid state.

Some users may see possible Network Congestion in the United States Eastern region. We are working to mitigate impact to those Internet users in this region.

Cloudflare is investigating issues with Cloudflare APIs that are specifically impacting OAuth/Wrangler API calls. 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.

Cloudflare is aware of, and investigating an issue with Durable Objects which potentially impacts multiple customers in the Atlanta region. Durable Objects are experiencing an elevated level of startup errors in the aforementioned region. We are currently investigating this issue.

Cloudflare is investigating issues with Let's Encrypt certificates. Some visitors may experience TLS connectivity issues due to potentially unsupported CA bundling for a subset of Cloudflare customers. Customers are advised to change to a different Certificate Authority as a workaround.

Cloudflare is investigating increased latency for customers using the Cloudflare for SaaS Custom Hostname API. Some products relying on new Custom Hostnames such as new R2 subscriptions, may be impacted. Existing Custom Hostnames remain unaffected and are operating normally.

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