Skip to main content
Menu
Rankings

Rankings

Which cloud and SaaS providers break the most, from their own posted incidents. How the Down Index scores them.

The week's worst incidents, ranked by Down Index score: 2025-W13, Mar 24 to Mar 30.

  1. 159API downVectara · Major outage · 54m
    • Impact30
    • Breadth20
    • Duration9
    • Reach0
    • Acknowledgement0
  2. 251Automation Run History temporarily unavailableAirtable · Degraded · 3h 51m
    • Impact8
    • Breadth20
    • Duration12
    • Reach11
    • Acknowledgement0
  3. 347ReadMe Hubs are downReadMe · Major outage · 1d 9h
    • Impact30
    • Breadth2
    • Duration15
    • Reach0
    • Acknowledgement0
  4. 440Platform Availability IssuesAttio · Major outage · 1h 6m
    • Impact30
    • Breadth0
    • Duration10
    • Reach0
    • Acknowledgement0
  5. 540Higher than expected timeouts on queriesVectara · Degraded · 3h 12m
    • Impact8
    • Breadth20
    • Duration12
    • Reach0
    • Acknowledgement0
  6. 630Authentication to SambaNova Cloud portal and SambaNova Developer Community ImpactedSambaNova Cloud · Partial outage · 53m
    • Impact18
    • Breadth3
    • Duration9
    • Reach0
    • Acknowledgement0
  7. 730Update logs aren't appearingPulumi Cloud · Partial outage · 1h 44m
    • Impact18
    • Breadth1
    • Duration11
    • Reach0
    • Acknowledgement0
  8. 829Errors loading notes feedSubstack · Partial outage · 28m
    • Impact18
    • Breadth3
    • Duration8
    • Reach0
    • Acknowledgement0
  9. 928Microsoft Outlook service disruptionSuperhuman · Degraded · 3d 19h
    • Impact8
    • Breadth5
    • Duration15
    • Reach0
    • Acknowledgement0
  10. 1028System Errors to access Wasabi servicesWasabi · Degraded · 0m
    • Impact8
    • Breadth20
    • Duration0
    • Reach0
    • Acknowledgement0
  11. 1128ECS Update steps failing to executeOctopus Deploy · Partial outage · 1h 17m
    • Impact18
    • Breadth0
    • Duration10
    • Reach0
    • Acknowledgement0
  12. 1226Degraded performance for commentsReddit · Degraded · 2h 25m
    • Impact8
    • Breadth7
    • Duration11
    • Reach0
    • Acknowledgement0
  13. 1325Intermittent Latency in Web ApplicationRootly · Partial outage · 18m
    • Impact18
    • Breadth0
    • Duration7
    • Reach0
    • Acknowledgement0
  14. 1425Ask AI Service OutageSuperhuman · Degraded · 2h 42m
    • Impact8
    • Breadth5
    • Duration12
    • Reach0
    • Acknowledgement0
  15. 1525Slow performance across hubsReadMe · Degraded · 6d 10h
    • Impact8
    • Breadth2
    • Duration15
    • Reach0
    • Acknowledgement0
  16. 1625Linkedin Pages - IssueLinkedIn · Degraded · 20h 36m
    • Impact8
    • Breadth2
    • Duration15
    • Reach0
    • Acknowledgement0
  17. 1722OpenAI - Increased Error RatesClose · Degraded · 3h 23m
    • Impact8
    • Breadth2
    • Duration12
    • Reach0
    • Acknowledgement0
  18. 1822Mirror Syncs Failing with SQL errorCensus · Degraded · 21m
    • Impact8
    • Breadth7
    • Duration7
    • Reach0
    • Acknowledgement0
  19. 1921Missing Debug Logs in Plivo Console for Messaging and Voice ServicePlivo · Degraded · 42m
    • Impact8
    • Breadth4
    • Duration9
    • Reach0
    • Acknowledgement0
  20. 2020Increased LatencyCohere · Degraded · 3h 19m
    • Impact8
    • Breadth0
    • Duration12
    • Reach0
    • Acknowledgement0
  21. 2119CommandR / CommandR plus: Elevated Error RateCohere · Degraded · 1h 54m
    • Impact8
    • Breadth0
    • Duration11
    • Reach0
    • Acknowledgement0
  22. 2219Pipeline lagRollbar · Degraded · 2h 24m
    • Impact8
    • Breadth0
    • Duration11
    • Reach0
    • Acknowledgement0
  23. 2318Dashboard performance degradationCypress Cloud · Partial outage · 0m
    • Impact18
    • Breadth0
    • Duration0
    • Reach0
    • Acknowledgement0
  24. 2417Elevated ErrorsReddit · Degraded · 24m
    • Impact8
    • Breadth2
    • Duration7
    • Reach0
    • Acknowledgement0
  25. 2515Increased LatencyCohere · Degraded · 21m
    • Impact8
    • Breadth0
    • Duration7
    • Reach0
    • Acknowledgement0

← 2025-W12 · 2025-W14 →

Scoring your own services' incidents the same way? Sazabi does that for your stack.