Where does this status come from?

From Cloudflare's own status page API at https://www.cloudflarestatus.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Cloudflare's words. Their page covers more than this page shows; it is narrowed to the parts that concern Cloudflare.

How can my agent or app check Cloudflare status?

Fetch https://upbutler.com/status/cloudflare/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"cloudflare"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Cloudflare's?

Add "cloudflare" to the dependencies of your UpButler workspace. When one of your monitors fails while Cloudflare has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Cloudflare down?

Right now

Partly. Cloudflare is degraded.

Elevated Errors in China Network Colos.

Read from www.cloudflarestatus.com 4 min ago · every 120s

For agents

proceed

Proceed, expect slow or flaky responses.

GET upbutler.com/status/cloudflare/status.agent.json

MCP: upstream_status {"service":"cloudflare"}

CDN, DNS, Workers, R2 and Workers AI. This page shows the products, not the 300+ data-center locations.

What Cloudflare reports

Degraded· 3 open incidents

Taken as is from Cloudflare's own status page API. Incident titles and component names below are theirs. Narrowed to what concerns Cloudflare.

Open www.cloudflarestatus.com

UpButler's independent probe

API edge is answeringHTTP 400 · 248 ms

One request without credentials to api.cloudflare.com every two minutes. An answer shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.

Checked 72 s ago · up since 2026-10-10 01:23 UTC

Open at Cloudflare

Elevated Errors in China Network Colosinvestigating · impact minor
Since 2026-10-10 04:13 UTC · China Network
We are investigating a spike in errors observed in our China colos.
Cloudflare One Clients are incorrectly challenged on some sitesidentified · impact minor
Since 2026-09-22 19:23 UTC · Cloudflare One Client
The issue has been identified and a fix is being implemented.
Incorrect geo location for some Cloudflare WARP usersidentified · impact minor
Since 2026-08-27 18:46 UTC · WARP
We are continuing to work on a fix for this issue.

Text written by Cloudflare, shown unchanged.

Cloudflare components

3 of 80 not operational

Cloudflare Sites and Services

Abuse ReportsOperational
AccessOperational
Account ManagementOperational
AI GatewayOperational
AI SearchOperational
Always OnlineOperational
AnalyticsOperational
APIOperational
API ShieldOperational
Apps MarketplaceOperational
Area 1 - APIOperational
Area 1 - DashOperational
ArtifactsOperational
Argo Smart RoutingOperational
Audit LogsOperational
Authoritative DNSOperational
BillingOperational
BlogOperational
Bring Your Own IP (BYOIP)Operational
Browser IsolationOperational
Browser RunOperational
Bot ManagementOperational
Brand ProtectionOperational
Cache ReserveOperational
CDN/CacheOperational
CDN Cache PurgeOperational
Challenge PlatformOperational
Cloud Access Security Broker (CASB)Operational
Cloud App Control / KiveraOperational
Cloud ConnectorOperational
Cloud Network Interconnect (CNI)Operational
Cloudflare One ClientDegraded
Cloudforce One ReportsOperational
Community SiteOperational
ContainersOperational
Custom PagesOperational
D1Operational
Data Localization SuiteOperational
Data Loss Prevention (DLP)Operational
DashboardOperational
Developer's SiteOperational
Digital Experience Monitoring (DEX)Operational
Distributed Web GatewayOperational
DNS FirewallOperational
DNS Root ServersOperational
DNS UpdatesOperational
Durable ObjectsOperational
Email RoutingOperational
Email Security (Area1)Operational
Email Security (Zero Trust)Operational
Email SendingOperational
Ethereum GatewayOperational
FirewallOperational
GatewayOperational
Geo-Key ManagerOperational
Health ChecksOperational
HyperdriveOperational
Image ResizingOperational
ImagesOperational
InfrastructureOperational
IP GeolocationOperational
Load Balancing and MonitoringOperational
ListsOperational
Log ExplorerOperational
LogsOperational
Cloudflare Network FirewallOperational
Magic TransitOperational
Cloudflare WANOperational
Cloudflare One ApplianceOperational
Marketing SiteOperational
MCP PortalOperational
MeshOperational
MirageOperational
NetworkOperational
NotificationsOperational
SnippetsOperational
ObservatoryOperational
Page ShieldOperational
WARPDegraded
China NetworkDegraded

