Space for ads
Checked every 5 minutes · How we measure this
As of 03:20 EDT on 8 Oct 2026, Cloudflare reports degraded or failing components on its own status page. Our probe still reached cloudflare.com in 145 ms, with 100.00% availability over the last 24 hours.
Checked every 5 minutes · last checked 8 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
Cloudflare API service issues
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Network Performance Issues in Columbus
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Network routing issue
We are continuing to monitor for any further issues.
Confirmed on the vendor status page
RSA Keyless SSL handshake issues
We are continuing to monitor for any further issues.
Confirmed on the vendor status page
Durable Objects Availability Issue in Eastern North America
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
API Shield JWT Validation Errors
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Issues with Workers Build failing to start
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Cloudflare CDN experiencing increase in errors.
Cloudflare is investigating an increase in errors for CDN configuration changes and purge calls specifically issued from the dashboard. Otherways to purge and configure Cloudflare (for example via API or terraform) were unaffected.
Confirmed on the vendor status page
Increased Errors for Durable Objects and R2
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Cloudflare Workers build delays
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Network Performance Issues in Los Angeles (LAX)
We are continuing to investigate this issue.
Confirmed on the vendor status page
Membership Permission Change Delays
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Network Performance Issues in Madrid
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
OTP Deliverability Errors
We are investigating an issue causing a high percentage of Access One Time Pin emails to fail. All other authentication methods are operating as normal.
Confirmed on the vendor status page
Replicate Flux Hotswap Models Stuck
We are investigating Flux hotswap models that haven't made progress since last Thursday, 2026-09-24.
Confirmed on the vendor status page
Yes. Cloudflare failed our last 2 consecutive automated checks of cloudflare.com. Availability over the past 24 hours is 100.00%. Last checked 8 minutes ago.
Measured from our automated checks, Cloudflare has been available 100.00% over 24 hours, 99.90% over 7 days, 99.91% over 30 days. We recorded 58 incidents in the last 30 days.
Cloudflare has averaged 146 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
