← Back to context

Comment by JohnMakin

11 hours ago

Explain why how why when aws lambda when out in us-east-1 a year or so ago every other region had intense issues they couldn’t quickly recover from? and their incident report explained this exact fact? where’s your info coming from? I follow this stuff very closely because my livelihood depends on it.

Do you have a link to this incident report? I don’t recognize this one.

  • https://aws.plainenglish.io/aws-outage-october-20-2025-a-cas...

    here’s one third party, it was pretty well documented as a control plane failure in us-east-1

    • Here's the official story from AWS:

      https://aws.amazon.com/message/101925/

      This, too, was contained to us-east-1:

      "While the event started at 11:48 PM PDT on October 19 and ended at 2:20 PM PDT on October 20, there were three distinct periods of impact to customer applications. First, between 11:48 PM on October 19 and 2:40 AM on October 20, Amazon DynamoDB experienced increased API error rates in the N. Virginia (us-east-1) Region. Second, between 5:30 AM and 2:09 PM on October 20, Network Load Balancer (NLB) experienced increased connection errors for some load balancers in the N. Virginia (us-east-1) Region. This was caused by health check failures in the NLB fleet, which resulted in increased connection errors on some NLBs. Third, between 2:25 AM and 10:36 AM on October 20, new EC2 instance launches failed and, while instance launches began to succeed from 10:37 AM, some newly launched instances experienced connectivity issues which were resolved by 1:50 PM."