CHYP.ai · ORBIT // Cloudy_Day Security Suite

ORBIT · CLOUDY_DAY · FLAGSHIP

Outage Dissector

Every outage, taken apart. Pick any live or historic incident and get the reconstructed timeline, blast radius, blast map, failure-mode fingerprint, evidence matrix, historical twins and one honest magnitude, from public sources only.

  • 63open incidents
  • 6provider storms
  • 86network index · Clear
  • 21meltdowns indexed
Biggest right nowCloudflare ≈M6.4 Storm

◎The Magnitude Board

MeltdownSevere stormStormSquallTremor10m1h6h1d3d1wduration (log) →MGoogle Cloud · 2020-04-08 · IAM configuration change propagated globally past canary · M8.5Cloudflare · 2020-07-17 · Backbone router configuration error overwhelmed Atlanta · M6.4Amazon Web Services · 2020-11-25 · Kinesis front-end fleet exceeded OS thread limit · M7.2Google Cloud · 2020-12-14 · Automated quota system shrank User ID Service capacity · M8.5Fastly · 2021-06-08 · Valid customer configuration triggered a latent global bug · M6.9Amazon Web Services · 2021-12-07 · Internal-network surge, retries, and control-plane API failures · M7Cloudflare · 2022-06-21 · Network configuration change took 19 data centers offline · M6.8Amazon Web Services · 2023-06-13 · Lambda cell crossed a capacity threshold and hit a latent defect · M7Cloudflare · 2024-06-20 · New DDoS rule exposed a latent rate-limiting bug · M7.5Amazon Web Services · 2024-07-30 · Kinesis cell-management misidentified healthy hosts during a deployment · M7Microsoft Azure · 2024-07-30 · Front Door: network control-plane failure plus latent routing configuration · M7Microsoft Azure · 2024-09-27 · ARM control plane blocked by a global Cosmos DB misconfiguration · M5.5Google Cloud · 2025-06-12 · Service Control crash loop after a blank quota-policy field went global · M8.8Microsoft Azure · 2025-10-09 · Front Door: manual metadata cleanup bypassed protection · M7Amazon Web Services · 2025-10-19 · DynamoDB DNS automation wrote an empty record it could not repair · M7.1Microsoft Azure · 2025-10-29 · Front Door: incompatible metadata across two control-plane versions · M8.4Cloudflare · 2025-11-18 · Bot Management feature file doubled and crashed traffic-routing software · M8.1Cloudflare · 2025-12-05 · WAF change for a React vulnerability hit a latent Lua bug · M7.3Google Cloud · 2026-07-14 · Network-control-plane configuration update dropped GCVE private traffic · M7.5LIVE · Cloudflare · Cloudflare: 19 components partial outage · AS · M6.4 · open 2dLIVE · Cloudflare · Cloudflare: 6 components partial outage · AF · M5.8 · open 2dLIVE · Cloudflare · Cloudflare: 4 components partial outage · SA · M5.7 · open 2dLIVE · Cloudflare · Cloudflare: 3 components partial outage · NA · M5.6 · open 2dLIVE · Amazon Web Services · AWS Bahrain: Multiple services — Region Availability · M5.5 · open 2dLIVE · Amazon Web Services · AWS UAE: Multiple services — Region Availability · M5.5 · open 2dLIVE · Cloudflare · Cloudflare: 2 components partial outage · EU · M5.4 · open 2dLIVE · Cloudflare · Cloudflare: 2 components partial outage · OC · M5.4 · open 2dLIVE · Alchemy · [Network-Wide] Zetachain Testnet Stall · M4.7 · open 42h 21mLIVE · Shippo · USPS International Label Creation Impacted for Select European Destinations · M4.6 · open 20h 36mLIVE · Cloudflare · Cloudflare: 2 components degraded performance · M4.6 · open 2dLIVE · Snowflake · INC20000369 · M4.4 · open 5h 36mLIVE · Alchemy · Monad Mainnet & Testnet - eth_simulateV1 temporarily unavailable · M4 · open 31h 43mLIVE · OVHcloud · [US-WEST-OR][Storage] - Cloud Archive incident notification · M4 · open 40h 5mLIVE · Wise · Delayed transfers to COP · M4 · open 42h 21mLIVE · OVHcloud · [GLOBAL][AI & Machine Learning] - AI Endpoint Incident Notification · M3.9 · open 29h 34mLIVE · Twilio · Twilio: 2 components degraded performance · AS · M3.9 · open 2dLIVE · Cloudflare · Cloudflare: Changes to Cloudflare Workers are not producing Event Subscription events · M3.9 · open 2dLIVE · Cloudflare · Network Performance Issues in Washington, DC datacenter (IAD) · M3.8 · open 15h 53mLIVE · Cloudflare · Network Performance Issues in Miami · M3.8 · open 31h 28mLIVE · Linode (Akamai Cloud) · Akamai Cloud (Linode): Service Issue - Linode Kubernetes Engine · M3.5 · open 28hLIVE · Akamai · Akamai: 1 component degraded performance · M3.5 · open 33h 8mLIVE · Twilio · Twilio: Voice Call Failures from a Subset of Twilio Philippines Phone Numbers to Multiple Networks in Philippines · M3.5 · open 2dLIVE · Twilio · Twilio: Voice Call Silent and One-Way Audio from Colombia to a Subset of Twilio Phone Numbers · M3.5 · open 2dLIVE · Linode (Akamai Cloud) · Akamai Cloud (Linode): Service Issue - Block Storage (BR-GRU) · M3.5 · open 2d

● live right now (pulsing) · ● famous meltdowns, coloured by primary failure mode. Up is worse, right is longer. Click any dot to dissect it.

⚡Provider storms

▶Dissect now

