3DS Outscale experienced a minor incident on June 2, 2026 affecting Outscale Kubernetes as a Service (OKS), lasting 53m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 02, 2026, 12:02 PM UTC
[FR] Suite à l'incident actuellement en cours sur la région EU-WEST-2 sur son compute and storage: Le mode lecture a été activé sur l'API du service OKS dans la région EU-WEST-2 pour réduire l'impact sur le service OKS. • Les opérations de lecture sur les clusters (ou projects) restent disponibles via l'API du service OKS. • Les opérations de type create, update/upgrade ou delete cluster (ou project) sont temporairement désactivées jusqu’à nouvel ordre via l'API du service OKS. NB: les opérations au sein d'un cluster existant (via la kube-api du control plane de votre cluster) restent disponibles. [ENG] Following the incident currently ongoing in the EU‑WEST‑2 region on its compute and storage : Read mode has been activated on the OKS service API in the EU-WEST-2 to reduce the impact to OKS services. • Read operations on clusters ( or projects) remain available with OKS services API. • Create, update/upgrade or deleted clusters ( or projects ) operations are temporarily disabled until further notice with OKS services API. NB: The operations inside already created clusters (via kube-api of your cluster control plane) remain available.
- identified Jun 02, 2026, 12:56 PM UTC
[FR] Le mode lecture d’OKS pour l’API OKS a été désactivé. Le service est désormais revenu à la normale. [ENG] OKS read mode for the OKS API has been disabled. The service has now returned to normal.
- resolved Jun 02, 2026, 12:56 PM UTC
[FR] Le mode lecture d’OKS pour l’API OKS a été désactivé. Le service est désormais revenu à la normale. [ENG] OKS read mode for the OKS API has been disabled. The service has now returned to normal.