Compare the status, incidents stats and history between Fly.io and Heroku
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.
We are currently investigating elevated connectivity errors between our control plane and a small number of Managed Postgres clusters in IAD.
We're investigating elevated database load causing timeouts and elevated 500 error rates on the Fly.io Dashboard and the GraphQL API.
We're seeing a higher number of 500s when calling the Machines API, running a deploy, or attempting to access the dashboard. We're currently investigating the issue.
Engineers have identified that affected applications are isolated to a subset of Basic dynos in the US region of the Common Runtime. Other dyno types, Heroku services, Dashboard, and CLI are not af...
Triage and remediation of DNS and Applications states have been completed.
Build's Release Phase are operating normally.
14-day free trial · No credit card required · No code required