Compare the status, incidents stats and history between Fly.io and Render
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.
We are experiencing a delay in starting workloads for a subset of users in the Oregon region. This includes builds, crons, and service (including free tier) scale-ups.
We are currently investigating this issue.
GitHub is experiencing system issues that will result in failures with operations where Render interacts with GitHub. Please see https://www.githubstatus.com/incidents/y7lb2rg4btd7 for GitHub speci...
14-day free trial · No credit card required · No code required