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
Rankings
Most reliable
Top 5 by uptime % — ties broken by usage popularity.
Least reliable
Bottom 5 by uptime %. Lots of major or critical incidents on official status pages.





Notable outages
Longest single major or critical incidents in the window.
SlackMajorChat functionality unavailable on Slack Help pageJun 26, 2026 · still open117d 15hDuration
SlackMajorReceiving reminders in Slack issueJul 24, 2026 · still open89d 22hDuration
SlackMajorIssue sending messages to channels via certain workflowsJul 24, 2026 · still open89d 16hDuration
SlackMajorFeature Degradation Affecting the Receipt of Emails in SlackJul 28, 2026 · still open85d 22hDuration
SlackMajorTrouble Using Search Bar For Some AdminsAug 6, 2026 · still open76d 2hDuration
Most incidents reported
Count, not severity — high counts often mean fine-grained regional reporting.
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
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.
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.






