3DS Outscale Outage History

3DS Outscale is up right now

3DS Outscale had 39 outages in the last 2 years totaling 433h 30m of downtime — averaging 1.6 incidents per month.

There were 39 3DS Outscale outages since August 4, 2025 totaling 433h 30m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.outscale.com

Minor June 17, 2026

[EU-WEST-2] OOS : latency

Detected by Pingoru
Jun 17, 2026, 10:47 AM UTC
Resolved
Jun 18, 2026, 08:28 AM UTC
Duration
21h 40m
Affected: Outscale Object storage (OOS)
Timeline · 4 updates
  1. investigating Jun 17, 2026, 10:47 AM UTC

    [FR] Nous constatons des latences actuellement sur le service OOS, notamment sur les actions d'upload. [ENG] We are currently experiencing latency on the OOS service, particularly during upload actions.

  2. identified Jun 17, 2026, 11:38 AM UTC

    [FR] Nous avons identifié la source de l'incident et nous travaillons pour réduire cette latence. [ENG] We have identified the source of the incident and we are working to reduce this latency.

  3. monitoring Jun 17, 2026, 12:10 PM UTC

    [FR] Nous avons déployé un correctif et nous observons un retour à la normale. Nous continuons de surveiller la situation. [ENG] We have deployed a fix and are seeing a return to normal. We continue to monitor the situation.

  4. resolved Jun 18, 2026, 08:28 AM UTC

    [FR] L’incident est résolu et le service fonctionne normalement. [ENG] The incident is resolved and the service is operating normally.

Read the full incident report →

Major June 2, 2026

[EU-WEST-2] Incident Compute and Storage

Detected by Pingoru
Jun 02, 2026, 11:48 AM UTC
Resolved
Jun 03, 2026, 08:15 AM UTC
Duration
20h 26m
Affected: Outscale Object storage (OOS)Persistent storageCompute
Timeline · 4 updates
  1. identified Jun 02, 2026, 11:48 AM UTC

    Un incident est actuellement en cours impactant certaines instances. An incident is in progress impacting some instances.

  2. identified Jun 02, 2026, 12:01 PM UTC

    Nous travaillons pour résoudre au plus vite l'incident.. We are working to resolve the incident as quickly as possible.

  3. monitoring Jun 02, 2026, 12:14 PM UTC

    Un correctif a été mis en place, nous constatons un retour à la normale, nous surveillions la situation. A fix has been implemented, we are seeing a return to normal, we were monitoring the situation.

  4. resolved Jun 03, 2026, 08:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 21, 2026

Degradation of the Storage service on eu-west-2

Detected by Pingoru
May 21, 2026, 04:17 PM UTC
Resolved
May 22, 2026, 06:19 AM UTC
Duration
14h 1m
Affected: Persistent storage
Timeline · 3 updates
  1. investigating May 21, 2026, 04:17 PM UTC

    [FR] Un incident est actuellement en cours sur notre région eu-west-2, entraînant une dégradation du service Storage. Nos équipes sont pleinement mobilisées afin de rétablir la situation dans les meilleurs délais. Nous vous tiendrons informés de l’évolution de l’incident et vous remercions pour votre compréhension. --------------------------- [EN] An incident is currently ongoing in our eu-west-2 region, resulting in a degradation of the Storage service. Our teams are fully mobilized and working to restore the service as quickly as possible. We will keep you informed of any updates and thank you for your understanding.

  2. monitoring May 21, 2026, 04:28 PM UTC

    [FR] Le service devrait être rétabli. Nos équipes travaillent toujours pour assurer la stabilité du service. [EN] The service should be restored. Our teams are still working to ensure the stability of the service.

  3. resolved May 22, 2026, 06:19 AM UTC

    [FR] Le service est rétabli. Nous clôturons ce status. [EN] The service is restored. we are closing this status.

Read the full incident report →

Critical May 21, 2026

[All Region] Cockpit unavailable

