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.
Between 7:26 PM and 8:13 PM PDT we experienced increased packet loss and latency in a single availability zone(apne1-az1) in the AP-NORTHEAST-1 Region. The issue has been resolved and services are ...
We are investigating elevated API Error rates and connectivity issues in the AP-SOUTH-2 Region.
Between 6:37 AM and 7:28 AM PDT, some customers experienced intermittent connectivity issues for Direct Connect, Inter-Region, and Internet traffic from the SA-EAST-1 Region to Internet destination...
We've received a flood of networking related alerts from a subset of servers running in LHR. We are not yet sure of the impact on customer workloads.
We are investigating issues with WireGuard over websockets (the default connection mode in flyctl). `flyctl ssh`, `flyctl proxy`, `flyctl logs` commands as well as others may fail. If you are on a...
We’re migrating production traffic over to a new production database. GraphQL queries, including flyctl commands, may be slow.
14-day free trial · No credit card required · No code required