☗Hall of Meltdowns

M8.8 Meltdown2026-11-12

Microsoft 365

Exchange / Microsoft 365: servers unexpectedly unavailable, core process overwhelmed

CapacityCascade

Ongoing as of 3:19 PM PT (no official full-restore time in the sourced notes)

M7.5 Severe storm2026-07-14

Google Cloud

Network-control-plane configuration update dropped GCVE private traffic

Config pushControl plane

10h 40m

M7.3 Severe storm2025-12-05

Cloudflare

WAF change for a React vulnerability hit a latent Lua bug

Config push

25m

M8.1 Severe storm2025-11-18

Cloudflare

Bot Management feature file doubled and crashed traffic-routing software

Config pushCapacityCascade

3h 10m to core traffic; 5h 46m to all systems

M8.4 Severe storm2025-10-29

Microsoft Azure

Front Door: incompatible metadata across two control-plane versions

Control planeConfig pushCascade

8h 24m

M7.1 Severe storm2025-10-19

Amazon Web Services

DynamoDB DNS automation wrote an empty record it could not repair

Control planeCascade

14h 32m overall (three distinct impact periods)

M7.0 Severe storm2025-10-09

Microsoft Azure

Front Door: manual metadata cleanup bypassed protection

Config pushControl plane

8h 10m (availability restored 12:50 UTC)

M8.8 Meltdown2025-06-12

Google Cloud

Service Control crash loop after a blank quota-policy field went global

Control planeConfig pushCapacity

7h 27m

M5.5 Storm2024-09-27

Microsoft Azure

ARM control plane blocked by a global Cosmos DB misconfiguration

Config pushControl plane

1h 38m

M7.0 Severe storm2024-07-30

Microsoft Azure

Front Door: network control-plane failure plus latent routing configuration

Control planeConfig push

7h 58m (majority by 13:58 UTC)

M7.0 Severe storm2024-07-30

Amazon Web Services

Kinesis cell-management misidentified healthy hosts during a deployment

Config pushCapacityCascade

6h 52m

M7.5 Severe storm2024-07-19

CrowdStrike

Sensor content-configuration update caused a widespread Windows outage

Config push

duration not stated

M7.5 Severe storm2024-06-20

Cloudflare

New DDoS rule exposed a latent rate-limiting bug

Config push

114m

M7.0 Severe storm2023-06-13

Amazon Web Services

Lambda cell crossed a capacity threshold and hit a latent defect

CapacityControl planeCascade

3h 48m to full recovery

M6.8 Storm2022-06-21

Cloudflare

Network configuration change took 19 data centers offline

Config push

75m

M7.0 Severe storm2021-12-07

Amazon Web Services

Internal-network surge, retries, and control-plane API failures

RetriesControl planeCapacity

6h 52m to network-device recovery

M6.9 Storm2021-06-08

Fastly

Valid customer configuration triggered a latent global bug

Config push

49m to 95% of the network

M8.5 Meltdown2020-12-14

Google Cloud

Automated quota system shrank User ID Service capacity

CapacityConfig pushControl plane

47m

M7.2 Severe storm2020-11-25

Amazon Web Services

Kinesis front-end fleet exceeded OS thread limit

CapacityControl planeCascade

17h 8m

M6.4 Storm2020-07-17

Cloudflare

Backbone router configuration error overwhelmed Atlanta

Config pushCapacity

27m

M8.5 Meltdown2020-04-08

Google Cloud

IAM configuration change propagated globally past canary

Config pushControl plane

50m to majority mitigation

From the Control-Plane Meltdown Index: vendor post-incident reports only, quotes verbatim. Open the index (CSV, JSON) →

⬡Five ways the cloud falls over

1

Retry amplification

Failed or slow calls produce more client or peer retries, which increase load, which produce more failures — a retry storm, thundering herd, or metastable collapse.

12

Control-plane coupling

A shared API, metadata, identity, DNS, or management plane sits on the path of many services. When it fails, the blast radius is far larger than the originating component.

16

Config propagation

A configuration, feature-file, content, or policy update is pushed — globally or past a protection layer — and a latent defect or incompatible metadata takes the data plane down with it.

7

Dependency cascade

One impaired foundation (DNS, IAM, streams, a front door) causes a chain of failures in services that depend on it, often with health-check or failover side effects.

9

Capacity exhaustion

A thread limit, quota, health-check eviction, or overwhelmed core process removes capacity; remaining capacity is then overloaded, often accelerating the loss.

MHow CHYP Magnitude works

One open number from 0 to 10, so a 25-minute global meltdown and a 3-day regional drizzle stop sharing the same headline. Every input is public and shown on each case file.

  • 34% Severity: the worst official state
  • 24% Breadth: places, regions and stated scope
  • 12% Duration: log scale, saturates at one week
  • 20% Reach: catalogued services that depend on the provider
  • 10% Corroboration: independent evidence families (of 4)

0+ Tremor 3+ Squall 5+ Storm 7+ Severe storm 8.5+ Meltdown

A ranking aid, not a measurement of harm. It never says why something broke.

Guardrails

  • Public, passive sources only: ORBIT's own NetWeather ledger, official status pages ORBIT already archives, early signals, the news wire, CISA KEV and the Meltdown Index. ORBIT never contacts a provider or probes a host.
  • Lanes stay separate. Overlap is coincidence, not causation unless the provider states a link.
  • Failure-mode reads on live incidents are automated keyword hypotheses, not root causes. Historic modes come from the vendor's own report.
  • Outage history tracked since 2024, with earlier landmark cases from vendor reports. Independent researcher, not affiliated with any provider or government agency.

Machine-readable: /api/v1/dissect.json · every case file has a JSON and Markdown capsule.

Where to next