Compare the status, incidents stats and history between Azure and AWS
Every service has different practices when updating its status page, so compare these stats with a grain of salt. E.g., one service can be more aggressive when updating its status page than other so that they will have more incidents, but it doesn't mean it is worse than the other.
There is currently network degradation in East US. The team is addressing this incident and will provide an update as soon as possible.
Impact Statement: Starting at 13:09 UTC on 18 March 2025, a subset of Azure customers in the East US region may experience intermittent connectivity loss and increased network latency sending traff...
We identified a networking issue affecting a subset of datacenters in the East US region. We are currently re-routing affected traffic to minimize the impact on networking-dependent services. Pleas...
We can confirm increased propagation times for invalidations to CloudFront configurations. End-user requests for content from our edge locations are not affected by this issue and are being served ...
We are investigating connectivity issues affecting instances in a single Availability Zone (apne1-az4) in the AP-NORTHEAST-1 Region.
We can confirm increased latencies and increased API error rates for Amazon Bedrock when using Titan, Cohere and Mistral models in the US-EAST-1 Region. We can confirm the impact is related to the ...
14-day free trial · No credit card required · No code required