Vendor record
Cloudflare
Checked
Front door check counts and Cloudflare’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Cloudflare endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,877 of 2,877 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
2 more checks gave no clear answer and are not counted.
- Endpoint checked
- api.cloudflare.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Cloudflare product, region or your app worked.
How we count front door checksShorter disruptions
Our checks are 15 minutes apart, so they miss disruptions shorter than that. Datadog runs a separate outage tracker that may show disruptions our checks cannot see.
Independent outage detection for Cloudflare: Datadog’s Updog(opens in a new tab)CheckUpstream is not affiliated with Datadog.
Cloudflare says
Incident posts from Cloudflare’s status page, with its titles, impact levels and times. They say what Cloudflare chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
194
incidents Cloudflare posted, last 90 days
Median recorded duration: 3h 24m. From 193 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Cloudflare Dashboard sign up issues
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(1h 9m)
Cloudflare Access Availability Issues
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(39m)
Workers Cron Triggers issues
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(1h 8m)
Network Performance Issues in Eastern North America
MajorCloudflare’s postStarted, per Cloudflare
Closed in our record(51m)
Network Performance Issues in London
MajorCloudflare’s postStarted, per Cloudflare
Closed in our record(17m)
15 older records
Pages.dev sites experiencing availability issues in Norway
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(4h 47m)
Increased Errors for Durable Objects
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(6h 3m)
DNS Update Delays
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(2h 51m)
Increased HTTP 502 Errors
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(9h 52m)
Increased Errors for Durable Objects and Downstream Services in Western Europe
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(51m)
Cloudflare Workers AI Issues
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(2h 34m)
Degraded performance for Cloudflare Browser Run
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(52m)
Cloudflare Workers - Cron Trigger Activation Issues
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(19h 54m)
Elevated number of 5XX errors in PDX
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(2h 9m)
Network Performance Issues in LAX
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(2h 12m)
Cloudflare Workers - Cron Trigger Activation Issues
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(8h 52m)
Audit Logs v2 ingestion is missing multiple Cloudflare products
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(2d 14h)
Network performance issues in Ashburn, US (IAD)
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(10h 59m)
Cloudflare Workers - Cron Trigger Activation Issues
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(3h 15m)
Cloudflare Network Performance Issues
MinorCloudflare’s postStarted, per Cloudflare
Closed in our record(7h 33m)
Your code, your dependencies
See which of your code paths call Cloudflare
Connect GitHub or GitLab to find where your public or private repository uses Cloudflare. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Cloudflare status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Cloudflare currently down?
Cloudflare's latest recorded status is Partial Outage. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Cloudflare last have an outage?
The most recent closed incident record began earlier today and spans 1h 9m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Cloudflare?
No. CheckUpstream checks Cloudflare’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Cloudflare in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Cloudflare?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.