Skip to main content
down.guideby Sazabi
Rankings

The Down Index, 2025-W03

That week's worst incidents, scored 0-100 from impact, breadth, duration, reach and how long the provider took to acknowledge.

2025-01-13 to 2025-01-20

  1. 146Google SERP proxiesApify · Major outage · 4m
    • Impact30
    • Breadth1
    • Duration4
    • Reach11
    • Acknowledgement0
  2. 245Google SERPApify · Major outage · 2m
    • Impact30
    • Breadth1
    • Duration3
    • Reach11
    • Acknowledgement0
  3. 335Unable to login to CodecovCodecov · Partial outage · 13h 18m
    • Impact18
    • Breadth2
    • Duration15
    • Reach0
    • Acknowledgement0
  4. 432HTML and styled dataframes not renderingHex · Partial outage · 1h 22m
    • Impact18
    • Breadth4
    • Duration10
    • Reach0
    • Acknowledgement0
  5. 532Partial OutageAsana · Partial outage · 1h 49m
    • Impact18
    • Breadth3
    • Duration11
    • Reach0
    • Acknowledgement0
  6. 628Config as Code projects might be affected by Github incidentOctopus Deploy · Partial outage · 26m
    • Impact18
    • Breadth3
    • Duration7
    • Reach0
    • Acknowledgement0
  7. 721Pusher dashboard inaccessible for logins with username/passwordPusher · Degraded · 50m
    • Impact8
    • Breadth4
    • Duration9
    • Reach0
    • Acknowledgement0
  8. 819ingestion delays on c22Iterable · Degraded · 2h 22m
    • Impact8
    • Breadth0
    • Duration11
    • Reach0
    • Acknowledgement0
  9. 918File Upload Failure in v6.8 Due to Proxy Route IssueUploadThing · Partial outage · 0m
    • Impact18
    • Breadth0
    • Duration0
    • Reach0
    • Acknowledgement0

← 2025-W02 · 2025-W04 → · Methodology

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