Degraded / minor incident Cloudflare status
cloudflare.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
Cloudflare's status page shows “Degraded / minor incident” in Chicago, United States - (ORD) and R2; the vendor is resolved. User reports haven't spiked, so wide impact isn't visible yet.
confidence: medium Vendor: minor issue · users: normal · routing: no data.
- Vendor status page Degraded / minor incident · 3 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP AS13335: routing data not loaded on this view
- News & network weather 8 active / 10 recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Chicago, United States - (ORD), R2, Newark, United States - (EWR), AS, AF
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 11 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | 15 h 20 min |
Evidence
- Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
- Vendor stage: resolved on “Increased errors for R2 and Tiered Cache”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- 8 active network-weather events mention Cloudflare. Overlap in time is coincidence, not causation. evidence confidence: low
What we don't know: what is happening inside Cloudflare's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: no data. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).
Who depends on whom
14 other services in our catalog may lean on Cloudflare, so trouble here can show up elsewhere first. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Cloudflare, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Cloudflare. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Increased errors for R2 and Tiered Cache
minor resolved · started · resolved
3 updates
- investigating
Cloudflare is aware of, and investigating an issue with R2. Customers in Chicago, IL, may see 503 errors when using R2. We are currently investigating this issue.
- monitoring
Starting at 05:00 UTC, a network connectivity issue between several Cloudflare data centers caused a small percentage of requests to fail. R2 customers may have seen HTTP 500 errors, and requests for content served through Tiered Cache may have returned 520, 522 or 524 errors. Customers in Chicago and Newark saw the highest error rates, and other locations were affected at lower rates. Error rates have dropped close to normal levels since 05:30 UTC. We are continuing to monitor while the underlying network issue is resolved.
- resolved
This incident has been resolved.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.