Compare the status, incidents stats and history between Linode 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.
Our team is investigating a service issue affecting MongoDB on the Managed Databases service. During this time, users will be unable to provision new MongoDB clusters.
Our team is investigating a connectivity issue in our EU-Central (Frankfurt) data center. During this time, users may experience connection timeouts and errors for all services deployed in this dat...
Our team is investigating a service issue affecting the Managed Databases service. During this time, users may experience issues when attempting to use these systems. We will share additional up...
Issues with multiple pacific ocean underwater cables providing connectivity to / from SIN with certain providers.
We are currently investigating this issue.
There appears to be a lot more connection timeouts happening due to stale state. This was likely caused by the same change that caused the postgres clusters issues earlier.
Try it out! How much time you'll save your team, by having the outages information close to them?