Cloudflare

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 is investigating an issue where Cloudflare One Client customers are incorrectly challenged while visiting some websites.

Cloudflare is investigating issues with Cloudflare WARP and Cloudflare Zero Trust users being incorrectly geolocated by some third party services.

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.

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 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.

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

Customers may experience delays starting Cloudflare Workers builds.

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.

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.

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.

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.

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.

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.

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

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.

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

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.

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

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 is observing network connectivity issues in LHR, London. We are working to analyse and mitigate this problem. More updates to follow shortly

Cloudflare is aware of problems launching containers in the Asia-Pacific Region

Cloudflare is aware of an issue affecting the registration of the following top-level domains (TLDs): "audio", "baby", "build", "cam", "ceo", "christmas", "college", "dealer", "diet", "fans", "flowers", "fm", "game", "guitars", "help", "hosting", "icu", "inc", "lol", "mom", "monster", "pics", "protection", "rent", "security", "storage", "theatre", "xyz"

When searching for a Workers KV in the dashboard, the page hangs, typically upon the second attempt, causing the entire dashboard to freeze. This issue only impacts searching in the dashboard. Workers and Workers KV themselves are not affected. We are working to analyse and mitigate this problem. More updates to follow shortly.

Cloudflare is investigating an issue causing elevated error rates for Durable Objects and downstream services in the Asia Pacific region. We are working to mitigate this issue and will provide additional updates shortly.

Cloudflare identified an issue affecting network performance in Ashburn, VA, United States. A fix has been implemented, and we are monitoring the results.

Some Pruna models may not be able to scale up and are therefore either experiencing long queue times or entirely unavailable. We are working with Pruna to resolve the issue.

Cloudflare is investigating an issue that potentially impacts users resolving queries for .tn TLD domains via the 1.1.1.1 public resolver. Further detail will be provided as more information becomes available.

Cloudflare is investigating delays with dispatching of notification emails for some customers. Webhooks and PagerDuty notifications are not affected.

Our helpdesk provider is currently experiencing issues, and as such customers might encounter errors while submitting or viewing tickets. Responses on customer inquiries may be delayed during this time.

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

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

Cloudflare is investigating delays affecting analytics and notifications for Load Balancing health monitoring events. Load Balancing steering remains fully operational and is not impacted. We are working to resolve the issue.

We are investigating an issue which is preventing Replicate models from failing to start new replicas.

Cloudflare is aware of investigating issues with our Cloudflare Queues product.

Cloudflare is investigating failures in updating and creating Cloud Connector Rules. We are working to mitigate this problem. More updates to follow shortly.

Cloudflare is investigating issues with Cloudflare Tunnel. More updates to follow shortly.

Cloudflare is investigating issues with Network Performance in Taiwan datacenter (TPE) We are working to analyze and mitigate this problem. More updates to follow shortly.

Let's Encrypt are seeing SSL certificates provisioning delays. You can read their public status page here: https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/6aa35c1d892d7304f2747e01 SSL certificates already in production and other CAs certificate provisioning remains unaffected and are operating normally.

Cloudflare is aware of and investigating an issue preventing users from adding new redirects to existing Bulk Redirects. Traffic processed by existing Bulk Redirects remains unaffected, and this issue is limited to the configuration of these rules. Further details will be provided as we investigate.

Cloudflare is investigating delays in propagation of updates to DNS records. More updates to follow shortly.

Workers Cron Triggers may not execute or may be delayed in executing. Updates to Workers Cron Triggers may take some time to take effect.

Cloudflare is aware of, and investigating, increased Workers AI errors when attempting to use GLM 5.3. Updates to follow.

Cloudflare is investigating intermittent issues accessing the Cloudflare Dashboard from Firefox and Safari browsers.

Cloudflare is investigating an issue with Cache Reserve errors in Paris (CDG). Customers may see an elevated request volume to origin servers in the forementioned region. We are working to analyse and mitigate this problem. More updates to follow shortly.

Cloudflare customers may experience an issue when invited to a new account. An error message is displayed, "Invaild redirect_url". A workaround can be used: * Invited members create an account directly from the dashboard (not using the email link) * Admin resends invitation * Invited member clicks new link and signs into their Cloudflare account * Accepts invitation to join without issue We are continuing to investigate this issue.

