The State of Status · 122-day view

The Reliability Leaderboard.

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

Generated Oct 22, 2026 · Refreshes every 10 days

Providers
23
Top 23 by usage · 122d window
Total incidents
1,736
All severities, official status pages
Real downtime
1,204.2h
Major + critical only, 48h cap per incident
Clean records
4/23
Zero major/critical in window
Longest outageSlack · 2823.4h
ConcentrationTop 3 caused 60% of downtime

Rankings

Who's in

We rank 23 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 · 33 incidents
99.989%
Avg uptime
Email
1 provider · 13 incidents
99.556%
Avg uptime
Monitoring
4 providers · 61 incidents
99.517%
Avg uptime
Cloud
6 providers · 166 incidents
98.912%
Avg uptime
Developer Tools
1 provider · 81 incidents
98.542%
Avg uptime
AI
2 providers · 228 incidents
98.033%
Avg uptime
Networking
1 provider · 254 incidents
97.629%
Avg uptime
Database
3 providers · 103 incidents
97.584%
Avg uptime
Communication
4 providers · 797 incidents
95.701%
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 October 22, 2026
Next refresh November 1, 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.