Compare the status, incidents stats and history between DigitalOcean 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.
As of 12:00 UTC, our Engineering team has again identified an issue with an upstream provider causing packet loss and increased latency in the SGP1 region. Users may have been experiencing degraded...
Our Engineering team is investigating an issue with Monitoring alerts for MongoDB Clusters in all region. During this time, alert policies may be delayed or fail to trigger their configured notific...
As of 08:43 UTC, our Engineering team is investigating reports of networking connectivity issues in our FRA1 and AMS3 regions. Users may have experienced packet loss/latency, timeouts, and related ...
We're seeing an increased number of errors or timeouts when pushing images to registry.fly.io during deploys.
Our Consul cluster is experiencing an outage. This impacts queries to our API, including creating and modifying apps, as well as incoming network requests for recently deployed apps.
Causing intermittent issues deploying to SIN.
Try it out! How much time you'll save your team, by having the outages information close to them?