Is Cloudflare Down? How to Check Cloudflare Status Right Now

Cloudflare powers a significant portion of the internet — DNS, CDN, DDoS protection, zero-trust networking, and more. When Cloudflare has an issue, the impact is outsized: sites go unreachable, APIs fail, and engineering teams scramble to figure out whether the problem is theirs or Cloudflare's.

Here's how to check Cloudflare's status right now, understand what's actually affected, and make sure you're never the last to know.

Is Cloudflare Down Right Now?

The fastest way to check:

1. Statusfield — Cloudflare status — real-time monitoring updated every 5 minutes, no login required.
2. Cloudflare's official status page — cloudflarestatus.com shows component-level status but can lag real incidents by 15–30 minutes.
3. Cloudflare Radar — radar.cloudflare.com shows global traffic anomalies. A sudden drop in a region is often the first signal of a real outage.
4. Twitter/X — search Cloudflare down sorted by Latest. Usually the fastest public signal.

What Cloudflare Outages Actually Look Like

Cloudflare runs a massive distributed network, so outages are almost never global. They're typically regional or component-specific:

The most impactful outages for most teams are CDN/Cache and DNS — these affect every visitor to every site running behind Cloudflare in the affected region.

Why "Is My Site Down?" Might Actually Mean "Is Cloudflare Down?"

Cloudflare is so embedded in the internet stack that distinguishing between your own infrastructure problems and Cloudflare problems is genuinely hard. Symptoms that look like your own site going down but are actually Cloudflare:

• 522 errors (Connection Timed Out) — Cloudflare couldn't reach your origin
• 523 errors (Origin Unreachable) — Cloudflare can't connect to your server
• 524 errors (A Timeout Occurred) — origin took too long to respond
• 1000–1999 error codes — Cloudflare-specific errors returned before your origin is even hit

If you're seeing these error codes, check Cloudflare status before debugging your own infrastructure.

How to Diagnose a Cloudflare Issue Fast

Step 1: Check if it's regional

Cloudflare's network spans 300+ cities. An outage in ORD (Chicago) doesn't affect AMS (Amsterdam). Check cloudflarestatus.com for the specific region your users are in.

Step 2: Bypass Cloudflare and hit your origin directly

If you can access your origin server directly (via IP or an unproxied DNS record), you can confirm whether your origin is healthy and the issue is in Cloudflare's layer.

# Find your origin IP (if not using Cloudflare's proxy on all records)
curl -I https://your-origin-ip --header "Host: yourdomain.com"

If this works and your domain doesn't, Cloudflare is the problem.

Step 3: Check the CF-Ray header

Every response proxied through Cloudflare includes a CF-Ray header. If you're seeing 5xx errors and the response includes CF-Ray, the request reached Cloudflare. If there's no CF-Ray header, the problem is before Cloudflare.

curl -I https://yourdomain.com | grep -i "cf-ray\|server"

Step 4: Use Cloudflare Radar

radar.cloudflare.com shows internet traffic in real-time. A visible traffic drop in a specific country or region is a strong signal of infrastructure issues affecting that area.

Cloudflare's Historical Outage Patterns

Cloudflare is one of the most reliable networks on the internet — their 2023 reliability report showed 99.99%+ uptime for core services. But their outages are notable precisely because of their blast radius. Some significant incidents:

• June 2022 — Major outage affecting 19 data centers, including critical locations. Dozens of major services went offline. Caused by a bad BGP advertisement during maintenance.
• July 2023 — Extended incident affecting Workers and KV in multiple regions.
• September 2023 — Cloudflare Access outage disrupting zero-trust authentication globally.

The pattern: most Cloudflare outages stem from network configuration changes (BGP, routing) and deployment issues — not hardware failures. They typically resolve in 1–3 hours once identified.

Getting Automatic Cloudflare Alerts

Manually checking a status page during an incident is a reactive pattern that costs you time. The better approach: get notified the moment something changes.

Option 1: Statusfield (Recommended)

Monitor Cloudflare on Statusfield and get instant notifications when any component changes status. You choose:

• Which Cloudflare components to watch (CDN, DNS, Workers, R2, etc.)
• Your alert channel (email, Slack, Discord, webhooks)
• Whether to include maintenance windows

You'll know before your users do — and before Cloudflare posts the incident.

Option 2: Cloudflare Status RSS

Subscribe to https://www.cloudflarestatus.com/history.rss in any RSS reader. Updates when Cloudflare posts changes — note this lags real incidents.

Option 3: PagerDuty / Opsgenie Integration

Cloudflare's status page supports direct PagerDuty integration. Good for on-call teams who need wake-up alerts for major incidents.

What To Do When Cloudflare Is Down

Immediate actions:

1. Confirm it's Cloudflare — use the steps above before touching anything else
2. Check the specific component and region — don't treat all Cloudflare outages the same
3. Communicate clearly — post in your internal channel: "Cloudflare [component] experiencing issues in [region]. Monitoring."

For sites behind Cloudflare:

• If Cloudflare's CDN is down, visitors in affected regions can't reach your site. You can temporarily DNS-cut to point directly at your origin for the affected region, but this exposes your origin IP.
• If it's a Workers outage, consider whether you can disable or bypass the affected Worker.
• If it's DNS (1.1.1.1), your own site is likely fine — it's your users' resolution that's broken.

For teams using Cloudflare Zero Trust:

• Users will be unable to authenticate to access-controlled resources
• Prepare to communicate this proactively: "We're aware of issues with Cloudflare Access. Working on a workaround."
• If you have a backup authentication path, activate it

For Cloudflare R2 / D1 / KV users:

• Implement read-through caching where possible
• Queue writes for when service recovers rather than failing requests
• Have a fallback storage layer for critical data paths

Setting Up Proactive Cloudflare Monitoring

The right time to set up monitoring is before the next outage.

Monitor Cloudflare on Statusfield →

Set it up alongside your other critical dependencies — AWS, GitHub, Stripe, Vercel — in a single dashboard. When Cloudflare has a regional incident at 3 AM, you'll know within minutes, not when a customer messages you.

Frequently Asked Questions

How often does Cloudflare go down?

Cloudflare publishes a quarterly reliability report. For most core services (CDN, DNS), uptime exceeds 99.99%. Specific components like Workers or new products (R2, D1) may have higher incident rates as they mature. Major global outages are rare — roughly 1–2 per year.

Why does Cloudflare have such a large impact when it goes down?

Cloudflare handles approximately 20% of all internet traffic. Many sites use Cloudflare for CDN, DNS, and DDoS protection simultaneously. When any of those layers experiences issues, the effect cascades to every visitor of every site in the affected region.

Can I tell if my site's issue is Cloudflare or my own server?

Yes. Look for Cloudflare-specific error codes (5xx, 1xxx) and the CF-Ray header in responses. If CF-Ray is present and you're getting errors, the request reached Cloudflare. Try hitting your origin IP directly to confirm whether your server is healthy.

Does Cloudflare have an SLA?

Cloudflare Enterprise has SLAs. Cloudflare's free, Pro, and Business plans do not have formal uptime guarantees, though Cloudflare voluntarily publishes uptime data.

Should I use Cloudflare if it can take down my site?

Yes — the protection and performance benefits of Cloudflare outweigh the outage risk for most teams. The key is having monitoring and a runbook so that when (not if) there's an incident, your response time is minutes, not hours.

Is there a Cloudflare status API?

Yes: https://www.cloudflarestatus.com/api/v2/status.json returns the current status as JSON. You can poll this in scripts or dashboards.