Cloudflare is investigating an issue within the Dashboard UI (Networking > Routes) where the route configuration table is failing to display destination IP addresses/hostnames, connector names, and route descriptions correctly. Actual packet routing, network connectivity across the Cloudflare edge, and API-based route management remain fully operational and unaffected. Our engineering team is actively working on resolving the underlying rendering issue, and we will provide further updates as soon as more information is available.

We are investigating reports of customers encountering a white screen when attempting to access websites behind Browser Isolation. This is caused by Browser Isolation session initialization failing to complete. Our engineering team is actively working to identify and resolve the root cause.

We are investigating reports of performance degradation affecting our TURN service since August 22nd. Currently, a significant portion of traffic is being relayed via TCP rather than the expected UDP. Customers using Chrome browsers or other services relying on WebRTC may experience increased latency and connection lag. Our engineering team has identified the cause and a mitigation is currently being deployed. We are monitoring the rollout to ensure performance returns to expected levels.

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

We are investigating reports of delays in the provisioning of newly purchased domains. Our engineering team is currently working to resolve these delays affecting domain registration.

Customers may experience intermittent connectivity issues when accessing services through our Canberra (CBR01) data center. Our team is actively working to restore normal service.

Cloudflare is investigating issues with R2 buckets in Eastern North America.

Cloudflare is aware of, and implementing a fix for individual device posture checks not showing on the Devices Page. Device posture checks in the meantime can be inspected through the Logs -> Posture Logs. This is purely a dashboard visibility issue— firewall policies are not impacted.

Cloudflare cache purging called via the Dashboard or API is returning errors, with the message "unable to purge. internal error". We are working to resolve this issue as soon as possible. More updates to follow.

Cloudflare is investigating issues with R2 buckets in Western North America.

Cloudflare is aware of and investigating an issue with delays running Cloudflare Workers builds which potentially impacts multiple customers.

We investigated an increased level of HTTP 5xx errors and latency affecting services in the Hong Kong region. The issue has now been resolved.

Cloudflare is aware of, and investigating, an increased number of errors for Durable Objects in Western North America. The suspected cause is a reduction in routing capacity due to a fibre cut. We are working to mitigate this issue, and update will follow.

Cloudflare is investigating an increased level of errors for customers running Workers scripts in Narita. We are working to analyse and mitigate this problem. More updates to follow shortly.

Cloudflare is investigating an issue with creating new Pipeline resources, including Pipelines, Streams, and Sinks. Existing Pipelines are unaffected. More updates to follow shortly.

One of Cloudflare's peers experienced a route leak, misdirecting some traffic to Palmas, Brazil. We are working to mitigate impact to Internet users in this region.

Some customers using email security gateway like Proofpoint may experience delayed Cloudflare notifications and login codes. Proofpoint is temporarily deferring messages with an SMTP 421 4.7.0 response. Cloudflare will continue retrying delivery.

We are currently investigating this issue.

Some customers using Proofpoint may experience delayed Cloudflare notifications and login codes. Proofpoint is temporarily deferring messages with an SMTP 421 4.7.0 response. Cloudflare will continue retrying delivery. Affected customers should ask their Proofpoint administrator to allowlist notify.cloudflare.com and Cloudflare IPs 104.30.16.2,104.30.16.3,104.30.16.4,104.30.16.5,104.30.16.6, and 104.30.16.7. If this cannot be configured locally, contact Proofpoint for additional support.

Some Firefox users may see delayed or failed asset loads on R2 custom domains due to an incorrect HTTP/3 advertisement. We are working on a fix.

We are investigating an issue affecting the Access IP List service, which may result in failures when bypassing users whose IPs are listed in them. Our engineering team is currently working to identify and resolve the root cause. We will provide updates as more information becomes available.

We are investigating an issue affecting Workers KV in the Western Europe Region, which may result in elevated error rates for read requests. Writes are not affected. Our engineering team is currently working to identify and resolve the root cause. We will provide updates as more information becomes available.