Developer platforms
Is Cloudflare down?
Live Cloudflare status, measured independently. We probe 7 Cloudflare endpoints from monitoring regions on every continent and record every outage we detect.
Cloudflare is up
Our probes are reaching Cloudflare normally from every region we check from.
Checked every minute from 6 regions on every continent.
- Uptime, 24 hoursUptime, last 24 hours
- Uptime, 7 daysUptime, last 7 days
- Uptime, 30 daysUptime, last 30 days
- Website99.99% uptime, 30 days6 regions, 285 to 570 msUnknownp50median response452 msp95slowest 5% of checks585 ms1000 ms500024 h ago12 h agonow
- Edge network100% uptime, 30 days6 regions, 14 to 18 msUnknownp50median response16 msp95slowest 5% of checks29 ms20 ms10024 h ago12 h agonow
- API100% uptime, 30 days6 regions, 34 to 52 msUnknownp50median response42 msp95slowest 5% of checks76 ms100 ms50024 h ago12 h agonow
- Workers100% uptime, 30 days6 regions, 24 to 94 msUnknownp50median response52 msp95slowest 5% of checks223 ms200 ms100024 h ago12 h agonow
- Pages (developers.cloudflare.com)99.99% uptime, 30 days6 regions, 41 to 65 msUnknownp50median response51 msp95slowest 5% of checks81 ms100 ms50024 h ago12 h agonow
- 1.1.1.1 DNS over HTTPS100% uptime, 30 days6 regions, 9 to 15 msUnknownp50median response12 msp95slowest 5% of checks56 ms20 ms10024 h ago12 h agonow
- Official status feed100% uptime, 30 days6 regions, 58 to 810 msUnknownp50median response453 msp95slowest 5% of checks795 ms1000 ms500024 h ago12 h agonow
Daily strip:99.9% or better95–99.9%below 95%no data yet
Get notified when Cloudflare goes down
Follow these 7 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment Cloudflare goes down. They don't count against your monitor quota. Free plan, no card required.
About Cloudflare outages
Cloudflare sits in front of millions of sites as CDN, DNS, and firewall, and runs Workers, Pages, R2, and the 1.1.1.1 public resolver. When Cloudflare has a bad day, the visible symptom is usually a wave of unrelated websites returning 5xx errors at once.
Cloudflare incidents are frequently regional, tied to a single data centre or a routing change, so a probe from one location cannot tell the story. We probe the edge network itself, the API, a Workers deployment, a Pages site, and the DNS-over-HTTPS resolver from every continent, alongside cloudflare.com.
What we check
Every row is a real monitor in upti.my, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website cloudflare.com is unreachable. Often the first public sign of a wider edge problem. | httpwww.cloudflare.com | HTTP 200 | 1 min |
Edge network The Cloudflare edge itself is not serving. Sites behind Cloudflare return errors regardless of their origin. | httpwww.cloudflare.com/cdn-cgi/trace | HTTP 200 | 1 min |
API The Cloudflare API is not answering. Dashboard changes, Terraform runs, and Wrangler deploys fail. | httpapi.cloudflare.com/client/v4/ips | HTTP 200 | 2 min |
Workers A Cloudflare-hosted Workers endpoint is failing. Workers deployments may be affected. | httpwelcome.developers.workers.dev | HTTP 200 | 1 min |
Pages (developers.cloudflare.com) A site served by Cloudflare Pages is failing. | httpdevelopers.cloudflare.com | HTTP 200 | 2 min |
1.1.1.1 DNS over HTTPS The public resolver is failing. Devices and networks configured to use 1.1.1.1 lose name resolution. | httpcloudflare-dns.com/dns-query | HTTP 200 | 1 min |
Official status feed Cloudflare's status page is itself unreachable. | httpwww.cloudflarestatus.com/api/v2/status.json | HTTP 200 | 5 min |
For component-level detail and incident write-ups from the vendor, see Cloudflare's official status page.
Recent Cloudflare outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
Cloudflare is up. Is your Cloudflare integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on Cloudflare and fail quietly. Here is what teams that rely on Cloudflare monitor on their side.
Your site behind Cloudflare
A Cloudflare edge problem shows up on your domain as 52x errors while your origin is healthy. Monitor your public hostname and your origin directly so you know which side is failing.
HTTP monitoringCloudflare Workers cron triggers
Cron triggers can be skipped or delayed and there is no alert when a run does not happen. A heartbeat per trigger catches the silence.
Heartbeat monitoring for cronDNS hosted at Cloudflare
If Cloudflare authoritative DNS fails, nothing else about your stack matters. Monitor your key records from multiple regions.
DNS monitoringCloudflare status: frequently asked questions
Error 521, 522, and 523 mean Cloudflare could not reach your origin, which is usually your side. Error 500, 502 with the Cloudflare branding, or 530 pages during a wider incident usually indicate a Cloudflare problem. Compare with our probes and the official page before restarting anything.
Look at the per-region results above. If our probes fail from every region, Cloudflare has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, Cloudflare may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about Cloudflare" above: your upti.my workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on Cloudflare: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
DNS monitoring: what can go wrong
Resolver failures, propagation, and hijacks.
Uptime monitoring
Multi-region checks for public endpoints.
Other developer platforms
upti.my is not affiliated with Cloudflare. Cloudflare and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.