Compare the status, incidents stats and history between Azure and Cloud 66
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: As early as 22:00 UTC on 08 Jan 2025, we noticed a partial impact to some of the Azure Services in East US 2 due to a configuration change in a regional networking service. This c...
Starting at 18:44 on 26 December 2024, a power incident in a single availability zone in the South Central US region impacted the availability of multiple Azure services.Impacted ServicesVirtual Ma...
What happened?Between 18:44 UTC on 26 December 2024 and 19:30 UTC on 27 December 2024, a power incident in a single availability zone in the South Central US region impacted the availability for mu...
We are aware of problems when scaling/creating Kubernetes clusters. This appears to be caused by new rate limits imposed by docker hub. The team are working on a solution.
We are currently investigating a number of stuck deployments.
We are aware of issues with our CustomConfig git repositories. This issue impacts direct git access to the CustomConfig git repository. Direct access to CustomConfig pages via the web dashboard and...
14-day free trial · No credit card required · No code required