Detected by Pingoru
May 21, 2026, 09:11 AM UTC
Resolved
May 22, 2026, 06:18 AM UTC
Duration
21h 7m
Affected: CockpitCockpitCockpitCockpitCockpit
Timeline · 3 updates
  1. investigating May 21, 2026, 09:11 AM UTC

    [FR] : L'accès à cockpit est actuellement indisponible, nous investissons la situation. _______________________________________________________________________________________________ [EN] : Access to cockpit is not available, we are investigating to solved the issus.

  2. monitoring May 21, 2026, 09:14 AM UTC

    [FR] : L'accès à cockpit est actuellement fonctionnel, nous surveillons la situation. _______________________________________________________________________________________________ [EN] : Access to cockpit is now available, we are monitoring the situation.

  3. resolved May 22, 2026, 06:18 AM UTC

    [FR] : L'accès à cockpit est actuellement fonctionnel, nous clôturons ce status. _______________________________________________________________________________________________ [EN] : Access to cockpit is now available, we are closing this status.

Read the full incident report →

Major May 1, 2026

[EU-WEST-2] Incident API / API Incident

Detected by Pingoru
May 01, 2026, 02:30 AM UTC
Resolved
May 02, 2026, 07:17 AM UTC
Duration
1d 4h
Affected: APIWeb UIOAPICockpit
Timeline · 4 updates
  1. investigating May 01, 2026, 02:52 AM UTC

    Nous rencontrons actuellement un incident d'API, nous sommes en cours d'investigation. / We are currently facing an API incident, we are investigating.

  2. monitoring May 01, 2026, 05:52 AM UTC

    Un correctif a été déployé. Nous surveillons actuellement la situation afin de nous assurer de la stabilité du service / A fix has been deployed. We are currently monitoring the situation to ensure the stability of the service.

  3. monitoring May 01, 2026, 05:53 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved May 02, 2026, 07:17 AM UTC

    L’incident est clôturé. La phase de monitoring n’a révélé aucune anomalie. Le service est stable et sous surveillance continue. / The incident is now closed. The monitoring phase did not reveal any further anomalies. The service is stable and remains under continuous monitoring.

Read the full incident report →

Major April 2, 2026

[US-EAST-2] Network Incident

Detected by Pingoru
Apr 02, 2026, 10:37 AM UTC
Resolved
Apr 03, 2026, 01:41 PM UTC
Duration
1d 3h
Affected: Public network
Timeline · 5 updates
  1. investigating Apr 02, 2026, 10:37 AM UTC

    Les nouvelles machines virtuelles créées sur la région US-EAST-2 ne sont pas accessibles depuis Internet. Le réseau interne aux VM reste fonctionnel. Les VM existantes ne sont pas impactées et fonctionnent normalement. Newly created virtual machines in the US-EAST-2 region are currently unreachable from the Internet. Internal VM networking remains functional. Existing VMs are not impacted and continue to operate normally.

  2. investigating Apr 02, 2026, 12:00 PM UTC

    L'incident est toujours en cours. Nos équipes travaillent activement à la résolution du problème. Les nouvelles VM créées sur la région US-EAST-2 restent inaccessibles depuis Internet. Les VM existantes ne sont pas impactées. Une prochaine mise à jour sera communiquée dès que possible. The incident is still ongoing. Our teams are actively working on resolving the issue. Newly created VMs in the US-EAST-2 region remain unreachable from the Internet. Existing VMs are not impacted. A further update will be provided as soon as possible.

  3. identified Apr 02, 2026, 12:12 PM UTC

    La cause de l'incident a été identifiée. Nos équipes travaillent activement à la mise en place d'un correctif. Les nouvelles VM créées sur la région US-EAST-2 restent inaccessibles depuis Internet. Les VM existantes ne sont pas impactées. Une prochaine mise à jour sera communiquée dès que possible. The root cause of the incident has been identified. Our teams are actively working on implementing a fix. Newly created VMs in the US-EAST-2 region remain unreachable from the Internet. Existing VMs are not impacted. A further update will be provided as soon as possible.

  4. monitoring Apr 02, 2026, 12:17 PM UTC

    L'incident est désormais résolu. Les nouvelles machines virtuelles créées sur la région US-EAST-2 sont de nouveau accessibles depuis Internet. L'ensemble des services fonctionnent normalement. Nos équipes restent en surveillance active afin de garantir la stabilité du service. Nous nous excusons pour la gêne occasionnée. The incident has been resolved. Newly created virtual machines in the US-EAST-2 region are now reachable from the Internet. All services are operating normally. Our teams will continue to monitor the situation to ensure service stability. We apologize for any inconvenience caused.

  5. resolved Apr 03, 2026, 01:41 PM UTC

    L'incident est désormais résolu. Les nouvelles machines virtuelles créées sur la région US-EAST-2 sont de nouveau accessibles depuis Internet. L'ensemble des services fonctionnent normalement The incident has been resolved. Newly created virtual machines in the US-EAST-2 region are now reachable from the Internet. All services are operating normally

