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.
Impact Statement: Starting at 07:33 UTC on 16 Sep 2023, you have been identified as a customer using Azure SQL Database in East US who may experience issues when trying to connect to your Database....
Starting at 08:30 UTC on 30 August 2023, a subset of customers with workloads hosted in the Australia East may be experiencing difficulties accessing and managing resources deployed in this region....
Impact Statement: Starting at approximately 08:30 UTC on 30 August 2023, a utility power surge in the Australia East region tripped a subset of the cooling units offline in one datacenter, within o...
We can confirm that customers are experiencing elevated error rates for cluster upgrade operations in the US-EAST-1 Region. This is a result of actions we took to prevent additional customer impact...
We are investigating increased error rates and increased delays in network propagation for newly launched EC2 instances in a single Availability Zone (use1-az2) in US-EAST-1 Region. EC2 System Stat...
We are investigating increased networking latencies and errors affecting multiple Availability Zones (usw2-az1 and usw2-az2) in the US-WEST-2 Region.
Try it out! How much time you'll save your team, by having the outages information close to them?