From Cloudflare Statuspage API. Times in Eastern (ET).
No active incidents reported by Cloudflare
Checked Nov 6, 10:48 AM EST · official feed, refreshed every 10 minutes
Edge data centers by region
North America55 of 63 sites normal · 2 in maintenance · 6 degraded or re-routed
Albuquerque, United States - (ABQ) (major outage), Guatemala City, Guatemala - (GUA) (degraded performance), Norfolk, United States - (ORF) (major outage)
Europe57 of 61 sites normal · 4 degraded or re-routed
Kyiv, Ukraine - (KBP) (degraded performance), Paris, France - (CDG) (degraded performance), Saint Petersburg, Russia - (LED) (major outage)
Latin America & the Caribbean40 of 52 sites normal · 1 in maintenance · 11 degraded or re-routed
Arica, Chile - (ARI) (major outage), Buenos Aires, Argentina - (EZE) (degraded performance), Curitiba, Brazil - (CWB) (degraded performance)
Asia76 of 98 sites normal · 22 degraded or re-routed
Bangalore, India - (BLR) (degraded performance), Hagatna, Guam - (GUM) (major outage), Fuzhou, China - (FOC) (degraded performance)
Africa25 of 33 sites normal · 8 degraded or re-routed
Oceania11 of 13 sites normal · 2 degraded or re-routed
Canberra, Australia - (CBR) (major outage), Sydney, Australia - (SYD) (degraded performance)
Green = normal, blue = planned maintenance, orange = degraded or re-routed. A few sites re-routed at any time is normal; traffic moves to the next site.
Services and components · 40 of 40 normal
CDN/Cacheoperational
Always Onlineoperational
Cache Reserveoperational
CDN Cache Purgeoperational
Cloud Connectoroperational
Custom Pagesoperational
Load Balancing and Monitoringoperational
Speed Optimizationsoperational
Waiting Roomoperational
WebSocketsoperational
Authoritative DNSoperational
DNS Firewalloperational
DNS Root Serversoperational
DNS Updatesoperational
Recursive DNSoperational
Secondary DNSoperational
Networkoperational
Argo Smart Routingoperational
Bring Your Own IP (BYOIP)operational
Cloud Network Interconnect (CNI)operational
Health Checksoperational
Infrastructureoperational
IP Geolocationoperational
Cloudflare Network Firewalloperational
Our 5-minute checks · last 7 days
We read Cloudflare's official status every 5 minutes. Each sliver is one hour, colored by the worst status seen; the daily figure is the share of checks with no degraded or major status. Stored since Oct 30, 11:32 PM EDT.
7 days agonow
67%Fri 10/30
8%Sat 10/31
0%Sun 11/1
0%Mon 11/2
0%Tue 11/3
Periods flagged by our checks
Oct 30, 11:32 PM EDT → ongoing
Partial System Outage
Incident history
Incidents per month from the official feed, by severity. The public Statuspage API returns only the latest 50 incidents (back to Oct 22, 2026). History is short: dashed boxes and empty months before the feed's first entry mean no published data, not a clean record.
Last 13 weeks
OperationalMinorDegradedMajorNo data
Root causes: hack, AI, config error or something else?
For each incident in the past year we show a cause only when Cloudflare's own report states one, quoting the sentence. The category is our label for that sentence; anything else is marked Unconfirmed / not yet disclosed.
Unconfirmed / not yet disclosed: 47
Other (see official report): 3
Nov 6, 4:47 AM EST · resolved Nov 6, 5:08 AM EST
Wrangler Deployments, Pages, and Workers Builds failures
Oct 29, 6:31 AM EDT · resolved Oct 29, 8:10 AM EDT
Increased HTTP 429 Rate Limit Errors on Cloudflare Dashboard
Other (see official report)
“Our engineering team is actively investigating the root cause and adjusting rate-limiting thresholds to restore normal dashboard access.” — Cloudflare
The big ones, with the cause in the official write-up's own words.
Dec 5, 2025
Body-parsing change breaks ~28% of HTTP traffic
Config / deploy error
“The issue was not caused, directly or indirectly, by a cyber attack… Instead, it was triggered by changes being made to our body parsing logic while attempting to detect and mitigate an industry-wide vulnerability.”
Impact: About 25 minutes of failures for a subset of customers (about 28% of HTTP traffic Cloudflare serves).
“The issue was not caused, directly or indirectly, by a cyber attack… it was triggered by a change to one of our database systems' permissions which caused the database to output multiple entries into a 'feature file' used by our Bot Management system.”
Impact: Error pages on a large share of websites behind Cloudflare worldwide for several hours.
Workers KV outage from a third-party storage provider
Third-party dependency
“Part of this infrastructure is backed by a third-party cloud provider, which experienced an outage today and directly impacted availability of our KV service.”
Impact: 2 hours 28 minutes of impact on Workers KV, WARP, Access, Gateway, Turnstile and more.
A short playbook. Tick items as you go (saved on this device only).
1 · Confirm the impact
2 · Fail over and limit the damage
3 · Monitor and get alerts
4 · Communication templates
Customer heads-up (incident open)
Status update ({time} ET): Some of our services are slow or unavailable because of an outage at Cloudflare, a provider we use. Your data is safe. We're working around it and will update you by {next} ET. Live status: {your_status_page}
Internal alert
Cloudflare incident affecting {services} in {region} since {time} ET. Impact on us: {impact}. Owner: {name}. Failover: {yes_no}. Next check-in {next} ET.
All clear
Resolved ({time} ET): Cloudflare has recovered and our services are back to normal. If anything still looks wrong, reply here or contact {support}. Thank you for your patience.
Fill in the {curly} parts. Post updates somewhere not hosted on the affected provider.
Official links, contacts and alerts
Every link checked before publishing. Phone numbers only where Cloudflare publishes them.