Read the full incident report →

Minor March 24, 2026

[EU-WEST-2] Incident API

Detected by Pingoru
Mar 24, 2026, 01:34 PM UTC
Resolved
Mar 25, 2026, 10:31 AM UTC
Duration
20h 56m
Affected: API
Timeline · 3 updates
  1. identified Mar 24, 2026, 01:34 PM UTC

    Nous observons actuellement des temps de réponse dégradés sur notre API. Nos équipes sont mobilisées et travaillent activement à la résolution du problème. Nous vous tiendrons informés de l'évolution de la situation. Merci pour votre compréhension. _______________________________________________________________________________________________ We are currently experiencing degraded response times on our API. Our teams are fully mobilized and actively working to resolve the issue. We will keep you informed as the situation evolves. Thank you for your understanding.

  2. monitoring Mar 24, 2026, 03:56 PM UTC

    L’API est actuellement sous surveillance. Nos équipes suivent attentivement son comportement et ses performances afin de garantir la stabilité du service. ______________________________________________________________________________________________ The API is currently being monitored. Our teams are closely monitoring its behavior and performance to ensure service stability.

  3. resolved Mar 25, 2026, 10:31 AM UTC

    Cet incident est désormais résolu. Notre API est à nouveau pleinement opérationnelle et fonctionne normalement. Nous nous excusons pour la gêne occasionnée et vous remercions de votre patience. _______________________________________________________________________________________________ This incident has been resolved. Our API is now fully operational and performing as expected. We apologize for any inconvenience this may have caused and thank you for your patience throughout this incident.

Read the full incident report →

Major March 16, 2026

[EU-WEST-2] Incident API / API Incident

Detected by Pingoru
Mar 16, 2026, 02:10 PM UTC
Resolved
Mar 16, 2026, 05:00 PM UTC
Duration
2h 50m
Affected: APICockpit
Timeline · 5 updates
  1. investigating Mar 16, 2026, 02:30 PM UTC

    [FR] Nous rencontrons actuellement un incident d'API, nous sommes en cours d'investigation. ________________________________________________________________ [EN] We are currently experiencing an API incident and are investigating it.

  2. identified Mar 16, 2026, 02:51 PM UTC

    [FR] Le service devrait être rétabli. Nos équipes travaillent toujours pour assurer la stabilité du service. ________________________________________________________________ [EN] The service should be restored. Our teams are still working to ensure the stability of the service.

  3. identified Mar 16, 2026, 03:48 PM UTC

    [FR] Nos équipes continuent de surveiller activement la situation afin de garantir la stabilité du service. Des vérifications sont toujours en cours et nous restons mobilisés jusqu'à résolution complète. Nous vous tiendrons informés dès qu'une nouvelle mise à jour sera disponible. ________________________________________________________________ [EN] Our teams continue to actively monitor the situation to ensure service stability. Checks are still ongoing and we remain fully mobilised until complete resolution. We will keep you informed as soon as a new update is available.

  4. monitoring Mar 16, 2026, 04:22 PM UTC

    [FR] L’API est actuellement sous surveillance. Nos équipes continuent de suivre attentivement son comportement et ses performances afin de garantir la stabilité du service. ________________________________________________________________ [EN] The API is currently being monitored. Our teams are closely observing its behavior and performance to ensure service stability.

  5. resolved Mar 17, 2026, 03:21 PM UTC

    [FR] L’incident est résolu et le service fonctionne normalement ________________________________________________________________ [EN] The incident has been resolved and the service is operating normally

