CHYP.ai · ORBIT // Cloudy_Day Security Suite

CDN & edge

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 Recursive DNS and Miami, United States - (MIA); 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 vs. reality: Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal)

Regions mentioned: Recursive DNS, Miami, United States - (MIA), Workers, AS, AF

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started10 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the change5 h 9 min

Evidence

  • Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
  • Vendor stage: resolved on “Issues with 1.1.1.1 public resolver in Canada”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low
  • 10 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

Issues with 1.1.1.1 public resolver in Canada

minor resolved · started · resolved

4 updates

  1. investigating

    Cloudflare is aware of, and investigating, an issue which potentially impacts multiple users in Canada that use 1.1.1.1 public resolver. Further detail will be provided as more information becomes available.

  2. identified

    We have reached out to the network where we see an active hijack of 1.1.1.0/24. 1.0.0.1 and public resolver IPv6 prefixes are fully operational and reachable at this time.

  3. monitoring

    The network with the offending route leak has fixed the issue on their end. We are currently monitoring the effect of this fix.

  4. resolved

    This incident has been resolved.

Official incident page ↗

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.

Where to next