Compare the status, incidents stats and history between Azure and Fly.io
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 01:13 UTC on 13 November 2024, a small number of customers may experience DNS resolution failures when connecting to Azure Storage Accounts. Customers with affected St...
Starting 01:13 UTC November 13, 2024, customers may experience DNS resolution failures related to Azure storage connectivity. Customers may experience failures while attempting to perform managemen...
Starting approximately at 4:00 UTC on 06 November 2024, customers using Azure Databricks in the USGov Arizona and USGov Virginia regions may experience authentication failures when logging into the...
We have noticed a spike in packet loss across the FRA region at around 14:44 UTC caused by an upstream issue. This has recovered since 14:47 UTC, and we are currently monitoring the situation along...
We have noticed a temporary blip in our upstream network(s) between 16:38-16:40 UTC that affected our platform. This has been resolving and we are monitoring for any continuing effects.
We were alerted to elevated error rates for machine creates and updates. A deploy caused a validation error which is now being reverted.
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