Read the full incident report →

Major March 13, 2026

[EU-WEST-2] API Incident

Detected by Pingoru
Mar 13, 2026, 01:21 PM UTC
Resolved
Mar 13, 2026, 02:59 PM UTC
Duration
1h 37m
Affected: API
Timeline · 2 updates
  1. investigating Mar 13, 2026, 01:21 PM UTC

    Nous avons rencontré une perturbation partielle du service affectant l'API dans la région eu-west-2. L'incident s'est produit entre 13h15 et 13h50 UTC+1. Bien que le service soit pleinement rétabli, la cause racine n'a pas encore été identifiée. Nos équipes poursuivent leurs investigations et vous tiendront informés dès que de nouveaux éléments seront disponibles. Nous nous excusons pour la gêne occasionnée et vous remercions de votre patience. _______________________________________________________________________________________________ We experienced a partial service disruption affecting the API in the eu-west-2 region. The incident occurred between 13:15 and 13:50 UTC+1. While the service has been fully restored, the root cause has not yet been identified. Our teams are continuing their investigations and will provide further updates as soon as more information becomes available. We apologize for any inconvenience this may have caused and thank you for your patience.

  2. resolved Mar 13, 2026, 02:59 PM UTC

    Nos équipes ont identifié la cause racine : la perturbation était due à des problèmes de latence, qui ont désormais été entièrement résolus de notre côté. Nous nous excusons pour la gêne occasionnée et vous remercions de votre patience. _______________________________________________________________________________________________ Our teams have identified the root cause: the disruption was caused by latency issues, which have now been fully resolved on our end. We apologize for any inconvenience this may have caused and thank you for your patience.

Read the full incident report →

Major February 10, 2026

[US-EAST-2 ][EU-WEST-2] Network Incident

Detected by Pingoru
Feb 10, 2026, 03:00 PM UTC
Resolved
Feb 12, 2026, 04:27 PM UTC
Duration
2d 1h
Affected: Internal networkInternal network
Timeline · 4 updates
  1. investigating Feb 09, 2026, 07:38 PM UTC

    Nous rencontrons actuellement un incident réseau impactant la communication entre les régions us-east-2 et eu-west-2. Nos équipes sont pleinement mobilisées et travaillent activement à l’identification de la cause et à la résolution du problème. --------------------------------------------------------------- We are currently experiencing a network incident impacting communication between the us-east-2 and eu-west-2 regions. Our teams are fully engaged and actively working to identify the root cause and resolve the issue.

  2. monitoring Feb 10, 2026, 04:14 PM UTC

    Nos équipes ont pu identifier l’anomalie, qui se situait sur un transitaire. Des actions ont été effectuées et nous continuons à surveiller la situation de près. --------------------------------------------------------------- Our teams were able to identify the issue, which was located on a transit node. Actions have been taken, and we continue to closely monitor the situation.

  3. monitoring Feb 10, 2026, 04:15 PM UTC

    Nous continuons à surveiller la situation pour détecter tout nouveau problème. --------------------------------------------------------------- We are continuing to monitor for any further issues.

  4. resolved Feb 12, 2026, 04:27 PM UTC

    Le service est désormais entièrement rétabli et fonctionne nominalement. The service is now fully restored and operating normally.

Read the full incident report →

Minor February 10, 2026

