CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · NetWeather event

AWS Bahrain: Multiple services — Region Availability

Amazon Web Services chronic M5.8 Storm since Sep 15, 3:22 AM PT

Amazon Web Services reported “AWS Bahrain: Multiple services — Region Availability” starting Sep 15, 3:22 AM PT.

  • 67d 2hDurationand counting
  • 2Systems namedfrom the source
  • 1Places named1 on the map
  • 136Dependentscatalogued, inferred
  • 1/4Evidence kindsindependent families
  • 1Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Sep 20, 2026Oct 2, 2026Oct 14, 2026Oct 26, 2026Nov 7, 2026Nov 19, 2026 Official statusNov 19, 3:38 AM PT · AWS Bahrain: Multiple services — Region AvailabilityNov 20, 9:53 PM PT · Official status Major outage → OperationalNetwork & routingNov 21, 1:00 AM 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 Bahrain: Multiple services — Region Availability” starting Sep 15, 3:22 AM PT.

What broke

UAE, Bahrain.

Who was hit

136 catalogued services run on Amazon Web Services (inferred); 6 of them show an official problem in the same window (coincidence, not causation). Hit: 1 named location (AWS me-south-1).

How it recovered

Still open after 67d 2h.

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 CloudSendGrid · Degraded / minor incident · unwell in the same window (coincidence, not causation)SendGridTwilio · Degraded / minor incident · unwell in the same window (coincidence, not causation)TwilioWise · Degraded / minor incident · unwell in the same window (coincidence, not causation)WiseXero · Degraded / minor incident · unwell in the same window (coincidence, not causation)XeroJFrog · MaintenancePostman · MaintenanceZoom · 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 · 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. 6 are unwell in the same window: a lead, not proof of a cascade. Dependencies are inferred from public information.

3Blast map

AWS me-central-1 · Listed by AWS since 2026-03-01 · We are… · same provider, other region: AWS UAE: Multiple services — Region AvailabilityAWS me-south-1 · Listed by AWS since 2026-03-02 · We are…
  1. AWS me-south-1

Bright: this event. Dim: the same provider's other open events (1). Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.

4Failure-mode fingerprint

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

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

5Evidence matrix

