What happened
Amazon Web Services: Internal-network surge, retries, and control-plane API failures. Scope: Regional (control planes); existing data-plane workloads largely continued.
CHYP.ai · ORBIT // Cloudy_Day Security Suite
OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report
Amazon Web Services: Internal-network surge, retries, and control-plane API failures. Scope: Regional (control planes); existing data-plane workloads largely continued.
Severe storm
Drag or press Play to replay what was public at each moment. Each dot links to its evidence. Lanes are kept separate on purpose.
Amazon Web Services: Internal-network surge, retries, and control-plane API failures. Scope: Regional (control planes); existing data-plane workloads largely continued.
EC2 control-plane APIs, Elastic Load Balancing APIs, Route 53 APIs, AWS Management Console and 4 more.
136 catalogued services run on Amazon Web Services (inferred). Hit: Regional (control planes); existing data-plane workloads largely continued.
Resolved after 6h 52m.
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. Dependencies are inferred from public information.
Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.
Failure modes as stated in the vendor's own post-incident report (Meltdown Index).
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.
This resulted in a large surge of connection activity that overwhelmed the networking devices between the internal network and the main AWS network, resulting in delays for communication between these networks. These delays increased latency and errors for services communicating between these networks, resulting in even more connection attempts and retries.
Network devices fully recovered at 2:22 PM PST. Some services recovered later (STS full recovery 4:28 PM PST; new EC2 launches 2:40 PM PST). Duration uses the official 2:22 PM PST network-device recovery.
Verbatim excerpt from Summary of the AWS Service Event in the Northern Virginia (US-EAST-1) Region.
77% similar · same provider
Lambda cell crossed a capacity threshold and hit a latent defect
CapacityControl planeCascade
77% similar · same provider
Kinesis front-end fleet exceeded OS thread limit
CapacityControl planeCascade
66% similar · same provider
DynamoDB DNS automation wrote an empty record it could not repair
Control planeCascade
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.
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.
Everything above as one shareable, citable capsule with a content hash.
JSON capsuleMarkdownShare card (SVG)
Open Amazon Web Services in the War Room →Status page →
<a href="https://www.chyp.ai/dissect/m/aws-use1-2021-12-07/"><img src="https://www.chyp.ai/dissect/m/aws-use1-2021-12-07/card.svg" alt="Internal-network surge, retries, and control-plane API fail… · ORBIT Outage Dissector" width="600"></a>