Degraded / minor incident Cloudflare DNS (1.1.1.1) status
one.one.one.one · Official status inherited from Cloudflare
FROM ALL SOURCES
Cloudflare's status page shows “Degraded / minor incident” in Miami, United States - (MIA) and Workers; the vendor is identified the cause. 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 · 2 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP AS13335: routing data not loaded on this view
- News & network weather 10 active / 15 recent mentions
- Providers it may run on (inferred) status comes from Cloudflare's page
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Miami, United States - (MIA), Workers, Queues, AS, AF
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 10 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 | 1 h 8 min |
Evidence
- Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
- Vendor stage: identified the cause on “Network Performance Issues in Miami”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- 10 active network-weather events mention Cloudflare DNS (1.1.1.1). Overlap in time is coincidence, not causation. evidence confidence: low
What we don't know: what is happening inside Cloudflare DNS (1.1.1.1)'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 “identified the cause”. 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
Cloudflare DNS (1.1.1.1) may run on Cloudflare (inferred). We don't map other services that depend on Cloudflare DNS (1.1.1.1). 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 DNS (1.1.1.1) or its upstream providers, 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 DNS (1.1.1.1). No blame or attack claims without an official source. Generated .
ORBIT score
Storm
- official status: Degraded / minor incident
Official status
Degraded / minor incident Degraded / minor incident
Partially Degraded Service
Network Performance Issues in Miami minor identified · started
Affects: Miami, United States - (MIA)
Changes to Cloudflare Workers are not producing Event Subscription events minor identified · started
Affects: Workers, Queues
From Official status inherited from Cloudflare · official page ↗
User reports
0 in the last 15 min
Typical: 0 per 15 min (24 h baseline) · 0 in 24 h
Runs on (inferred)
- Cloudflare · see its status
Inferred from public engineering posts and press; may be outdated. Trouble upstream doesn't prove trouble here.
Network weather mentions
- Cloudflare: 16 components partial outage · AS Official incident (vendor status page) · active
- Cloudflare: 5 components partial outage · AF Official incident (vendor status page) · active
- Cloudflare: 4 components partial outage · SA Official incident (vendor status page) · active
- Cloudflare: 4 components partial outage · NA Official incident (vendor status page) · active
- Cloudflare: Network Performance Issues in Miami Official incident (vendor status page) · active
- Cloudflare: Changes to Cloudflare Workers are not producing Event Subscription events Official incident (vendor status page) · active
From NetWeather's public sources. Shown for context: coincidence, not causation.
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.