Compare the status, incidents stats and history between Fly.io and Railway
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'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.
we're temporarily pausing deployments while we investgate delays in network propagation
As we're rolling out a routing reconfiguration of our metal edge, a small subset of users may notice latency issues while the new routing configuration is being propagated to all ISPs.
We are currently investigating this incident.
14-day free trial · No credit card required · No code required