[CLOUDGOUV-EU-WEST-1] OOS dégradées

Detected by Pingoru
Feb 10, 2026, 09:59 AM UTC
Resolved
Feb 11, 2026, 09:16 AM UTC
Duration
23h 16m
Affected: Outscale Object storage (OOS)
Timeline · 2 updates
  1. investigating Feb 10, 2026, 09:59 AM UTC

    Nous observons des erreurs sur certains types de requêtes effectuées sur le service. Nous investiguons pour trouver la cause de celles-ci

  2. resolved Feb 11, 2026, 09:16 AM UTC

    La situation est stabilisée, aucun nouvel écart constaté. Incident clôturé.

Read the full incident report →

Minor February 3, 2026

[CLOUDGOUV-EU-WEST-1] Incident sur le service LBU

Detected by Pingoru
Feb 03, 2026, 09:10 AM UTC
Resolved
Feb 04, 2026, 08:28 AM UTC
Duration
23h 17m
Affected: Load Balancing
Timeline · 7 updates
  1. investigating Feb 03, 2026, 09:10 AM UTC

    Nous rencontrons actuellement un incident affectant le service LBU (impact non généralisé à l’ensemble des LBU), entraînant une indisponibilité du transfert de trafic vers les instances backend. We are currently experiencing an incident affecting the LBU service (impact not generalized across all LBUs), causing traffic forwarding to the backend instances to be unavailable.

  2. investigating Feb 03, 2026, 11:25 AM UTC

    Nos équipes restent mobilisés pour résoudre au plus vite l'incident. Our team is still working to solved the incident quickly as possible.

  3. investigating Feb 03, 2026, 12:01 PM UTC

    Nos équipes restent mobilisés pour résoudre au plus vite l'incident. Our team is still working to solved the incident quickly as possible.

  4. monitoring Feb 03, 2026, 12:28 PM UTC

    Nous vous confirmons que l’incident est désormais totalement résolu de notre côté et que le service fonctionne nominalement. Une communication complémentaire vous sera fournie ultérieurement. We confirm that the incident has now been fully resolved on our side, and the service is operating normally. Further communication will be provided at a later stage.

  5. monitoring Feb 03, 2026, 12:29 PM UTC

    Nous continuons à surveiller pour détecter tout problème supplémentaire. We are continuing to monitor for any further issues.

  6. monitoring Feb 03, 2026, 12:29 PM UTC

    Nous vous confirmons que l’incident est désormais totalement résolu de notre côté et que le service fonctionne nominalement. Une communication complémentaire vous sera fournie ultérieurement. We confirm that the incident has now been fully resolved on our side, and the service is operating normally. Further communication will be provided at a later stage.

  7. resolved Feb 04, 2026, 08:28 AM UTC

    Nous vous confirmons que l’incident est désormais totalement résolu de notre côté et que le service fonctionne nominalement. We confirm that the incident has now been fully resolved on our side, and the service is operating normally.

Read the full incident report →

Major January 29, 2026

[CLOUDGOUV-EU-WEST-1] Incident Persistant storage

Detected by Pingoru
Jan 29, 2026, 11:03 AM UTC
Resolved
Jan 30, 2026, 12:33 PM UTC
Duration
1d 1h
Affected: Persistent storage
Timeline · 4 updates
  1. investigating Jan 29, 2026, 11:03 AM UTC

    Nous rencontrons actuellement un problème avec le persistent storage, ce qui peut impacter la disponibilité de certains services. Nos équipes sont en cours d’investigation et nous vous tiendrons informés de l’évolution. Actually we have a problem on our persistent storage, this impact the availability of our services. Our team is currently working to investigate the issue and we going back to you when we have more information.

  2. investigating Jan 29, 2026, 11:06 AM UTC

    Nous continuons notre investigation sur l'incident. We are still investigate the issue.

  3. monitoring Jan 29, 2026, 11:08 AM UTC

    Le problème lié au persistent storage semble désormais résolu. Les services fonctionnent normalement et nous restons en phase de monitoring afin de nous assurer de la stabilité complète de la plateforme. This issue is linked to the persistant storage seems to be resolved. The services is working normally and we keep monitoring the complet stability of the plateform.

  4. resolved Jan 30, 2026, 12:33 PM UTC

    Nous vous confirmons que l’incident est désormais totalement résolu de notre côté et que le service fonctionne nominalement. We confirm that the incident has now been fully resolved on our side, and the service is operating normally.

