Compare the status, incidents stats and history between Linode and Azure
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.
Our team has identified an issue affecting our Block Storage service in our US-ORD (Chicago), US-IAD (Washington, D.C.) and Los Angeles (LAX3) data centers between the following times: - Chicago (...
Our team is investigating an issue affecting connectivity in our US-IAD (Washington) data center. During this time, users may experience intermittent connection timeouts and errors for all services...
Our team has identified an issue which introduced latency to the Object Storage service between 14:18 UTC and 16:29 UTC on January 15, 2025. At this time we have been able to correct the issues aff...
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...
14-day free trial · No credit card required · No code required