Scheduled maintenance is currently in progress. We will provide updates as necessary.
Cloudflare is investigating reports of some legitimate requests being incorrectly assigned a low 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 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 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.
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. Customers may experience slow responses while adding a new R2 subscription. Existing Custom Hostnames remain unaffected and are operating normally.
We are currently investigating intermittent failures affecting in-call actions and buttons. Some users may experience unresponsive or unreliable controls during active calls. Our team is actively working to identify the root cause and will provide updates as the investigation progresses.
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.