Cloudflare statusLiveFetched seconds agoSource: cloudflarestatus.com
Is Cloudflare down?
Live status check · Degraded performance
Minor Service Outage
Live status pulled from cloudflarestatus.com, cached and revalidated every 60 seconds. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About Cloudflare status
Cloudflare sits in front of roughly a fifth of the public web. When the edge network or DNS plane has a regional incident, the blast radius is huge: APIs, websites, Workers, R2, and KV can all be affected at once.
Components and surfaces that can break
- Surface 01
Edge / CDN (per-datacenter status).
- Surface 02
Workers, Durable Objects, KV, R2, Queues.
- Surface 03
DNS (1.1.1.1), Access, and Cloudflare Tunnel.
Recent Cloudflare incidents
Cloudflare maintains a public incident history. Read the latest entries to see whether you're hitting a known issue, and look at the post-mortems for context on how long similar incidents typically take to clear.
What to do if Cloudflare is actually down
Confirm which datacenter you're hitting
Cloudflare publishes per-datacenter health. Use cloudflare-cdn-cgi/trace from a browser or curl to see which colo your requests land in, then check the matching status row.
Don't move DNS during an incident
If your zone is on Cloudflare DNS, switching nameservers mid-outage is rarely worth it. Most Cloudflare incidents are resolved within an hour and DNS propagation takes longer.
Pause Workers Cron Triggers that retry aggressively
Workers Cron Triggers fire on Cloudflare's plane. If your trigger does retries on errors, it can hammer a recovering origin. Pause it during the incident and let an external scheduler resume the job once Cloudflare is green.
Keep firing through the incident
Schedule your own Cloudflare health check with Crontap
Cloudflare Workers Cron Triggers have a 1-minute minimum and run on Cloudflare's edge. If the edge or your specific colo is degraded, the trigger may fire late or not at all. Crontap calls the Worker URL from outside Cloudflare, so the schedule keeps running.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
Cloudflare status: FAQ
- How do I check if Cloudflare is down in my region?
- cloudflarestatus.com lists every colo separately. If you don't know which colo you hit, run curl -sI https://www.cloudflare.com/cdn-cgi/trace and look for the colo= line. Match that against the status page.
- Why did my Cloudflare Worker Cron Trigger miss a run?
- Cron Triggers fire on the same plane as Workers. Regional degradations, cold starts, and platform incidents can cause individual triggers to be skipped. There is no built-in retry for missed runs.
- How can I keep a Worker on schedule during a Cloudflare incident?
- Expose the Worker via a normal HTTP route and have Crontap call it on the same cadence. The Worker still runs on Cloudflare, but the schedule lives outside the platform, so the trigger fires even when Cron Triggers themselves are unhealthy.