Space for ads
Checked every 5 minutes · How we measure this
As of 00:30 EDT on 22 Sep 2026, Cloudflare reports degraded or failing components on its own status page. Our probe still reached cloudflare.com in 118 ms, with 100.00% availability over the last 24 hours.
Checked every 5 minutes · last checked 5 minutes ago
The line is response time measured from our probe to cloudflare.com, which rises when the service slows down. Shaded red marks intervals where checks actually failed. It excludes your own connection and browser rendering.
Reported by Cloudflare on its own status page. Verify on their status page.
0 problem reports
Network connectivity issues in LHR, London
The issue has been identified and a fix is being implemented.
Confirmed on the vendor status page
Unable to start containers in Asia-Pacific
The issue has been identified and a fix is being implemented.
Confirmed on the vendor status page
Unable to register certain domains
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"
Confirmed on the vendor status page
Cloudflare Dashboard Workers KV Issue
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Increased Errors for Durable Objects and Downstream Services in Asia Pacific (APAC) Region
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Network Performance Issues in Ashburn, VA, United States
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Replicate Pruna issue
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.
Confirmed on the vendor status page
Issues with 1.1.1.1 public resolver on .tn queries
The issue has been identified and a fix is being implemented.
Confirmed on the vendor status page
Email Notifications Delayed
Cloudflare is investigating delays with dispatching of notification emails for some customers. Webhooks and PagerDuty notifications are not affected.
Confirmed on the vendor status page
Support Helpdesk Availability Issues
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Network Performance Issues in Los Angeles
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Network latency affecting Singapore
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Load Balancing Analytics and Notification Delays
We are continuing to monitor for any further issues.
Confirmed on the vendor status page
Some Replicate models are failing to start
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.
Confirmed on the vendor status page
Cloudflare Queues issues
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Cloudflare is reporting degraded or failing components on its own status page. Our probe is still reaching cloudflare.com normally — 24-hour availability from our checks is 100.00% — so the front door is up while something behind it is not. The component list on this page shows which parts Cloudflare says are affected. Last checked 5 minutes ago.
Measured from our automated checks, Cloudflare has been available 100.00% over 24 hours, 99.85% over 7 days, 99.86% over 30 days. We recorded 26 incidents in the last 30 days.
Cloudflare has averaged 149 ms across our successful checks in the past 24 hours, which is fast — comfortably within what a healthy service should return. Response time is measured from our probe to cloudflare.com and does not include rendering time in your browser.
Our probe is also failing to reach cloudflare.com normally, so this is not just you. Use the report button on this page to add your own signal — when several people report the same problem within a short window, it appears on the chart above.
A working marketing site does not mean a working API. Call the API host directly — curl -s -o /dev/null -w "%{http_code}" https://cloudflare.com/ — and check the vendor status page linked above for component-level detail, since one component can fail while the rest stay green.
HTTP 429 and 529 mean you are being throttled, not that the service is down. Inspect the response headers for a retry-after value and back off exponentially rather than retrying immediately.
A 401 or 403 is an authentication problem on your side. Rotated keys, an expired billing method, or a revoked token all present as sudden total failure.
Open any other site. If nothing loads, the issue is your network rather than Cloudflare. On Windows run ping cloudflare.com and nslookup cloudflare.com in Command Prompt; on macOS or Linux use Terminal. A DNS failure and a server failure look identical in a browser but are very different problems.
Load cloudflare.com in a private or incognito window. If it works there, clear cookies and site data for cloudflare.com in your normal browser rather than clearing everything.
Switch from Wi-Fi to mobile data, or vice versa. Regional ISP routing problems are common and often affect one carrier while others are unaffected.
We link the vendor status page so you can check our reading against theirs.
No comments received
