Cloudflare service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for cloudflare.com. Compare the regional responses with the problem you see in Cloudflare.
Find Cloudflare help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Cloudflare's company website is not a check of a customer's proxied domain, DNS or origin server.
The checker above requests cloudflare.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Cloudflare action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Separate a Cloudflare dashboard issue from a developer-product entrypoint using these related checks: Cloudflare Dashboard status check, Cloudflare Workers status check, Cloudflare Pages status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse infrastructure checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Select the affected Cloudflare product; account support options depend on role and plan.
Open the website in your browser and compare it with the result above. This link opens the service, not its status page.
Open Cloudflare help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Domain, Ray ID, UTC time, client region, status and recent rule or deployment change.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Cloudflare.
These are troubleshooting comparisons, not claims that Cloudflare is currently experiencing a particular incident.
Capture the failing hostname, response code and any Cloudflare Ray ID; compare another public path on that hostname.
For a domain you administer, correlate the request with Cloudflare and origin logs and the relevant product/region on the status page.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Cloudflare seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open cloudflare.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Cloudflare issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Cloudflare support.
Run the cloudflare.com check and compare its original timestamps and responses with your actual error. Cloudflare's company website is not a check of a customer's proxied domain, DNS or origin server.
Use the official help/reporting resource linked above. Select the affected Cloudflare product; account support options depend on role and plan.
Capture the failing hostname, response code and any Cloudflare Ray ID; compare another public path on that hostname. For a domain you administer, correlate the request with Cloudflare and origin logs and the relevant product/region on the status page.
Domain, Ray ID, UTC time, client region, status and recent rule or deployment change.