Is Cloudflare down?
Is Cloudflare unavailable, or is a website using Cloudflare having trouble? Check for a Cloudflare incident, then separate platform-wide problems from origin-server, DNS, browser, account, and network issues.
Site Administrator
Last reviewed: September 25, 2026
LATEST RECORDED STATUS
Up Cloudflare’s website appeared to be up and responding normally at the last check.
| Endpoint | Status | Observed |
|---|---|---|
| cloudflare.com | Operational | 2026-11-09 11:46 UTC |
| api.cloudflare.com | Operational | 2026-11-09 11:46 UTC |
Is it working for you?
0 recent reports — more reports are needed for a useful trend.
For the full picture, including partial or regional outages a single external check may miss, see Cloudflare’s official status page. official status page.
What this check can tell you
- Check Cloudflare Status before treating a Cloudflare-branded error as a confirmed platform outage.
- A 502, 503, or 504 affecting one website can originate from that site’s server or application rather than Cloudflare.
- Compare the affected hostname from another device or network to identify local DNS, browser, VPN, firewall, or routing problems.
- Site owners should check DNS, TLS, firewall rules, load balancer health, origin logs, and recent deployments when one hostname fails.
- For dashboard and API errors, verify the account, token scope, endpoint, request format, and target resource before repeated retries.
- Preserve the exact error, timestamp, hostname, response code, and Ray ID without disclosing passwords, tokens, cookies, or private request data.
About Cloudflare reliability
Understanding Cloudflare availability
Cloudflare sits between visitors and many websites, applications, APIs, and DNS configurations. Because of that position, a problem on one site can look like a Cloudflare outage. A Cloudflare-branded error page alone does not confirm that Cloudflare’s platform is unavailable.
Check Cloudflare Status for incident notices and affected Cloudflare components. This is most useful for broad platform problems, but it may not explain an issue limited to one hostname, zone, account, data center, origin server, or API request.
Use the scope of the failure to narrow the likely cause:
- A dashboard or API failure affecting multiple accounts, resources, or requests may indicate a Cloudflare platform problem, although authentication and permissions still need checking.
- A single website returning a 5xx response may have an unavailable origin, application failure, firewall rule, DNS problem, or connection issue between the origin and Cloudflare.
- DNS resolution failures can prevent a hostname from reaching Cloudflare at all.
- TLS, redirect, timeout, and connection-refused errors often involve the hostname, origin, certificate, route, or local network rather than a Cloudflare-wide outage.
Before escalating, record the hostname or endpoint, URL path, approximate time and time zone, HTTP status, exact error text, affected network, and Cloudflare Ray ID if displayed. Note whether unrelated Cloudflare-backed sites are also affected.
How to troubleshoot Cloudflare
Troubleshooting Cloudflare problems
Check for a Cloudflare incident
Open Cloudflare Status and compare any incident details with the affected Cloudflare product or behavior. If several unrelated Cloudflare-dependent services fail at the same time, a platform incident is more plausible. If only one hostname, zone, account, or endpoint is affected, investigate its configuration and dependencies first.
A website returns a Cloudflare 5xx error
A 5xx response can come from the origin server, application, upstream dependency, or connection between the origin and Cloudflare. If you administer the site, check origin availability, server and application logs, recent deployments, firewall rules, load balancer health, and whether the origin accepts traffic from Cloudflare.
- 502 Bad Gateway: inspect the origin or upstream response for an invalid gateway response.
- 503 Service Unavailable: check whether the origin or application is overloaded, unavailable, rate-limited, or intentionally refusing requests.
- 504 Gateway Timeout: check for a slow or unreachable origin or upstream dependency and review response timing.
If you only visit the site, check the status page and retry later. If the problem continues, contact the site owner with the URL, time, error code, and Ray ID shown. Repeated refreshing will not repair an origin failure.
DNS does not resolve
Test the hostname from another network or with another DNS resolver. For a site you manage, check recent DNS changes, record values, proxy settings, and nameserver delegation. Clear a local DNS or browser cache only after confirming the authoritative configuration; cache clearing cannot fix an incorrect record or delegation.
The browser reports a TLS, redirect, timeout, or connection error
Try a private window and another browser to rule out extensions and cached state, then test from a different network such as mobile data. Site owners should inspect the certificate presented by the origin, HTTPS mode, redirect rules, and any HTTP-to-HTTPS loop. Connection refusals and timeouts commonly involve the origin, firewall, route, or local network rather than the Cloudflare dashboard.
The Cloudflare dashboard or API fails
Check Cloudflare Status, then verify the account or zone, authentication method, token permissions, API endpoint, HTTP method, request format, and target resource. Compare the failing request with a known-valid request without exposing credentials. A failure limited to one token, account, zone, endpoint, or resource is more likely to be an authorization or configuration issue than a global outage.
Collect evidence before escalation
Save the full response or screenshot, hostname, path or API endpoint, HTTP method, status code, exact error, timestamp and time zone, affected network, and Cloudflare Ray ID when available. Do not share API tokens, passwords, cookies, or other secrets.
Related troubleshooting guides
TROUBLESHOOTING GUIDE
502 Bad Gateway
A 502 Bad Gateway means a reverse proxy, load balancer, or CDN could not obtain a valid response from the backend server. Check the backend process, proxy error log, upstream host or port, socket permissions, resource limits, and CDN-to-origin access. The fault is usually between servers rather than in the browser.
TROUBLESHOOTING GUIDE
503 Service Unavailable
A 503 Service Unavailable response means the service cannot handle the request at that time. Common causes include exhausted CPU, memory, worker, or connection capacity; incomplete maintenance mode; an unavailable database or other dependency; or a proxy, WAF, rate limiter, or load balancer returning 503. Identify which layer generated the response, then review logs and resource usage before changing settings.
TROUBLESHOOTING GUIDE
504 Gateway Timeout
A 504 Gateway Timeout means a proxy, CDN, load balancer, or gateway waited for a backend response but its timeout expired first. The backend may still be running; common causes include slow database queries, overloaded workers, long-running tasks, delayed third-party services, and restrictive intermediary timeouts. Compare direct backend timing with the full gateway path before changing timeout settings.
TROUBLESHOOTING GUIDE
504 Gateway Timeout Behind Cloudflare
A Cloudflare-branded 504 Gateway Timeout usually means Cloudflare’s edge did not receive a timely response from your origin. Common causes include slow database or application work, an unreachable origin, incorrect DNS or firewall settings, and SSL/TLS configuration problems. Test the origin separately, then optimize or background long-running work and review the Cloudflare timeout that applies to the request and plan.
TROUBLESHOOTING GUIDE
DNS_PROBE_FINISHED_BAD_CONFIG
DNS_PROBE_FINISHED_BAD_CONFIG usually means your device or local network cannot use its configured DNS server correctly. First determine whether multiple websites fail, then restore automatic DNS settings, flush the DNS cache, and test without a VPN or proxy. If only one domain fails across unrelated networks, its nameserver delegation may be misconfigured.
TROUBLESHOOTING GUIDE
DNS_PROBE_FINISHED_NXDOMAIN
DNS_PROBE_FINISHED_NXDOMAIN means DNS could not find the exact hostname requested. Check the spelling, subdomain, authoritative nameservers, required A, AAAA, or CNAME record, and domain registration status. If the DNS change was recent, cached negative responses may persist; it is usually a DNS or domain configuration issue rather than a web-server outage.
TROUBLESHOOTING GUIDE
ERR_CONNECTION_REFUSED
ERR_CONNECTION_REFUSED means the browser reached a destination address, but the connection was rejected before the website returned a response. Common causes include a stopped web server, no process listening on port 80 or 443, a service bound only to localhost, an incorrect DNS destination, or a firewall rule blocking access. Check the destination and listener first, then test from an external network.
TROUBLESHOOTING GUIDE
ERR_CONNECTION_TIMED_OUT
`ERR_CONNECTION_TIMED_OUT` means the browser waited for the destination server or an intermediary to respond, but no usable response arrived before the connection timeout. Common causes include an unreachable or overloaded server, a firewall silently dropping traffic, incorrect DNS, a broken network route, or a CDN or proxy that cannot reach the origin. Test from another network first, then check DNS, infrastructure health, firewall rules, and resource usage.
Sources & references
Official source
- Cloudflare Status — incident notices and component availability for Cloudflare services.
Use the status page for platform-wide availability. For a problem limited to one website, zone, account, or API request, consult the relevant Cloudflare product documentation and preserve the request details needed for account or technical support. The site owner may also need to check its origin-server, DNS, certificate, firewall, and application records.
How this check works
Every time this page loads, our server makes its own request to cloudflare.com (and its API domain, when applicable) and reports what it got back — a real HTTP response, a timeout, or a connection failure. That result is cached for up to 2 minutes.
This confirms external reachability; it does not test every feature, region, account, or network path. Cross-check the official status page when one is available.
Embed this live status badge
Add this badge to a dashboard, documentation page, or blog. The badge reads the cached Erriscope observation and links back to this status page.
<a href="https://erriscope.com/status/cloudflare/"><img src="https://erriscope.com/status/badge/cloudflare.svg" alt="Cloudflare status on Erriscope" width="210" height="34"></a>Frequently asked questions
Is this the same as Cloudflare's official status page?
No. This is a live, one-off connectivity check run from our own server, not Cloudflare's own incident reporting. Their official status page can show partial, regional, or component-level issues our single external check cannot detect.
Why does this show "Up" when Cloudflare feels slow or broken for me?
A basic reachability check confirms that the server responded to our request. It does not test every feature, region, ISP, browser, or account-specific issue.
How often is this checked?
A check is refreshed after the two-minute cache expires. The displayed check time shows when the observation was made.
Does an API outage mean the whole product is down?
Not necessarily. Many services split their website and API onto separate infrastructure, so one can fail while the other keeps working.
Is Cloudflare down right now?
Check Cloudflare Status for active incidents and affected components. One website failing is not enough to confirm a Cloudflare-wide outage because its origin, DNS, application, or security configuration may be responsible.
Why am I seeing a Cloudflare error page?
Cloudflare may be unable to reach the site’s origin, may receive an invalid or delayed response, or may be enforcing a configured security or routing rule. The error code, message, hostname, and any Ray ID provide more useful clues than Cloudflare branding alone.
Does a Cloudflare 502 or 504 mean Cloudflare is unavailable?
Not necessarily. These errors can result from an unreachable, overloaded, misconfigured, or slow origin server or upstream service. Check Cloudflare Status, then investigate the origin and its connection to Cloudflare if you manage the site.
Why does a Cloudflare-backed site work on one network but not another?
The difference may involve local DNS cache, a DNS resolver, VPN or firewall policy, ISP routing, browser settings, or an IPv4/IPv6 path. Compare the hostname from another network and device before concluding that Cloudflare has a platform outage.
Why is the Cloudflare dashboard or API not working?
First check Cloudflare Status. If no matching incident is shown, verify authentication, token permissions, account or zone selection, endpoint, HTTP method, request format, and target resource. Determine whether the failure affects one resource or multiple resources, and never share API credentials during troubleshooting.
What should I include when reporting a Cloudflare problem?
Include the affected hostname or API endpoint, exact error and HTTP status, timestamp with time zone, reproduction steps, network used, and Cloudflare Ray ID if displayed. Exclude passwords, tokens, cookies, and other sensitive request data.
This is a live connectivity check from our server, not an official statement from Cloudflare. A down result may also reflect a regional or partial outage.
LIVE CHECKS
