CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · NetWeather event

AWS got hit by an outage too. Here's why you didn't hear about it

Amazon Web Services active M5.3 Storm since Nov 21, 6:35 AM PT

Amazon Web Services reported “AWS got hit by an outage too. Here's why you didn't hear about it” starting Nov 21, 6:35 AM PT.

  • 11h 36mDurationand counting
  • 2Systems namedfrom the source
  • —Places named0 on the map
  • 136Dependentscatalogued, inferred
  • 1/4Evidence kindsindependent families
  • 1Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Nov 21, 6 AMNov 21, 9 AMNov 21, 11 AMNov 21, 1 PMNov 21, 3 PMNov 21, 5 PM Official statusNov 21, 6:40 AM PT · AWS got hit by an outage too. Here's why you didn't hear about itNetwork & routingNov 21, 1:00 PM PT · AS16509 (AWS) BGP update churn -0.7σ vs 24hEarly signalsnothing in this windowNews & chatternothing in this windowCoincidence (KEV)nothing in this window ▼ startnow ▼

Drag or press Play to replay what was public at each moment. Each dot links to its evidence. Lanes are kept separate on purpose.

What happened

Amazon Web Services reported “AWS got hit by an outage too. Here's why you didn't hear about it” starting Nov 21, 6:35 AM PT.

What broke

UAE, Bahrain.

Who was hit

136 catalogued services run on Amazon Web Services (inferred); 4 of them show an official problem in the same window (coincidence, not causation). Hit: global/unspecified.

How it recovered

Still open after 11h 36m.

2Blast radius

Loom · Major outage · unwell in the same window (coincidence, not causation)LoomElastic Cloud · Degraded / minor incident · unwell in the same window (coincidence, not causation)Elastic CloudWise · Degraded / minor incident · unwell in the same window (coincidence, not causation)WiseXero · Degraded / minor incident · unwell in the same window (coincidence, not causation)XeroJFrog · MaintenanceSendGrid · MaintenanceTwilio · MaintenanceVonage API · Maintenance1Password · OperationalAbly · OperationalAffirm · OperationalAirtable · OperationalAiven · OperationalAmazon CloudFront · OperationalAmazon Route 53 · OperationalAnthropic (Claude) · OperationalAsana · OperationalAtlassian Statuspage · OperationalBitbucket · OperationalBuildkite · OperationalCanva · OperationalCash App · OperationalCircleCI · OperationalClickUp · OperationalCloudinary · OperationalCockroachDB Cloud · OperationalCoinbase · OperationalConfluence · OperationalContentful · OperationalCrypto.com · OperationalCursor · OperationalDocker Hub · OperationalDropbox · OperationalDuo Security · OperationalDuolingo · OperationalEpic Games Store · OperationalAmazon Web Se…136 dependents +100 more catalogued dependents not drawn

Center: Amazon Web Services. Inner ring: what it runs on. Outer ring: catalogued services that run on it, coloured by their official status right now. 4 are unwell in the same window: a lead, not proof of a cascade. Dependencies are inferred from public information.

3Blast map

No place names in the public text. Region tag: global/unspecified.

Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.

4Failure-mode fingerprint

RetriesControl planeConfig pushCascadeCapacity
  • Dependency cascade“multiple services”, 4 dependents also unwell
  • Retry amplificationno sign
  • Control-plane couplingno sign
  • Config propagationno sign
  • Capacity exhaustionno sign

Automated keyword read of the public updates. A hypothesis to test, never a root cause.

5Evidence matrix

