- Detected by Pingoru
- Oct 05, 2026, 01:44 PM UTC
- Resolved
- Oct 05, 2026, 05:13 PM UTC
- Duration
- 3h 28m
Affected: API
Timeline · 3 updates
-
investigating Oct 05, 2026, 01:44 PM UTC
Nous rencontrons actuellement un incident d'API, nous sommes en cours d'investigation. We are currently facing an API incident, we are investigating.
-
monitoring Oct 05, 2026, 02:04 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 continue to closely monitor its behavior and performance to ensure service stability.
-
resolved Oct 05, 2026, 05:13 PM UTC
[FR] L'incident est actuellement résolu. [EN] The incident is now resolved
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2026, 12:00 PM UTC
- Resolved
- Aug 05, 2026, 01:00 PM UTC
- Duration
- 59m
Affected: Outscale Kubernetes as a Service (OKS)
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2026, 11:53 AM UTC
- Resolved
- Aug 05, 2026, 12:34 PM UTC
- Duration
- 40m
Affected: Compute
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Aug 03, 2026, 06:59 PM UTC
- Resolved
- Aug 04, 2026, 05:13 PM UTC
- Duration
- 22h 13m
Affected: Outscale Object storage (OOS)
Timeline · 3 updates
-
investigating Aug 03, 2026, 06:59 PM UTC
Nous constatons actuellement une indisponibilité affectant les buckets chiffrés du service OOS. Nos équipes sont mobilisées pour identifier la cause du problème et rétablir le service dans les meilleurs délais. We are currently experiencing an outage affecting encrypted buckets in the OOS service. Our teams are working to identify the cause of the issue and restore service as quickly as possible.
-
monitoring Aug 03, 2026, 07:39 PM UTC
Nous ne constatons plus d'erreurs et les buckets chiffrés du service OOS devraient à nouveau être pleinement fonctionnels. Nos équipes poursuivent néanmoins la surveillance afin de confirmer le retour complet à la normale. We are no longer seeing errors, and the encrypted OOS buckets should once again be fully functional. However, our teams are continuing to monitor the situation to confirm a complete return to normal.
-
resolved Aug 04, 2026, 05:13 PM UTC
L'incident affectant les buckets chiffrés du service OOS est désormais résolu. Le service est de nouveau pleinement opérationnel et nous ne constatons plus d'anomalies. La période de surveillance est terminée et l'incident est clos. The incident affecting encrypted buckets in the OOS service has now been resolved. The service is fully operational again, and we are no longer observing any issues. The monitoring period has been completed, and the incident is now closed.
Read the full incident report →
- Detected by Pingoru
- Jul 25, 2026, 10:43 AM UTC
- Resolved
- Jul 25, 2026, 12:51 PM UTC
- Duration
- 2h 7m
Affected: API
Timeline · 3 updates
-
investigating Jul 25, 2026, 11:10 AM UTC
[FR] Nous rencontrons actuellement une dégradation des performances de l'API , pouvant entraîner des temps de réponse plus élevés que d'habitude. Nos équipes sont en cours d'investigation. [EN] We are currently experiencing API performance degradation, which may result in higher-than-normal response times. Our teams are actively investigating the issue
-
identified Jul 25, 2026, 11:42 AM UTC
[FR] Nos équipes ont identifié le problème et travaillent activement à sa résolution. Nous mettons tout en œuvre pour rétablir un fonctionnement normal de l'API dans les meilleurs délais. [EN] Our teams have identified the issue and are actively working to resolve it. We are making every effort to restore normal API performance as quickly as possible.
-
resolved Jul 25, 2026, 12:51 PM UTC
[FR] L'incident est désormais résolu. La performance de l'API dans la région EU-WEST-2 est revenue à la normale. [EN] The incident has been resolved. API performance in the EU-WEST-2 region has returned to normal.
Read the full incident report →
- Detected by Pingoru
- Jul 22, 2026, 10:15 PM UTC
- Resolved
- Jul 23, 2026, 08:08 AM UTC
- Duration
- 9h 53m
Affected: Outscale Object storage (OOS)Persistent storagePublic network
Timeline · 8 updates
Read the full incident report →
- Detected by Pingoru
- Jul 09, 2026, 01:35 PM UTC
- Resolved
- Jul 10, 2026, 01:48 PM UTC
- Duration
- 1d
Affected: Degradation of the Storage service on eu-west-2
Timeline · 4 updates
-
investigating Jul 09, 2026, 01:35 PM UTC
[EN] We are currently investigating potential service disruptions affecting the eu-west-2 region. Our teams are actively working to identify the root cause of the issue and restore normal service as quickly as possible. We will keep you informed of any developments and provide further updates as soon as more information becomes available. [FR] Nous enquêtons actuellement sur d'éventuelles perturbations affectant la région eu-west-2. Nos équipes sont mobilisées afin d'identifier l'origine du problème et de rétablir la situation dans les meilleurs délais. Nous vous tiendrons informés de toute évolution dès que de nouvelles informations seront disponibles.
-
monitoring Jul 09, 2026, 01:44 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.
-
monitoring Jul 09, 2026, 01:54 PM UTC
[FR] Le service est désormais sous surveillance. Si vous rencontrez toujours le problème, il peut être nécessaire de redémarrer la VM ou de démonter puis remonter le volume en read-write mode afin de le résoudre. Nos équipes continuent de surveiller la situation. [EN] The service is now under monitoring. If you are still experiencing the issue, a reboot of the VM or unmounting and remounting the volume in read-write mode may be necessary to resolve it. Our teams continue to monitor the situation.
-
resolved Jul 10, 2026, 01:48 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 →
- Detected by Pingoru
- Jul 09, 2026, 01:30 PM UTC
- Resolved
- Jul 09, 2026, 03:05 PM UTC
- Duration
- 1h 34m
Affected: Outscale Kubernetes as a Service (OKS)
Timeline · 2 updates
-
investigating Jul 09, 2026, 01:39 PM UTC
[FR] Un incident affectant l'API du service OKS est actuellement en cours dans la région CLOUDGOUV-EU-WEST-1. Nos équipes travaillent à sa résolution dans les meilleurs délais. 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. ________________________________________________________________ [EN] An incident affecting the OKS service API is currently impacting the CLOUDGOUV-EU-WEST-1 region. Our teams are working to resolve it as quickly as possible. 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.
-
resolved Jul 09, 2026, 03:05 PM UTC
[FR] L'incident est désormais résolu. [EN] The incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2026, 02:51 PM UTC
- Resolved
- Jul 03, 2026, 07:51 AM UTC
- Duration
- 16h 59m
Affected: Persistent storage
Timeline · 4 updates
-
investigating Jul 02, 2026, 02:51 PM UTC
[FR] Un incident sur le stockage est actuellement en cours sur la région ; nos équipes travaillent pour résoudre au plus vite l'incident. [ENG] An Incident related to storage is currently affecting the region; our teams are working to resolve it as quickly as possible.
-
monitoring Jul 02, 2026, 03:07 PM UTC
[FR] Le service est désormais sous surveillance. Si vous rencontrez toujours le problème, un redémarrage ou un fsck, suivi d'un umount puis d'un mount du système de fichiers, peut être nécessaire pour résoudre la situation. Nos équipes continuent de surveiller la situation. [EN] The service is now under monitoring. If you are still experiencing the issue, a restart or running fsck, followed by an umount and mount of the filesystem, may be necessary to resolve the issue. Our teams continue to monitor the situation.
-
monitoring Jul 02, 2026, 03:21 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jul 03, 2026, 07:51 AM UTC
[FR] L'incident est actuellement résolu et nous n'observons plus d'impact depuis hier. [EN] The incident is now resolved, and we have observed no impact since yesterday.
Read the full incident report →
- Detected by Pingoru
- Jun 24, 2026, 09:19 PM UTC
- Resolved
- Jun 24, 2026, 09:30 PM UTC
- Duration
- 11m
Timeline · 2 updates
-
identified Jun 24, 2026, 09:19 PM UTC
[FR] : Les incidents en cours provoquent actuellement l'indisponibilité du numéro du support. Vous pouvez nous joindre directement au : +33 7 72 34 44 24 [ENG] : Ongoing incidents are currently causing the support number to be unavailable. You can contact us directly at : +33 7 72 34 44 24
-
resolved Jun 24, 2026, 10:39 PM UTC
[FR] Le numéro normal du support est de nouveau disponible. [ENG] The standard support number is available again.
Read the full incident report →
- Detected by Pingoru
- Jun 24, 2026, 08:17 PM UTC
- Resolved
- Jun 26, 2026, 10:00 AM UTC
- Duration
- 1d 13h
Affected: Outscale Object storage (OOS)APIInternal networkCockpit
Timeline · 6 updates
-
identified Jun 24, 2026, 08:17 PM UTC
[FR] Nous rencontrons actuellement un incident qui touche l'API ; nos équipes travaillent à sa résolution. [ENG] We are currently experiencing an issue affecting the API; our teams are working to resolve it.
-
identified Jun 24, 2026, 09:03 PM UTC
[FR] Nos équipes travaillent actuellement sur l'incident ; nous espérons un retour le plus vite possible. [ENG] Our teams are currently working on the incident; we hope for a resolution as soon as possible.
-
identified Jun 24, 2026, 09:15 PM UTC
[FR] L'incident sur notre région provoque actuellement l'indisponibilité de l'API et d'OOS [ENG] The incident on our region is currently causing the API and OOS to be unavailable.
-
identified Jun 24, 2026, 09:37 PM UTC
[FR] Nous constatons des améliorations sur la région. [ENG] We are seeing improvements in the region.
-
monitoring Jun 24, 2026, 11:35 PM UTC
[FR] Nous constatons que la situation est stable sur la région. on continue de surveiller l'incident [ENG] We are seeing that the situation is stable in the region. we are continue to monitored the incident
-
resolved Jun 26, 2026, 10:00 AM UTC
[FR] : L’incident impactant la région est désormais entièrement résolu et clôturé. La situation est stabilisée et les systèmes fonctionnent normalement. Une surveillance sera maintenue de manière préventive afin de garantir la stabilité du service. Nous vous remercions pour votre patience et vous présentons nos excuses pour la gêne occasionnée. [ENG] : The incident affecting the region is now fully resolved and has been closed. The situation is stable and systems are operating normally. Preventive monitoring will remain in place to ensure continued service stability. We sincerely apologize for any inconvenience caused and thank you for your patience.
Read the full incident report →
- 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
-
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.
-
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.
-
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.
-
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 →
- 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
-
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.
-
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.
-
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.
-
resolved Jun 03, 2026, 08:15 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
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.
-
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 →
- 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
-
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.
-
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.
-
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 →
- 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
-
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.
-
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.
-
monitoring May 01, 2026, 05:53 AM UTC
We are continuing to monitor for any further issues.
-
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 →
- Detected by Pingoru
- Apr 07, 2026, 04:56 PM UTC
- Resolved
- Apr 07, 2026, 08:15 PM UTC
- Duration
- 3h 19m
Affected: Outscale Kubernetes as a Service (OKS)
Timeline · 2 updates
Read the full incident report →
- 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
-
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.
-
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.
-
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.
-
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.
-
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 →
- 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
-
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.
-
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.
-
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 →
- 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
-
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.
-
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.
-
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.
-
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.
-
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 →
- 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
-
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.
-
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 →
- Detected by Pingoru
- Mar 04, 2026, 01:45 PM UTC
- Resolved
- Mar 05, 2026, 07:14 AM UTC
- Duration
- 17h 28m
Affected: Internal networkOutscale Kubernetes as a Service (OKS)
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 12:24 PM UTC
- Resolved
- Feb 12, 2026, 04:25 PM UTC
- Duration
- 1d 4h
Affected: APIDNSCockpitOutscale Kubernetes as a Service (OKS)
Timeline · 21 updates
Read the full incident report →
- 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
-
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.
-
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.
-
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.
-
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 →
- 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
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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 →
