Live / 3DSOutscale / Incident
3DSOutscale: Incident API / API Incident
3DSOutscale · outscale.comCritical outageResolved2026-11-05 09:01 UTC
Public — what happened
Summary
3DSOutscale reported a critical incident affecting its API, which it said had become unavailable; it began investigating at 20:15 UTC on 2026-11-03. By 20:39 UTC the company said the problem had been identified and fixed, with response times back to normal and all services working, and that it would keep monitoring. The incident was marked resolved on 2026-11-05 at 09:01, and the company did not say who was affected or give a cause.
Affected
API, OAPI, Cockpit
Timeline
- Started — 2026-11-03 20:15 UTC
- Investigating — 2026-11-03 20:15 UTC
- Monitoring — 2026-11-03 20:39 UTC
- Resolved — 2026-11-05 09:01 UTC · 36h 46m 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 46, 2026, our weekly internet health report.