Encore quelques problèmes, surtout chez Snapchat, des instances EC2 seraient en cause… 7h de down pour un service comme AWS c’est pas négligeable tout de même !
Le lun. 20 oct. 2025 à 14:14, Stephane Bortzmeyer via frnog <[email protected]> a écrit : > On Mon, Oct 20, 2025 at 09:59:12AM +0200, > Stephane Bortzmeyer via frnog <[email protected]> wrote > a message of 9 lines which said: > > > On (on = Twitter) me dit que Cloudflare et AWS ont tous les deux des > > problèmes ? Ça affecte entre autres Snapchat et Signal (cherchez > > lequel est le plus important). > > Ça semble largement réparé. > > "Oct 20 4:48 AM PDT We continue to work to fully restore new EC2 launches > in US-EAST-1. We recommend EC2 Instance launches that are not targeted to a > specific Availability Zone (AZ) so that EC2 has flexibility in selecting > the appropriate AZ. The impairment in new EC2 launches also affects > services such as RDS, ECS, and Glue. We also recommend that Auto Scaling > Groups are configured to use multiple AZs so that Auto Scaling can manage > EC2 instance launches automatically. > > We are pursuing further mitigation steps to recover Lambda’s polling > delays for Event Source Mappings for SQS. AWS features that depend on > Lambda’s SQS polling capabilities such as Organization policy updates are > also experiencing elevated processing times. We will provide an update by > 5:30 AM PDT. > Oct 20 4:08 AM PDT We are continuing to work towards full recovery for EC2 > launch errors, which may manifest as an Insufficient Capacity Error. > Additionally, we continue to work toward mitigation for elevated polling > delays for Lambda, specifically for Lambda Event Source Mappings for SQS. > We will provide an update by 5:00 AM PDT. > Oct 20 3:35 AM PDT The underlying DNS issue has been fully mitigated, and > most AWS Service operations are succeeding normally now. Some requests may > be throttled while we work toward full resolution. Additionally, some > services are continuing to work through a backlog of events such as > Cloudtrail and Lambda. While most operations are recovered, requests to > launch new EC2 instances (or services that launch EC2 instances such as > ECS) in the US-EAST-1 Region are still experiencing increased error rates. > We continue to work toward full resolution. If you are still experiencing > an issue resolving the DynamoDB service endpoints in US-EAST-1, we > recommend flushing your DNS caches. We will provide an update by 4:15 AM, > or sooner if we have additional information to share." > > > https://health.aws.amazon.com/health/status > > > --------------------------- > Liste de diffusion du FRnOG > http://www.frnog.org/ > --------------------------- Liste de diffusion du FRnOG http://www.frnog.org/
