CHYP.ai · ORBIT // Cloudy_Day Security Suite

TRANSPARENCY

How ORBIT and NetWeather work

We'd like to be a useful transparency tool for internet outages: show what each source says, side by side, link every claim to its evidence, and be upfront about what we can't see.

Principles

  • Evidence first. Every automated statement links to the data behind it and carries a confidence level (low, medium or high).
  • Stage is not health. A vendor's incident stage (investigating, monitoring, resolved) is shown next to what users and routing data show, and we flag the gap.
  • Four clocks. Vendor clock, crowd clock, network clock and our own clock are kept separate, because they rarely agree.
  • Coincidence, not causation. Signals that overlap in time are shown together, never as proof of cause.
  • No blame, no attack claims. We don't attribute outages to attacks or people unless an official source says so, and we don't name individuals.
  • Limits stated. Every readout ends with what we don't know.
  • Independent. Cloudy_Day is an independent researcher. ORBIT is not an official status source for any company or government agency.

Methods

  • Official status: public status-page APIs and feeds (165 services), polled politely with caching and back-off.
  • User reports: anonymous counts (Turnstile-checked, rate-limited, one per service per 15 minutes per visitor). We store no IP addresses or precise locations. A spike means at least 5 reports in 15 minutes and at least 3× the 24-hour baseline + 3.
  • Routing: public RIPEstat data (and Cloudflare Radar when configured). This shows reachability, not whether an app works.
  • Dependencies: inferred from public engineering posts and press, and labelled as inferred.
  • Automated analysis: template-driven from the numbers above. No free-form text generation, so nothing is invented. The owner can pin, edit, hide or annotate any readout, and owner notes are labelled as his.
  • No active scanning. We never probe or scan third-party systems.

Sources & limits

See every source and its license. User reports are self-selected and unverified; vendors may not publish everything; routing data has gaps. Comments are visitors' opinions, held for review.

Found an error? Tell us. Corrections are made openly.

Where to next