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 13:09 UTC on 18 March 2025, a subset of Azure customers in the East US region may experience intermittent connectivity loss and increased network latency sending traff...
We identified a networking issue affecting a subset of datacenters in the East US region. We are currently re-routing affected traffic to minimize the impact on networking-dependent services. Pleas...
Starting at 13:09 UTC on 18 March 2025, a subset of Azure customers in the East US region may experience intermittent connectivity loss and increased network latency. We are aware of the issue and ...
We are investigating timeouts connecting to registry.fly.io. Customers may experience slower image pushes and pulls within Fly Machines.
New machine/volume creates in LHR regions are currently unavailable as there is no host capacity available. Any workloads currently running will continue to run; it is also still possible to updat...
New machine/volume creates in IAD regions may fail as there is no host capacity available. Any workloads currently running will continue to run; it is also still possible to update existing machin...
14-day free trial · No credit card required · No code required