Official statusOfficial status · Sep 14, 9:22 PM PT: 0 itemsOfficial status · Sep 17, 4:43 PM PT: 0 itemsOfficial status · Sep 20, 12:04 PM PT: 0 itemsOfficial status · Sep 23, 7:25 AM PT: 0 itemsOfficial status · Sep 26, 2:46 AM PT: 0 itemsOfficial status · Sep 28, 10:07 PM PT: 0 itemsOfficial status · Oct 1, 5:28 PM PT: 0 itemsOfficial status · Oct 4, 12:49 PM PT: 0 itemsOfficial status · Oct 7, 8:10 AM PT: 0 itemsOfficial status · Oct 10, 3:31 AM PT: 0 itemsOfficial status · Oct 12, 10:52 PM PT: 0 itemsOfficial status · Oct 15, 6:13 PM PT: 0 itemsOfficial status · Oct 18, 1:33 PM PT: 0 itemsOfficial status · Oct 21, 8:54 AM PT: 0 itemsOfficial status · Oct 24, 4:15 AM PT: 0 itemsOfficial status · Oct 26, 11:36 PM PT: 0 itemsOfficial status · Oct 29, 6:57 PM PT: 0 itemsOfficial status · Nov 1, 1:18 PM PT: 0 itemsOfficial status · Nov 4, 8:39 AM PT: 0 itemsOfficial status · Nov 7, 4:00 AM PT: 0 itemsOfficial status · Nov 9, 11:21 PM PT: 0 itemsOfficial status · Nov 12, 6:42 PM PT: 0 itemsOfficial status · Nov 15, 2:03 PM PT: 0 itemsOfficial status · Nov 18, 9:24 AM PT: 2 itemsNetwork & routingNetwork & routing · Sep 14, 9:22 PM PT: 0 itemsNetwork & routing · Sep 17, 4:43 PM PT: 0 itemsNetwork & routing · Sep 20, 12:04 PM PT: 0 itemsNetwork & routing · Sep 23, 7:25 AM PT: 0 itemsNetwork & routing · Sep 26, 2:46 AM PT: 0 itemsNetwork & routing · Sep 28, 10:07 PM PT: 0 itemsNetwork & routing · Oct 1, 5:28 PM PT: 0 itemsNetwork & routing · Oct 4, 12:49 PM PT: 0 itemsNetwork & routing · Oct 7, 8:10 AM PT: 0 itemsNetwork & routing · Oct 10, 3:31 AM PT: 0 itemsNetwork & routing · Oct 12, 10:52 PM PT: 0 itemsNetwork & routing · Oct 15, 6:13 PM PT: 0 itemsNetwork & routing · Oct 18, 1:33 PM PT: 0 itemsNetwork & routing · Oct 21, 8:54 AM PT: 0 itemsNetwork & routing · Oct 24, 4:15 AM PT: 0 itemsNetwork & routing · Oct 26, 11:36 PM PT: 0 itemsNetwork & routing · Oct 29, 6:57 PM PT: 0 itemsNetwork & routing · Nov 1, 1:18 PM PT: 0 itemsNetwork & routing · Nov 4, 8:39 AM PT: 0 itemsNetwork & routing · Nov 7, 4:00 AM PT: 0 itemsNetwork & routing · Nov 9, 11:21 PM PT: 0 itemsNetwork & routing · Nov 12, 6:42 PM PT: 0 itemsNetwork & routing · Nov 15, 2:03 PM PT: 0 itemsNetwork & routing · Nov 18, 9:24 AM PT: 1 itemEarly signalsEarly signals · Sep 14, 9:22 PM PT: 0 itemsEarly signals · Sep 17, 4:43 PM PT: 0 itemsEarly signals · Sep 20, 12:04 PM PT: 0 itemsEarly signals · Sep 23, 7:25 AM PT: 0 itemsEarly signals · Sep 26, 2:46 AM PT: 0 itemsEarly signals · Sep 28, 10:07 PM PT: 0 itemsEarly signals · Oct 1, 5:28 PM PT: 0 itemsEarly signals · Oct 4, 12:49 PM PT: 0 itemsEarly signals · Oct 7, 8:10 AM PT: 0 itemsEarly signals · Oct 10, 3:31 AM PT: 0 itemsEarly signals · Oct 12, 10:52 PM PT: 0 itemsEarly signals · Oct 15, 6:13 PM PT: 0 itemsEarly signals · Oct 18, 1:33 PM PT: 0 itemsEarly signals · Oct 21, 8:54 AM PT: 0 itemsEarly signals · Oct 24, 4:15 AM PT: 0 itemsEarly signals · Oct 26, 11:36 PM PT: 0 itemsEarly signals · Oct 29, 6:57 PM PT: 0 itemsEarly signals · Nov 1, 1:18 PM PT: 0 itemsEarly signals · Nov 4, 8:39 AM PT: 0 itemsEarly signals · Nov 7, 4:00 AM PT: 0 itemsEarly signals · Nov 9, 11:21 PM PT: 0 itemsEarly signals · Nov 12, 6:42 PM PT: 0 itemsEarly signals · Nov 15, 2:03 PM PT: 0 itemsEarly signals · Nov 18, 9:24 AM PT: 0 itemsNews & chatterNews & chatter · Sep 14, 9:22 PM PT: 0 itemsNews & chatter · Sep 17, 4:43 PM PT: 0 itemsNews & chatter · Sep 20, 12:04 PM PT: 0 itemsNews & chatter · Sep 23, 7:25 AM PT: 0 itemsNews & chatter · Sep 26, 2:46 AM PT: 0 itemsNews & chatter · Sep 28, 10:07 PM PT: 0 itemsNews & chatter · Oct 1, 5:28 PM PT: 0 itemsNews & chatter · Oct 4, 12:49 PM PT: 0 itemsNews & chatter · Oct 7, 8:10 AM PT: 0 itemsNews & chatter · Oct 10, 3:31 AM PT: 0 itemsNews & chatter · Oct 12, 10:52 PM PT: 0 itemsNews & chatter · Oct 15, 6:13 PM PT: 0 itemsNews & chatter · Oct 18, 1:33 PM PT: 0 itemsNews & chatter · Oct 21, 8:54 AM PT: 0 itemsNews & chatter · Oct 24, 4:15 AM PT: 0 itemsNews & chatter · Oct 26, 11:36 PM PT: 0 itemsNews & chatter · Oct 29, 6:57 PM PT: 0 itemsNews & chatter · Nov 1, 1:18 PM PT: 0 itemsNews & chatter · Nov 4, 8:39 AM PT: 0 itemsNews & chatter · Nov 7, 4:00 AM PT: 0 itemsNews & chatter · Nov 9, 11:21 PM PT: 0 itemsNews & chatter · Nov 12, 6:42 PM PT: 0 itemsNews & chatter · Nov 15, 2:03 PM PT: 0 itemsNews & chatter · Nov 18, 9:24 AM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Sep 14, 9:22 PM PT: 0 itemsCoincidence (KEV) · Sep 17, 4:43 PM PT: 0 itemsCoincidence (KEV) · Sep 20, 12:04 PM PT: 0 itemsCoincidence (KEV) · Sep 23, 7:25 AM PT: 0 itemsCoincidence (KEV) · Sep 26, 2:46 AM PT: 0 itemsCoincidence (KEV) · Sep 28, 10:07 PM PT: 0 itemsCoincidence (KEV) · Oct 1, 5:28 PM PT: 0 itemsCoincidence (KEV) · Oct 4, 12:49 PM PT: 0 itemsCoincidence (KEV) · Oct 7, 8:10 AM PT: 0 itemsCoincidence (KEV) · Oct 10, 3:31 AM PT: 0 itemsCoincidence (KEV) · Oct 12, 10:52 PM PT: 0 itemsCoincidence (KEV) · Oct 15, 6:13 PM PT: 0 itemsCoincidence (KEV) · Oct 18, 1:33 PM PT: 0 itemsCoincidence (KEV) · Oct 21, 8:54 AM PT: 0 itemsCoincidence (KEV) · Oct 24, 4:15 AM PT: 0 itemsCoincidence (KEV) · Oct 26, 11:36 PM PT: 0 itemsCoincidence (KEV) · Oct 29, 6:57 PM PT: 0 itemsCoincidence (KEV) · Nov 1, 1:18 PM PT: 0 itemsCoincidence (KEV) · Nov 4, 8:39 AM PT: 0 itemsCoincidence (KEV) · Nov 7, 4:00 AM PT: 0 itemsCoincidence (KEV) · Nov 9, 11:21 PM PT: 0 itemsCoincidence (KEV) · Nov 12, 6:42 PM PT: 0 itemsCoincidence (KEV) · Nov 15, 2:03 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 9:24 AM PT: 0 itemsSep 14, 9:22 PM 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 beganSep 15, 3:22 AM PTORBIT first saw itNov 19, 3:38 AM PTLatest source updateSep 15, 3:22 AM PTLast checkedNov 21, 4:44 AM PT

This event was already open when the NetWeather ledger started (Nov 19, 2026), so the detection gap isn't measurable.

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

  • Open 67d 2h. At that age this is a standing condition, not an incident. It deserves its own runbook and its own SLO conversation.
  • 6 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 19 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-eb63c5dbc2622c87/"><img src="https://www.chyp.ai/dissect/event-nw-eb63c5dbc2622c87/card.svg" alt="AWS Bahrain: Multiple services — Region Availability · ORBIT Outage Dissector" width="600"></a>

Sources & limits

  • Provider-stated: this repeats what the vendor's public status page said. It is not an independent root-cause verification.
  • 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.