Read the full incident report →

Major January 28, 2026

[CLOUDGOUV-EU-WEST-1] Incident API / API Incident

Detected by Pingoru
Jan 28, 2026, 02:00 PM UTC
Resolved
Jan 30, 2026, 12:34 PM UTC
Duration
1d 22h
Affected: API
Timeline · 3 updates
  1. investigating Jan 28, 2026, 02:07 PM UTC

    Nous rencontrons actuellement un incident d'API, nous sommes en cours d'investigation. We are currently experiencing an API issue and are actively investigating.

  2. monitoring Jan 28, 2026, 02:11 PM UTC

    Le service n’est plus dégradé et fonctionne normalement. The service is no longer degraded and is fully operational.

  3. resolved Jan 30, 2026, 12:34 PM UTC

    Nous vous confirmons que l’incident est désormais totalement résolu de notre côté et que le service fonctionne nominalement. We confirm that the incident has now been fully resolved on our side and the service is operating normally.

Read the full incident report →

Minor January 20, 2026

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

Detected by Pingoru
Jan 20, 2026, 05:57 PM UTC
Resolved
Jan 21, 2026, 01:38 PM UTC
Duration
19h 40m
Affected: API
Timeline · 5 updates
  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.

Read the full incident report →

Minor January 16, 2026

[EU-WEST-2] Incident Api

Detected by Pingoru
Jan 16, 2026, 05:55 PM UTC
Resolved
Jan 16, 2026, 10:00 PM UTC
Duration
4h 4m
Affected: Outscale Object storage (OOS)OAPICockpitOutscale Kubernetes as a Service (OKS)
Timeline · 9 updates

Read the full incident report →

Major December 16, 2025

[US-EAST-2 ] Network Incident

Detected by Pingoru
Dec 16, 2025, 03:02 PM UTC
Resolved
Dec 16, 2025, 03:15 PM UTC
Duration
13m
Affected: API
Timeline · 3 updates
  1. investigating Dec 16, 2025, 02:20 PM UTC

    Nous rencontrons actuellement un incident réseau, nous sommes en cours d'investigation. We are currently facing a network incident, we are investigating.

  2. identified Dec 16, 2025, 03:13 PM UTC

    L'origine de l'incident a été identifié nos équipes sont mobilités pour un retour le plus rapide dans un état nominal. The root cause of the incident has been identified; our teams are mobilized for the fastest possible return to a nominal state.

  3. resolved Dec 16, 2025, 03:36 PM UTC

    Depuis 16h15, la region est de retour dans un état normale. Nous fermons l'incident. Since 4:15 PM, the region has returned to normal state. We are closing the incident.

Read the full incident report →

Minor December 15, 2025

[EU-WEST-2] OOS Degraded Performance

Detected by Pingoru
Dec 15, 2025, 09:07 AM UTC
Resolved
Dec 16, 2025, 08:40 AM UTC
Duration
23h 32m
Affected: Outscale Object storage (OOS)
Timeline · 3 updates
  1. identified Dec 15, 2025, 09:07 AM UTC

    La latence sur la région EUW2 est dégradée depuis 04:00 du matin, les équipes sont mobilisée sur le problème We observe latency in the EUW2 region since 04:00 this morning, and the teams are currently working to resolve the issue.

  2. monitoring Dec 15, 2025, 10:57 AM UTC

    Une charge exceptionnelle a été détectée sur le service. Des actions de mitigation ont été mises en place et le service est désormais stabilisé. La situation reste sous surveillance. An exceptional load was detected on the service. Mitigation actions have been applied and the service is now stable. The situation remains under monitoring.

  3. resolved Dec 16, 2025, 08:40 AM UTC

    L’incident est désormais résolu, les performances du service Outscale Object Storage (OOS) en région eu-west-2 sont revenues à la normale. The incident has been resolved, and Outscale Object Storage (OOS) performance in the eu-west-2 region has returned to normal.