Official statusOfficial status · Nov 21, 12:35 AM PT: 0 itemsOfficial status · Nov 21, 1:18 AM PT: 0 itemsOfficial status · Nov 21, 2:02 AM PT: 0 itemsOfficial status · Nov 21, 2:46 AM PT: 0 itemsOfficial status · Nov 21, 3:30 AM PT: 0 itemsOfficial status · Nov 21, 4:14 AM PT: 0 itemsOfficial status · Nov 21, 4:58 AM PT: 0 itemsOfficial status · Nov 21, 5:42 AM PT: 0 itemsOfficial status · Nov 21, 6:26 AM PT: 1 itemOfficial status · Nov 21, 7:10 AM PT: 0 itemsOfficial status · Nov 21, 7:54 AM PT: 0 itemsOfficial status · Nov 21, 8:38 AM PT: 0 itemsOfficial status · Nov 21, 9:22 AM PT: 0 itemsOfficial status · Nov 21, 10:06 AM PT: 0 itemsOfficial status · Nov 21, 10:50 AM PT: 0 itemsOfficial status · Nov 21, 11:34 AM PT: 0 itemsOfficial status · Nov 21, 12:18 PM PT: 0 itemsOfficial status · Nov 21, 1:02 PM PT: 0 itemsOfficial status · Nov 21, 1:46 PM PT: 0 itemsOfficial status · Nov 21, 2:30 PM PT: 0 itemsOfficial status · Nov 21, 3:14 PM PT: 0 itemsOfficial status · Nov 21, 3:58 PM PT: 0 itemsOfficial status · Nov 21, 4:42 PM PT: 0 itemsOfficial status · Nov 21, 5:26 PM PT: 0 itemsNetwork & routingNetwork & routing · Nov 21, 12:35 AM PT: 0 itemsNetwork & routing · Nov 21, 1:18 AM PT: 0 itemsNetwork & routing · Nov 21, 2:02 AM PT: 0 itemsNetwork & routing · Nov 21, 2:46 AM PT: 0 itemsNetwork & routing · Nov 21, 3:30 AM PT: 0 itemsNetwork & routing · Nov 21, 4:14 AM PT: 0 itemsNetwork & routing · Nov 21, 4:58 AM PT: 0 itemsNetwork & routing · Nov 21, 5:42 AM PT: 0 itemsNetwork & routing · Nov 21, 6:26 AM PT: 0 itemsNetwork & routing · Nov 21, 7:10 AM PT: 0 itemsNetwork & routing · Nov 21, 7:54 AM PT: 0 itemsNetwork & routing · Nov 21, 8:38 AM PT: 0 itemsNetwork & routing · Nov 21, 9:22 AM PT: 0 itemsNetwork & routing · Nov 21, 10:06 AM PT: 0 itemsNetwork & routing · Nov 21, 10:50 AM PT: 0 itemsNetwork & routing · Nov 21, 11:34 AM PT: 0 itemsNetwork & routing · Nov 21, 12:18 PM PT: 1 itemNetwork & routing · Nov 21, 1:02 PM PT: 0 itemsNetwork & routing · Nov 21, 1:46 PM PT: 0 itemsNetwork & routing · Nov 21, 2:30 PM PT: 0 itemsNetwork & routing · Nov 21, 3:14 PM PT: 0 itemsNetwork & routing · Nov 21, 3:58 PM PT: 0 itemsNetwork & routing · Nov 21, 4:42 PM PT: 0 itemsNetwork & routing · Nov 21, 5:26 PM PT: 0 itemsEarly signalsEarly signals · Nov 21, 12:35 AM PT: 0 itemsEarly signals · Nov 21, 1:18 AM PT: 0 itemsEarly signals · Nov 21, 2:02 AM PT: 0 itemsEarly signals · Nov 21, 2:46 AM PT: 0 itemsEarly signals · Nov 21, 3:30 AM PT: 0 itemsEarly signals · Nov 21, 4:14 AM PT: 0 itemsEarly signals · Nov 21, 4:58 AM PT: 0 itemsEarly signals · Nov 21, 5:42 AM PT: 0 itemsEarly signals · Nov 21, 6:26 AM PT: 0 itemsEarly signals · Nov 21, 7:10 AM PT: 0 itemsEarly signals · Nov 21, 7:54 AM PT: 0 itemsEarly signals · Nov 21, 8:38 AM PT: 0 itemsEarly signals · Nov 21, 9:22 AM PT: 0 itemsEarly signals · Nov 21, 10:06 AM PT: 0 itemsEarly signals · Nov 21, 10:50 AM PT: 0 itemsEarly signals · Nov 21, 11:34 AM PT: 0 itemsEarly signals · Nov 21, 12:18 PM PT: 0 itemsEarly signals · Nov 21, 1:02 PM PT: 0 itemsEarly signals · Nov 21, 1:46 PM PT: 0 itemsEarly signals · Nov 21, 2:30 PM PT: 0 itemsEarly signals · Nov 21, 3:14 PM PT: 0 itemsEarly signals · Nov 21, 3:58 PM PT: 0 itemsEarly signals · Nov 21, 4:42 PM PT: 0 itemsEarly signals · Nov 21, 5:26 PM PT: 0 itemsNews & chatterNews & chatter · Nov 21, 12:35 AM PT: 0 itemsNews & chatter · Nov 21, 1:18 AM PT: 0 itemsNews & chatter · Nov 21, 2:02 AM PT: 0 itemsNews & chatter · Nov 21, 2:46 AM PT: 0 itemsNews & chatter · Nov 21, 3:30 AM PT: 0 itemsNews & chatter · Nov 21, 4:14 AM PT: 0 itemsNews & chatter · Nov 21, 4:58 AM PT: 0 itemsNews & chatter · Nov 21, 5:42 AM PT: 0 itemsNews & chatter · Nov 21, 6:26 AM PT: 0 itemsNews & chatter · Nov 21, 7:10 AM PT: 0 itemsNews & chatter · Nov 21, 7:54 AM PT: 0 itemsNews & chatter · Nov 21, 8:38 AM PT: 0 itemsNews & chatter · Nov 21, 9:22 AM PT: 0 itemsNews & chatter · Nov 21, 10:06 AM PT: 0 itemsNews & chatter · Nov 21, 10:50 AM PT: 0 itemsNews & chatter · Nov 21, 11:34 AM PT: 0 itemsNews & chatter · Nov 21, 12:18 PM PT: 0 itemsNews & chatter · Nov 21, 1:02 PM PT: 0 itemsNews & chatter · Nov 21, 1:46 PM PT: 0 itemsNews & chatter · Nov 21, 2:30 PM PT: 0 itemsNews & chatter · Nov 21, 3:14 PM PT: 0 itemsNews & chatter · Nov 21, 3:58 PM PT: 0 itemsNews & chatter · Nov 21, 4:42 PM PT: 0 itemsNews & chatter · Nov 21, 5:26 PM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Nov 21, 12:35 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 1:18 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 2:02 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 2:46 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 3:30 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 4:14 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 4:58 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 5:42 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 6:26 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 7:10 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 7:54 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 8:38 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 9:22 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 10:06 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 10:50 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 11:34 AM PT: 0 itemsCoincidence (KEV) · Nov 21, 12:18 PM PT: 0 itemsCoincidence (KEV) · Nov 21, 1:02 PM PT: 0 itemsCoincidence (KEV) · Nov 21, 1:46 PM PT: 0 itemsCoincidence (KEV) · Nov 21, 2:30 PM PT: 0 itemsCoincidence (KEV) · Nov 21, 3:14 PM PT: 0 itemsCoincidence (KEV) · Nov 21, 3:58 PM PT: 0 itemsCoincidence (KEV) · Nov 21, 4:42 PM PT: 0 itemsCoincidence (KEV) · Nov 21, 5:26 PM PT: 0 itemsNov 21, 12:35 AM PTnow

