The Down Index, 2025-W05
That week's worst incidents, scored 0-100 from impact, breadth, duration, reach and how long the provider took to acknowledge.
2025-01-27 to 2025-02-03
- 146Increased errors and significantly degraded performance across APIVoyage AI · Major outage · 16m
- 245Proxy outageBrowserbase · Partial outage · 21h 52m
- 345IP Address Change for Database RequestsCensus · Major outage · 31m
- 445Mural notification emailsMural · Major outage · 4h 26m
- 544Projects not loadingHex · Major outage · 1h 20m
- 643Web app outageHex · Major outage · 46m
- 729Partial outage across API request handling and doc processingCoda · Partial outage · 1h 26m
- 826Disk failure in some Regional DatabasesUpstash · Partial outage · 0m
- 923Customers receiving 3200 errors and inaccessible endpointsngrok · Degraded · 18m
- 1023Issues with the Grammarly Editor and Account ManagementGrammarly · Degraded · 2h 50m
- 1121Slack and Teams Integration DegradationCypress Cloud · Degraded · 3h 23m
- 1221Degraded sync performanceCensus · Degraded · 13m
- 1320The Grammarly Editor is not working as expectedGrammarly · Degraded · 1h 41m
- 1420Campaigns may experience getting queued and not sentMailjet · Degraded · 2h 26m
- 1520Generative AI assistance is not availableGrammarly · Degraded · 2h 22m
- 1619Issues connecting to roomsDaily · Degraded · 38m
- 1718Elevated error rates on subscription related endpointsOrb · Partial outage · 0m
- 1818Test Replay DegradationCypress Cloud · Degraded · 53m
← 2025-W04 · 2025-W06 → · Methodology
Scoring your own services' incidents the same way? Sazabi does that for your stack.