What happened
Amazon Web Services: Lambda cell crossed a capacity threshold and hit a latent defect. Scope: Regional (one Lambda cell).
CHYP.ai · ORBIT // Cloudy_Day Security Suite
OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report
Amazon Web Services: Lambda cell crossed a capacity threshold and hit a latent defect. Scope: Regional (one Lambda cell).
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: Lambda cell crossed a capacity threshold and hit a latent defect. Scope: Regional (one Lambda cell).
AWS Lambda, Amazon STS, AWS Management Console, Amazon EKS and 2 more.
136 catalogued services run on Amazon Web Services (inferred). Hit: Regional (one Lambda cell).
Resolved after 3h 48m.
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 triggered a latent software defect which caused Lambda Execution Environments to be successfully allocated for incoming requests, but never fully utilized by the Lambda Frontend.
Invocations began returning to normal at 1:45 PM PDT; all affected services had fully recovered by 3:37 PM PDT. The defect was triggered when additional compute capacity crossed a capacity threshold that had not previously been reached within a single cell.
Verbatim excerpt from Summary of the AWS Service Event in the Northern Virginia (US-EAST-1) Region (13 Jun 2023).
100% similar · same provider
Kinesis front-end fleet exceeded OS thread limit
CapacityControl planeCascade
85% similar · same provider
DynamoDB DNS automation wrote an empty record it could not repair
Control planeCascade
77% similar · same provider
Kinesis cell-management misidentified healthy hosts during a deployment
Config pushCapacityCascade
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-lambda-2023-06-13/"><img src="https://www.chyp.ai/dissect/m/aws-lambda-2023-06-13/card.svg" alt="Lambda cell crossed a capacity threshold and hit a latent d… · ORBIT Outage Dissector" width="600"></a>