Correlation is not causation

Five independent lanes across the window. Brighter = stronger item. Items landing in the same column are coincidence unless the provider says otherwise.

6Four clocks

Source says it beganNov 21, 6:35 AM PTORBIT first saw itNov 21, 6:40 AM PTLatest source updateNov 21, 6:35 AM PTLast checkedNov 21, 6:10 PM PT

Detection gap: 6m between the source's start time and ORBIT's first sighting.

Public status always trails reality. These are the times each public record states, in PT.

7Historical twins

Nearest matches in the Control-Plane Meltdown Index (1.0.0, vendor-sourced, tracked since 2024 with earlier landmark cases). Similarity = provider + failure modes + scope.

Cloudy_Day take

  • 4 services that sit on Amazon Web Services are unwell at the same time. That's a lead to check, not proof of a cascade.
  • 136 catalogued services lean on one provider. That's concentration risk, and it's the real headline.
  • By the clock it has outlasted 17 of 19 indexed meltdowns (median 3h 48m). By impact it isn't close. That's why ORBIT ranks by magnitude, not minutes.

Automated take: rules written by Cloudy_Day, applied to public data. Not a human verdict on this incident, not a root-cause finding, not affiliated with Amazon Web Services.

8Dissection capsule

Share card for this dissection

Everything above as one shareable, citable capsule with a content hash.

JSON capsuleMarkdownShare card (SVG)

Open Amazon Web Services in the War Room →NetWeather evidence page →Status page →

Embed this card
<a href="https://www.chyp.ai/dissect/event-nw-40de7832e3907106/"><img src="https://www.chyp.ai/dissect/event-nw-40de7832e3907106/card.svg" alt="AWS got hit by an outage too. Here's why you didn't hear ab… · ORBIT Outage Dissector" width="600"></a>

Sources & limits

  • Media or community attention. It is reporting evidence, not network telemetry, and is excluded from the v2 Network Signals index.
  • Region: global / unspecified. The source did not assert a region; none was inferred from publisher location.
  • Temporal overlap with other events is coincidence, not causation, unless a provider states a causal link.
  • NetWeather is independent research, not an official status source. Confirm with the provider.
  • Correlation is not causation. Lanes are kept apart so overlap never reads as cause.
  • ORBIT is passive: it never contacts the provider or probes its systems. Independent researcher, not affiliated.