Live / 3DSOutscale / Incident
3DSOutscale: API incident on EU-WEST-2
3DSOutscale · outscale.comMinor incidentResolved2026-10-26 12:57 UTC
Public — what happened
Summary
3DSOutscale said its API on EU-WEST-2 was running slower than usual, which could mean longer waits for responses, and it began looking into the problem on 2026-10-24 at 13:42 UTC. On 2026-10-25 at 10:44 UTC the company said the issue had been identified and dealt with, with response times back to normal and all services working as expected. It said it would keep watching to make sure things stayed stable, and the incident was marked resolved on 2026-10-26 at 12:57. The company rated it as minor.
Affected
API
Timeline
- Started — 2026-10-24 13:42 UTC
- Investigating — 2026-10-24 13:42 UTC
- Monitoring — 2026-10-25 10:44 UTC
- Resolved — 2026-10-26 12:57 UTC · 47h 16m 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.