Live  /  3DSOutscale  /  Incident

3DSOutscale: [EU-WEST-2] Incident API degradation

3DSOutscale · outscale.comMajor incidentResolved2026-11-10 07:07 UTC
Public — what happened

Summary

3DSOutscale said its API in the eu-west-2 region began performing poorly on 5 November 2026 at 19:49 UTC, and it marked the incident as major. Early on 6 November the company said the problem had been identified and resolved, but later that day it reported the API was partly unavailable again. At 12:49 UTC it said a fix had been applied and service looked normal while it kept watching, and the incident was marked resolved on 10 November at 07:07.

Affected

API, OAPI, Cockpit, Outscale Kubernetes as a Service (OKS)

As listed on 3DSOutscale’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the 3DSOutscale status & history page.

Related: 3DSOutscale status & history. SquidGrid is not affiliated with 3DSOutscale.