Live / 3DSOutscale / Incident
3DSOutscale: [US-WEST-1] OOS Incident
3DSOutscale · outscale.comMajor incidentResolved2026-10-23 13:01 UTC
Public — what happened
Summary
3DSOutscale said an incident was affecting its OOS service in the US-WEST-1 region, which it rated as major. The company reported the problem starting around 15:20 UTC on 22 October 2026 and said its teams were working on it. By 15:46 UTC it said a fix had been deployed and the service restored, with monitoring to confirm stability. The incident was marked resolved at 13:01 UTC on 23 October, and no cause was given in the text provided.
Affected
Outscale Object storage (OOS)
Timeline
- Started — 2026-10-22 15:20 UTC
- Investigating — 2026-10-22 15:38 UTC
- Monitoring — 2026-10-22 15:46 UTC
- Resolved — 2026-10-23 13:01 UTC · 21h 40m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach 3DSOutscale against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for 3DSOutscale: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the 3DSOutscale report →
More from 3DSOutscale
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.