Cloudflare had 440 outages in the last 2 years totaling 113h 53m of downtime — averaging 18 incidents per month.
There were 440 Cloudflare outages since April 3, 2026 totaling 113h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.
Between 22:00 and 01:00 UTC on September 18, 2026, customers reaching Cloudflare's Ashburn, VA (IAD) data center may have experienced an elevated number of errors, including 499 and 522 responses, due to a network hardware issue. The issue has been resolved.
Between 17:13-17:28UTC on 2026-09-18, Cloudflare experienced an elevated rate of 5xx HTTP errors affecting traffic passing through Ashburn (IAD). The issue has been resolved, and impact to the IAD location is mitigated.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare experienced network performance issues in Vancouver, Canada, between 20:12 and 20:24 UTC. This incident has been resolved.
Cloudflare identified an issue affecting network performance in Ashburn, VA, United States. A fix has been implemented, and we are monitoring the results.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare is aware that there was an increased level of HTTP errors in the GIG (Rio de Janeiro) datacenter, between 14:00 and 14:30 UTC. This has since recovered and normal operations have resumed.
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.
This incident has been resolved.
Some Hyperdrives experienced elevated failure rates when connecting to origin databases between 2026-09-16 22:45 UTC and 2026-09-17 00:45 UTC due to a misconfigured release. Hyperdrives connecting through Workers VPC or Cloudflare Access tunnels were not affected. This incident has been resolved.
Customers may have observed elevated rates of HTTP 522 error responses from our St. Louis (STL) facility between approximately 16:35 and 16:55 UTC today, 2026-09-16.
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.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Cloudflare is investigating delays with dispatching of notification emails for some customers. Webhooks and PagerDuty notifications are not affected.
This incident has been resolved.
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.
We are continuing to investigate this issue.
Support portal and live chat support are still unavailable due to the ongoing helpdesk provider outage. Customers may still experience issues submitting or viewing tickets/chats, and overall response times may be delayed. Phone support remains fully operational for urgent inquiries.
Support portal and live chat support are still unavailable due to the ongoing helpdesk provider outage. We highly recommend waiting for the incident resolution to submit or update cases. If you have an urgent issue, you can reach out to us on the emergency phone support line, or email us at [email protected], but please note that responses might be heavily delayed.
Support portal and live chat support remain unavailable while our helpdesk provider works toward a resolution. We strongly advise holding non-urgent cases until the incident is resolved. Please note that emergency phone support, and [email protected] are reserved for P1 and emergency issues. Response times on this backup channel may still be heavily delayed.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare is investigating an increased level of HTTP 5XX errors. 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.
This incident has been resolved.
Cloudflare is investigating issues with network performance in Singapore. 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.
This incident has been resolved.
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.
Load Balancing health events analytics and notifications are now up to date. Events and notifications between 22:02 and 22:45 UTC were skipped.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are investigating an issue which is preventing Replicate models from failing to start new replicas.
Some third party models as well as https://replicate.com/qwen/qwen-edit-multiangle are affected and are unable to scale out. Please use alternate models while we work with providers to publish fixed versions.
This incident has been resolved.
We’re receiving reports of network related issues/congestion in Los Angeles between Sept 14 22:15 - Sept 14 23:10 UTC. This issue is now resolved.
Cloudflare is aware of investigating issues with our Cloudflare Queues product.
We are investigating an issue where messages published to some queues are not being delivered to their consumers, resulting in delivery delays. Publishing to queues is unaffected, and messages are being received and safely retained — no messages are being lost. We have identified the root cause and are actively working on a fix. Affected messages will be delivered automatically once the issue is resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare is investigating failures in updating and creating Cloud Connector Rules. We are working to mitigate this problem. More updates to follow shortly.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cloudflare is investigating issues with Cloudflare Tunnel. More updates to follow shortly.
The issue has been identified and a fix is being implemented.
Mitigation is reducing the affected traffic, and recovery is progressing. Some existing Cloudflare Tunnel connections may continue to experience intermittent issues while this work completes. We continue to monitor progress.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
This incident has been resolved.
An issue prevented Workers VPC from correctly resolving hostname routes for a small subset of accounts between 06:22 and 09:38 UTC on Friday, September 11th, 2026. This problem has been fully resolved, and all services are operating normally. During this timeframe, affected accounts may have experienced connection failures, timeouts, or routing errors when Workers VPC attempted to fetch requests via hostname routes. The issue was strictly limited to hostname route resolution within Workers VPC for the impacted accounts; direct IP-based and public routing, standard Workers executions, and all other services were not affected. Our engineering team identified and deployed a fix for the root cause, and we are continuing to monitor service metrics to ensure stability. We sincerely apologize for any disruption this may have caused.
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.
Let's Encrypt incident is now resolved. Cloudflare managed certificate backlog is still clearing.
Let's Encrypt has resolved the incident and we are monitoring the results.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
This incident has been resolved.