Compare the status, incidents stats and history between Heroku and Linode
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 engineers are still continuing to investigate on the issue. Details are to follow.
We are still communicating with upstream provider for the resolution progress and platform is stable since 01:22 UTC, We will post another update in 120 minutes, or as soon as one is available.
Engineers are still investigating the potential issue.
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 service issue affecting the Linode Cloud Manager and API. This is related to the emergency maintenance in US-Central (Dallas): - https://status.linode.com/incidents/m1b4...
We are investigating reports of failed Managed Database Clusters. Customers may experience connectivity issues or see the status of their cluster change to "Failed" or "Degraded" during this time.
Try it out! How much time you'll save your team, by having the outages information close to them?