Cloudflare Status
Official status board for Cloudflare systems and incidents.
Live Domain Check
Check if Cloudflare is down right now (cloudflare.com). Run a live multi-region check to see whether Cloudflare is offline for everyone or just you.
Get official Cloudflare outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
Cloudflare incidents can affect dashboard access, DNS updates, WAF behavior, cache performance, or edge routing by region. Even when your origin is healthy, Cloudflare path issues can make a site look down for part of your audience.
For Cloudflare, incident signals are often feature-specific: Site intermittently fails by region while origin remains healthy. DNS propagation/record edits appear delayed. If this matches what you see on cloudflare.com, it usually points to partial degradation instead of a full outage, so confirm with official status updates and a second-network retest.
Cloudflare publishes a detailed official status page with component and regional visibility.
Official status board for Cloudflare systems and incidents.
Official support and troubleshooting documentation.
Direct dashboard access check for account-side issues.
Monitor real-time social updates and official posts related to Cloudflare outages.
Official teams often post outage status updates and recovery progress through these social channels.
Use these service-specific patterns to identify likely root cause quickly and choose the right next step.
Practical steps to follow when cloudflare.com seems down. Use this checklist to confirm whether Cloudflare is down for everyone or only for you.
Run cloudflare.com in WebsiteDown.org first, then open cloudflare.com in your own browser. If results disagree, the issue is often local rather than global.
Check the official Cloudflare service status page and compare timestamps with your failed checks.
Test related hosts such as www.cloudflare.com, dash.cloudflare.com. If they work while cloudflare.com fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for cloudflare.com, then share those details with Cloudflare support for faster triage and recovery.
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, the issue is usually local cache, cookie, or extension state.
Sign out and sign back in one time, then retry the failing action on cloudflare.com. Avoid repeated password or security resets until you confirm this is not a broader Cloudflare issue.
Temporarily disable VPN, proxy, private DNS, and filtering extensions. Then switch between Wi-Fi and mobile data to isolate route-level differences.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Cloudflare support.
Run the automatic multi-region check on this page for cloudflare.com. If most regions fail at the same time, Cloudflare is likely experiencing a broader outage or partial incident.
If only one or two regions fail, the issue is usually local to your network path (DNS resolver, ISP route, VPN/proxy, or firewall). Re-check after 2 to 5 minutes and compare Wi-Fi with mobile data.
Use the Official Status, Support, and Social Channels section above in this order:
Official dashboards are authoritative but can lag during the first minutes of an incident. Combine those sources with this checker to confirm whether Cloudflare is down globally, regionally degraded, or only affecting specific users.
That pattern usually points to path-specific issues rather than a full Cloudflare outage. Common causes include:
Test in a private window, temporarily disable VPN/extensions, and retry from a second network. If one feature fails while the homepage still loads, treat it as a partial incident.
Use this quick triage sequence for cloudflare.com:
This order helps you avoid unnecessary account resets when the Cloudflare issue is provider-side.