Compare the status, incidents stats and history between AWS 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.
We are investigating increased error rates and latencies for DynamoDB, which is affecting other AWS services in the US-EAST-1 Region.
We are investigating increased API error rates for applications hosted on App Runner in the AP-SOUTHEAST-1 Region.
We are investigating increased processing times for queued queries in the US-WEST-2 Region.
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.
14-day free trial · No credit card required · No code required