Service comparison

Fly.io vs. Railway

Fly.io vs. Railway: uptime, incident frequency and resolution times, head-to-head.

Last 90 days · 79 incidents total · From each provider's official status page

Head-to-head

90-day summary

Uptime over time

Availability across windows

Window Fly.io Railway Δ
Last 24 hours
6.60%
100.00%
-93.40 pp
Last 7 days
71.33%
100.00%
-28.67 pp
Last 30 days
87.44%
100.00%
-12.56 pp
Last 90 days
93.55%
100.00%
-6.45 pp

Uptime is the share of each window with no incident open on the provider's official status page. Δ is percentage-point difference (Fly.io minus Railway). Higher is better.

Incidents 90-day

Severity breakdown

  • Fly.io

    79 total

    29 major 50 minor
    • Median resolution

      52m

    • Longest incident

      48h 10m

  • Railway

    0 total

    0 major 0 minor
    • Median resolution

      —

    • Longest incident

      —

Recent activity

Last 5 incidents, side-by-side

  • Fly.io logo

    Fly.io

    • Nov 12

      GitHub connections reset - sign in with GitHub again to restore GitHub deploys

      3h 37m

      Minor
    • Nov 12

      LAX region outage

      2d 10m

      Major
    • Nov 11

      Intermittent errors pushing images to Fly.io Registry

      < 1m

      Minor
    • Nov 6

      IPv6 egress issues on a subset of IAD hosts

      22m

      Minor
    • Nov 4

      Emergency network maintenance on a subset of hosts in ORD

      14m

      Minor
  • Railway logo

    Railway

    No incidents on record.

Bottom line

Railway wins

Railway edges out on 90-day uptime.

Fly.io posted 93.55% vs. 100.00% for Railway (Δ -6.45 pp). Incidents: 79 vs. 0 (+79).

Where would your uptime rank against Railway?

Pulsetic is website uptime monitoring. Aim it at a website you run and build a 90-day record of your own.

10 monitors free, email alerts on failure and recovery. No credit card.