Fly.io vs Vercel
Independent checks, recorded incidents and SLA terms for these vendors.
30-day window ending
Independent checks
Probes check endpoint responses. A passing check does not confirm that a customer action worked.
| Last 30 days | Fly.io | Vercel |
|---|---|---|
| Passing checks | 100.000% 2,880 conclusive checks | 100.000% 2,880 conclusive checks |
| Response time95th percentile | 107 ms | 455 ms |
Response time uses successful checks only: 95% returned within this duration. Different endpoints and regions can produce different results.
Fly.io · check scope
apiRegion not recorded
api.machines.dev
- First sample in this window
- Latest recorded sample
Vercel · check scope
apiRegion not recorded
api.vercel.com
- First sample in this window
- Latest recorded sample
What the incident records say
Recorded starts in the same 30-day window, excluding maintenance. Vendors report incidents differently; fewer posts don’t prove better reliability.
| Last 30 days | Fly.io | Vercel |
|---|---|---|
| Incidents recorded | 13 | 10 |
| Recorded incident durationMedian | 57m 13 valid durations | 53m 10 valid durations |
Duration uses at least 5 incidents with vendor-supplied starts and recorded closure times. First-observed starts are excluded. 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
Depot builder failures
- Started
- Closed in record
Network issues in US West Coast
- Started
- Closed in record
Sprites API Partial Outage
- Started
- Closed in record
Vercel
Deployment stuck in initializing state
- Started
- Closed in record
Elevated Errors Triggering Deployments
- Started
- Closed in record
Elevated error rate on Connect and Passport
- Started
- Closed in record
Check the terms for your plan
An SLA applies to specific products and plans. Credit eligibility also depends on exclusions, evidence and filing deadlines.