Cloudflare incidents, last 90 days

20 finished incidents seen since UpButler started tracking on 2026-10-10, 2 of them rated major or critical by Cloudflare. A typical one lasted 4 h 49 min; the longest 24 days.

Started (UTC)	Incident	Impact	Lasted
2026-10-09 18:52	Cloudflare API service issues	minor	7 h 19 min
2026-10-09 18:50	Network Performance Issues in Queretaro	minor	20 min
2026-10-09 14:41	Cloudflare DNS Resolver 1.1.1.1 and Gateway DNS are having issues in SIN	minor	4 h 49 min
2026-10-07 14:41	Cloudflare API service issues	minor	44 min
2026-10-07 02:48	Network Performance Issues in Columbus	major	9 h 3 min
2026-10-06 13:34	Network routing issue	minor	1 h 59 min
2026-10-06 08:22	RSA Keyless SSL handshake issues	minor	44 min
2026-10-05 17:14	Durable Objects Availability Issue in Eastern North America	minor	5 h 21 min
2026-10-05 10:55	API Shield JWT Validation Errors	minor	11 h 44 min
2026-10-03 05:54	Issues with Workers Build failing to start	minor	2 days
2026-10-02 21:46	Cloudflare CDN experiencing increase in errors.	critical	11 min
2026-10-01 20:59	Increased Errors for Durable Objects and R2	minor	19 min
2026-09-30 15:33	Cloudflare Workers build delays	minor	29 h 54 min
2026-09-30 13:49	Network Performance Issues in Los Angeles (LAX)	minor	5 h 29 min
2026-09-30 13:36	Membership Permission Change Delays	minor	4 h 34 min
2026-09-29 20:11	OTP Deliverability Errors	minor	39 min
2026-09-28 20:11	Replicate Flux Hotswap Models Stuck	minor	18 min
2026-09-26 10:20	Cloudflare Cloud Access Security Broker (CASB) Issues	minor	37 min
2026-09-23 18:42	Network Performance Degradation — Asia-Pacific	minor	6 days
2026-09-11 00:00	Hyperdrive Degraded Performance	none	24 days

Tell your outage from Cloudflare's

Declare that your project depends on Cloudflare. When one of your monitors fails while Cloudflare has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - cloudflare

Ask before you retry

curl -s https://upbutler.com/status/cloudflare/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "cloudflare",
  "verdict": "proceed",
  "status": "degraded",
  "reason": "Elevated Errors in China Network Colos",
  "retryAfterSec": null,
  "incident": {
    "title": "Elevated Errors in China Network Colos",
    "url": "https://www.cloudflarestatus.com/incidents/cyxclg7nnhjy"
  },
  "probe": {
    "state": "up",
    "statusCode": 400
  }
}

Questions

Is Cloudflare down right now?: Partly. As of 2026-10-10 05:08 UTC, Cloudflare is degraded, with an open incident: "Elevated Errors in China Network Colos". This page reads the status again every 2 minutes.
Where does this status come from?: From Cloudflare's own status page API at https://www.cloudflarestatus.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Cloudflare's words. Their page covers more than this page shows; it is narrowed to the parts that concern Cloudflare.
What does UpButler's own Cloudflare check prove?: Every two minutes UpButler sends one request without credentials to the Cloudflare API edge (api.cloudflare.com). Any answer from the edge, usually HTTP 400, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while Cloudflare reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
How can my agent or app check Cloudflare status?: Fetch https://upbutler.com/status/cloudflare/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"cloudflare"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Cloudflare's?: Add "cloudflare" to the dependencies of your UpButler workspace. When one of your monitors fails while Cloudflare has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in cloud and edge

UpButler is not affiliated with Cloudflare. Status and incident text belong to Cloudflare and are read from their public status source; the probe result is UpButler's own measurement.