Railway vs. Fly.io

Compare the status, incidents stats and history between Railway 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.

Railway

Railway current official status is Operational

Statistics

3
Incidents in the last 7 days
16
Incidents in the last 30 days
37
Incidents in the last 90 days

Latest incidents

Resolved Builds in Europe are degraded and progressing slower than normal

Builds in Europe are degraded and progressing slower than normal

about 24 hours ago Official incident report
Resolved Slow builds

Builds have been delayed over the last ~30 minutes. We're seeing recovery and are monitoring the incident.

Resolved Degraded read/write performance on Railway Volumes

We are currently investigating this incident.

Fly.io

Fly.io current official status is Operational

Statistics

2
Incidents in the last 7 days
6
Incidents in the last 30 days
21
Incidents in the last 90 days

Latest incidents

Resolved Managed Postgres - Connectivity errors in IAD

We are currently investigating elevated connectivity errors between our control plane and a small number of Managed Postgres clusters in IAD.

Resolved Fly.io Dashboard and GraphQL issues

We're investigating elevated database load causing timeouts and elevated 500 error rates on the Fly.io Dashboard and the GraphQL API.

Resolved Elevated GraphQL API issues

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.

Never again lose time looking in the wrong place

14-day free trial · No credit card required · No code required