3DS Outscale incident

[EU-WEST-2] Dégradation performance Api

Minor Resolved View vendor source →

3DS Outscale experienced a minor incident on January 20, 2026 affecting API, lasting 19h 40m. The incident has been resolved; the full update timeline is below.

Started
Jan 20, 2026, 05:57 PM UTC
Resolved
Jan 21, 2026, 01:38 PM UTC
Duration
19h 40m
Detected by Pingoru
Jan 20, 2026, 05:57 PM UTC

Affected components

API

Update timeline

  1. investigating Jan 20, 2026, 05:57 PM UTC

    L’API subit actuellement une forte charge, ce qui entraîne une latence accrue dans le traitement des requêtes. Nos équipes travaillent activement à la résolution du problème. ------------------------------------------------------------ The API is currently experiencing high load, resulting in increased latency in request processing. Our teams are actively working to resolve the issue.

  2. investigating Jan 20, 2026, 06:20 PM UTC

    Afin de pouvoir absorber la forte charge actuelle et d’éviter un effet boule de neige, nous avons dû placer l’API en maintenance temporaire. Nos équipes travaillent à un rétablissement dans les meilleurs délais. ------------------------------------------------------------ In order to handle the current high load and prevent a cascading effect, we have placed the API into temporary maintenance. Our teams are working to restore service as quickly as possible.

  3. monitoring Jan 20, 2026, 06:35 PM UTC

    Le fix a été appliqué. L’incident est maintenant résolu. ------------------------------------------------------------ The fix has been implemented. The incident is resolved now.

  4. monitoring Jan 20, 2026, 06:36 PM UTC

    La maintenance est désormais terminée et le problème est résolu. L’API est de nouveau opérationnelle et nous continuons à surveiller attentivement la situation afin de garantir la stabilité du service. ------------------------------------------------------------ The maintenance is now complete and the issue has been resolved. The API is fully operational again, and we are closely monitoring the situation to ensure service stability.

  5. resolved Jan 21, 2026, 01:38 PM UTC

    This incident has been resolved.