down.guideby Sazabi

The Down Index, 2026-W46 (live)

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

2026-11-09 to 2026-11-16

152Incident with Webhooks and ActionsGitHub Actions · Partial outage · 1h 50m
- Impact8
- Breadth20
- Duration10
- Reach14
- Acknowledgement0
235Increased timeouts due to surge in anonymous usersGitHub · Degraded · 3h 11m
- Impact8
- Breadth0
- Duration12
- Reach15
- Acknowledgement0
333B2B Environment down, not accessible - Multiple environments affectedOptimizely · Degraded · 1h 31m
- Impact8
- Breadth4
- Duration10
- Reach11
- Acknowledgement0
428[Dedibox VPS] - VPS provisioning failedScaleway · Degraded · 2h 56m
- Impact8
- Breadth0
- Duration11
- Reach9
- Acknowledgement0
527Crypto Payment FailuresBunny.net · Degraded · 2h 40m
- Impact8
- Breadth1
- Duration11
- Reach7
- Acknowledgement0
626[Network infrastructure] - AMS1 ; Room H6 Rack 50 - RPN Switch downScaleway · Degraded · 38m
- Impact8
- Breadth1
- Duration8
- Reach9
- Acknowledgement0
713Features → Prompting DegradedBolt.new · Degraded · 7m
- Impact8
- Breadth0
- Duration5
- Reach0
- Acknowledgement0

← 2026-W45 · Methodology

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