Read the full incident report →

Notice December 5, 2025

[SUPPORT] Zendesk Incident

Detected by Pingoru
Dec 05, 2025, 09:00 AM UTC
Resolved
Dec 05, 2025, 09:16 AM UTC
Duration
15m
Timeline · 2 updates
  1. investigating Dec 05, 2025, 09:05 AM UTC

    Nous rencontrons actuellement un incident avec notre plateforme de ticketing Zendesk, ce qui entraîne une inaccessibilité à la gestion des tickets. La création de tickets reste cependant disponible en utilisant l’application mobile Zendesk. We are currently experiencing an incident with our Zendesk ticketing platform, resulting in the ticket management interface being inaccessible. However, ticket creation is still available using the Zendesk mobile application.

  2. resolved Dec 05, 2025, 09:16 AM UTC

    L’incident affectant notre plateforme Zendesk a été entièrement résolu. Les services sont de nouveau opérationnels et vous pouvez à présent créer des tickets normalement par les canaux habituels. The issue affecting our Zendesk platform has been fully resolved. All services are now operational again, and you can once more create tickets normally through the usual channels.

Read the full incident report →

Minor December 2, 2025

[EU-WEST-2] Incident impacting instances

Detected by Pingoru
Dec 02, 2025, 07:09 PM UTC
Resolved
Dec 02, 2025, 08:18 PM UTC
Duration
1h 9m
Affected: Compute
Timeline · 4 updates
  1. investigating Dec 02, 2025, 07:08 PM UTC

    Un incident affectant la région eu-west-2 impacte actuellement certaines instances de nos clients. Nos équipes sont en cours d’investigation afin d’identifier la cause et de rétablir le service dans les meilleurs délais. An incident affecting the eu-west-2 region is currently impacting some customer instances. Our teams are investigating the root cause and working to restore normal service as quickly as possible .

  2. investigating Dec 02, 2025, 07:09 PM UTC

    Nous continuons nos investigation sur l'incident We are continuing to investigate this issue.

  3. investigating Dec 02, 2025, 07:10 PM UTC

    We are continuing to investigate this issue.

  4. resolved Dec 02, 2025, 08:18 PM UTC

    Suite à l’incident réseau survenu à 18h58, nous avons identifié la source du problème et nos équipes ont appliqué les actions correctives nécessaires. Le service est désormais stabilisé et à nouveau disponible. Cependant, afin de rétablir pleinement la connexion à vos environnements, un redémarrage de vos machines virtuelles est nécessaire. Following the network incident that occurred at 18:58, we have identified the source of the issue and our teams have implemented the necessary corrective actions. The service is now stable and available again. However, in order to fully restore connectivity to your environments, a restart of your virtual machines is required.

Read the full incident report →

Minor November 26, 2025

[US-WEST-1] Public Network Incident

Detected by Pingoru
Nov 26, 2025, 11:45 PM UTC
Resolved
Nov 27, 2025, 08:00 AM UTC
Duration
8h 15m
Affected: Public network
Timeline · 2 updates
  1. identified Nov 26, 2025, 08:17 PM UTC

    Incident started at 16:29 UTC. We are currently experiencing an issue with our transit provider, causing intermittent packet loss. Investigations are ongoing.

  2. resolved Nov 27, 2025, 08:04 AM UTC

    Since 00:45 UTC, the problem has been identified and resolved by our transport provider. We maintained continuous monitoring throughout the night, and this morning our public network is now fully stable.

Read the full incident report →