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: Beginning around 14:47 EDT on 27 September 2024, we are investigating an issue with Azure Resource Manager (ARM) impacting Azure US Gov regions. Impacted customers may experience ...
We are currently investigating reports of customers who were unable to access Azure services in the UK South region. Though our investigation to determine the contributing factor is ongoing, we can...
We are currently investigating reports of customers being unable to access Azure services in the UK South region. Further information will be provided as it becomes available.
We are investigating Increased API Error Rates for Multiple services in the US-EAST-2 Region.
From 7:58 AM to 9:10 AM PDT we observed issues registering and deregistering load balancer targets to Application Load Balancers (ALBs) in the US-EAST-1 Region. Engineers were engaged at 8:10 AM an...
Beginning at 12:40 PM PDT customers began to experience elevated latency and errors across multiple service APIs in the US-WEST-2 (Oregon) Region. The issue is with a subsystem that handles request...
How much time you'll save your team, by having the outages information close to them?
14-day free trial · No credit card required · Cancel anytime