Skip to main content

Fly.io vs Vercel

Front door check counts, what each vendor’s status page recorded and SLA terms for these vendors.

30-day window ending

Front door checks

Every 15 minutes we send a request to a documented endpoint for each vendor from a single CheckUpstream location and count the answers. A reachable front door does not confirm that a customer action worked.

Front door check counts: Fly.io and Vercel
Last 30 daysFly.ioVercel
Front door reachableOut of checks with a clear answer
  • 2,255 of 2,255

    checks to api.machines.dev

  • 2,255 of 2,255

    checks to api.vercel.com

Checks 15 minutes apart cannot see disruptions shorter than that. Each vendor is checked at its own endpoints, so the counts cover different things.

Fly.io · check scope

  • api.machines.devapi · No vendor region

    Front door reachable in 2,255 of 2,255 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    3 more checks gave no clear answer and are not counted.

    First check in this window
    Latest clear answer
View Fly.io record

Vercel · check scope

  • api.vercel.comapi · No vendor region

    Front door reachable in 2,255 of 2,255 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    3 more checks gave no clear answer and are not counted.

    First check in this window
    Latest clear answer
View Vercel record

What each vendor’s status page says

Recorded starts in the same 30-day window, excluding maintenance. Vendors report incidents differently; fewer posts don’t prove better reliability.

Recorded incidents: Fly.io and Vercel
Last 30 daysFly.ioVercel
Incidents recorded

16

4

Recorded incident durationMedian

1h 1m

14 valid durations

Too few dated records

3 valid durations

Duration uses at least 5 incidents with vendor-supplied starts and recorded closure times. First-observed starts are excluded, as are records posted with one time for start and resolution. A record may close when a post disappears or our tracking period expires; this does not confirm recovery. A missing closure time does not mean an outage is ongoing.

Fly.io says

  • Emergency maintenance in GRU

    Started
    Closed in record
    Source incident
  • GitHub connections reset - sign in with GitHub again to restore GitHub deploys

    Started
    Closed in record
    Source incident
  • LAX region outage

    Started
    Closed in record
    Source incident

Vercel says

  • Delays in observability data

    Started
    Closed in record
    Source incident
  • Elevated Sandbox and Blob request latency and errors

    Started
    Closed in record
    Source incident
  • Build delays and degraded Vercel Dashboard performance

    Started
    Closed in record
    Source incident

Check the terms for your plan

An SLA applies to specific products and plans. Credit eligibility also depends on exclusions, evidence and filing deadlines.

Fly.io

No public terms recorded here.

Review Fly.io SLA guide

Vercel

1 public term record.

Product not specified

Review Vercel SLA guide