The State of Status · 122-day view

The Reliability Leaderboard.

How 20 popular dev infra providers performed over the last 122 days. How we measure →

Generated Jun 27, 2026 · Refreshes every 10 days

Providers
20
Top 20 by usage · 122d window
Total incidents
1,614
All severities, official status pages
Real downtime
664h
Major + critical only, 48h cap per incident
Clean records
3/20
Zero major/critical in window
Longest outageVercel · 339.2h
ConcentrationTop 3 caused 56% of downtime

Rankings

Who's in

We rank 20 popular dev infrastructure providers that meet three rules:

  • 01Widely used — providers most engineering teams depend on (no long-tail listings).
  • 02At least 122 days of monitoring history, so the score isn't flattered by a short window.
  • 03Actively polled by Stawatch right now — we count what the provider published on its official status page.

By category

Payments
1 provider · 19 incidents
99.994%
Avg uptime
Communication
3 providers · 607 incidents
99.796%
Avg uptime
Email
2 providers · 33 incidents
99.762%
Avg uptime
Monitoring
3 providers · 54 incidents
99.668%
Avg uptime
Networking
1 provider · 273 incidents
99.078%
Avg uptime
Developer Tools
1 provider · 90 incidents
98.976%
Avg uptime
Cloud
4 providers · 178 incidents
98.308%
Avg uptime
Database
3 providers · 77 incidents
98.292%
Avg uptime
AI
2 providers · 283 incidents
96.625%
Avg uptime

How we calculate this

Data window

The last 122 days (~4 months) of incidents reported on each provider's official status page. Stawatch polls every tracked status page on a continuous schedule and stores start/end times locally. We re-aggregate every 10 days.

Uptime %

Counts only major and critical incidents — minor regional notices and informational entries providers leave open for weeks would otherwise inflate downtime in misleading ways.

uptime% = max(0, 1 − weighted_down / window_minutes) × 100

Per-incident cap

Each incident's contribution to weighted downtime is capped at 48 hours. Beyond that horizon the entry is almost always a long-tail monitoring state rather than active outage. Anything genuinely prolonged is still surfaced separately under Notable outages.

Severity weights

  • critical × 1.0
  • major × 1.0
  • minor × 0.0
  • none × 0.0

Total incidents

The incident count column reports every entry regardless of severity, so a provider with lots of minor regional issues is still visible in the data — even when their uptime % stays high.

Limitations

We can only see what providers publish. Internal incidents, silent regressions, and unreported degradations don't show up here. Provider-perceived severity is taken at face value.

Generated June 27, 2026
Next refresh July 7, 2026
Get alerts

Don't wait for X to tell you it's down.

Stawatch watches every provider on this page (and 200+ more) and pings your team in Slack, email, or any webhook the moment something breaks.