Oops, we did it again... AWS US-EAST-1 Oct 28 3:36 PM PDT Earlier today some EC2 launches within the use1-az2 Availability Zone (AZ) experienced increased latencies for EC2 instance launches. We communicated with affected customers via the AWS Personal Health Dashboard shortly after the issue began. This issue has been resolved and EC2 instance launches are operating normally, however some request throttles are currently in place for the use1-az2 Availability Zone (AZ), which are gradually being removed. Customers may experience “request limit exceeded” in this AZ while these throttles are in place; retries should resolve the issue.

Впрочем, уже починили: Oct 28 10:57 PM PDT Between 9:00 AM and 10:43 PM PDT, we experienced increased latencies for EC2 instance launches within the use1-az2 Availability Zone (AZ) in the US-EAST-1 Region. In addition we experienced increased ECS task and pod launch failure rates. This impacted services that depend on ECS, including Fargate, EMR Serverless, MWAA, CodeBuild, EKS, Glue, AppRunner, DataSync, MWAA and AWS Batch. As part of the recovery effort, we temporarily throttled ECS operations in three impacted cells. At 10:43 PM, we had fully mitigated the issue. The issue has been resolved and the service is operating normally. Azure (пока чинят) Starting at approximately 16:00 UTC on 29 October, 2025, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. We have confirmed that an inadvertent configuration change was the trigger event for this issue. И тоже, кстати, надавно падал - предыдущий инцидент был три недели назад.

Cloudflare (сидят с попкорном, надо полагать) We are closely monitoring the situation with Azure, Cloudflare remains available and will report any issues impacting our customers.

Кучно пошло, в общем. @snakeslair #thereisnoclouds