Public Cloud Outage History
Public Cloud is up right nowPingoru has recorded 205 incidents for Public Cloud: 205 in the last 12 months and 69 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 28 | 57 of 720 (8%) |
| May 2026 | 20 | 285 of 744 (38%) |
| June 2026 | 31 | 268 of 720 (37%) |
| July 2026 | 28 | 235 of 744 (32%) |
| August 2026 | 22 | 288 of 744 (39%) |
| September 2026 | 21 | 397 of 720 (55%) |
| October 2026 | 24 | 300 of 592 (51%) |
Incidents, newest first
Major April 13, 2026 [GRA][Network] - Network incident notification 2h 28m GRA1, GRA3, GRA5, GRA7 and 2 more
Started Apr 13, 2026, 09:30 AM UTC· resolved Apr 13, 2026, 11:58 AM UTC
- investigating Apr 13, 2026, 09:30 AM UTC
We are currently investigating an incident affecting our Network offering, which is causing temporary availability issue in the GRA region. Here are some supplementary details : Start time : 13/04/2026 09:25 UTC Impacted Service(s) : For these regions, you might have issues with network connectivity or managing your Public networks. Your existing network configurations remain active. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- investigating Apr 13, 2026, 11:05 AM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Most services are available again. 80% are available again. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Apr 13, 2026, 11:58 AM UTC
We are pleased to inform you that the incident affecting our Network has been resolved. Start time : 13/04/2026 09:25 UTC End time : 13/04/2026 11:57 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Minor April 8, 2026 [GRA9][Containers & Orchestration] - Managed Kubernetes Service Incident Notification 47m GRA9
Started Apr 08, 2026, 09:33 AM UTC· resolved Apr 08, 2026, 10:20 AM UTC
- identified Apr 08, 2026, 09:33 AM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific region GRA9. Here are some supplementary details : Start time : 08/04/2026 09:06 UTC Impacted Service(s) : Managed Kubernetes Service clusters in GRA9 are temporarily facing latency. Customers Impact : Customers are temporarily facing latency while trying to access their Managed Kubernetes Service clusters. Root Cause : This incident is caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/vwqd4hm52ytq Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Apr 08, 2026, 10:20 AM UTC
We are pleased to inform you that the incident affecting our Containers & Orchestration offer in GRA9 region has been resolved. Start time : 08/04/2026 09:06 UTC End time : 08/04/2026 10:12 UTC Root Cause : This was caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/vwqd4hm52ytq We apologize for any inconvenience caused and appreciate your understanding.
Major April 8, 2026 [GRA9][Network] - API Network incident notification 1h GRA, GRA9, GRA9, GRA9 and 2 more
Started Apr 08, 2026, 09:19 AM UTC· resolved Apr 08, 2026, 10:19 AM UTC
- investigating Apr 08, 2026, 09:19 AM UTC
We are currently experiencing an event affecting our Public Cloud Network API offer in GRA9 region. Start time : 08/04/2026 09:06 UTC Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible. We apologize for any inconvenience caused and appreciate your understanding.
- investigating Apr 08, 2026, 09:24 AM UTC
We are currently investigating an incident affecting our Network offering, which is causing temporary availability issue in the Public Cloud Network API. Here are some supplementary details : Start time : 08/04/2026 09:06 UTC Impacted Service(s) : The API for the GRA9 region is temporarily unavailable. Customers Impact : Customers are temporarily unable to create, start, manage their Public Cloud instances and create or attach new volumes. Instances already running are not impacted. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Apr 08, 2026, 10:19 AM UTC
We are pleased to inform you that the incident affecting our Public Cloud Network API offer in GRA9 region has been resolved. Start time : 08/04/2026 09:06 UTC End time : 08/04/2026 10:12 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Major April 2, 2026 [EU][Identity, Security & Operations] - Service Logs Incident Notification 3h 4m GRA
Started Apr 02, 2026, 10:42 AM UTC· resolved Apr 02, 2026, 01:46 PM UTC
- investigating Apr 02, 2026, 10:42 AM UTC
We are currently experiencing an event affecting our Identity, Security & Operations offer. Start time : 02/04/2026 10:10 UTC Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible. We apologize for any inconvenience caused and appreciate your understanding.
- investigating Apr 02, 2026, 10:48 AM UTC
We are currently investigating an incident affecting our Identity, Security & Operations offering, which is causing temporary availability issue in the EU. Here are some supplementary details : Start time : 02/04/2026 10:10 UTC Impacted Service(s) : Service Logs is unavailable Customers Impact : Customers can no longer access logs for their managed services or subscribe to logs for new ones. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution.
- identified Apr 02, 2026, 01:19 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our offer on the EU region. Here are some supplementary details : Start time : 02/04/2026 10:10 UTC Impacted Service(s) : Service Logs is unavailable Customers Impact : Customers can no longer access logs for their managed services or subscribe to logs for new ones. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Apr 02, 2026, 01:46 PM UTC
We are pleased to inform you that the incident affecting our Identity, Security & Operations has been resolved. Start time : 02/04/2026 10:10 UTC End time : 02/04/2026 13:45 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Major April 1, 2026 [GRA9][Network] - Load Balancer incident notification 59m GRA9
Started Apr 01, 2026, 03:06 PM UTC· resolved Apr 01, 2026, 04:05 PM UTC
- investigating Apr 01, 2026, 02:54 PM UTC
We are currently experiencing an event affecting our Load Balancer offer in GRA9. Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible. We apologize for any inconvenience caused and appreciate your understanding.
- investigating Apr 01, 2026, 03:06 PM UTC
We are currently investigating an incident affecting our Load Balancer offer, which is causing temporary availability issue in the GRA9 region. Here are some supplementary details : Start time : 01/04/2026 13:54 UTC Impacted Service(s) : Load balancer in GRA9 region is temporarily unavailable. Customers Impact : Some customers are temporarily unable to to perform load balancer management operations in GRA9. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Apr 01, 2026, 04:05 PM UTC
We are pleased to inform you that the incident affecting our Network on our Load Balancer offer in GRA9 has been resolved. Start time : 01/04/2026 13:54 UTC End time : 01/04/2026 16:00 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Notice April 1, 2026 [GRA][Containers & Orchestration] - Managed Private Registry incident notification 1h 51m GRA
Started Apr 01, 2026, 02:15 PM UTC· resolved Apr 01, 2026, 04:07 PM UTC
- monitoring Apr 01, 2026, 02:15 PM UTC
Service has been fully restored since 01/04/2026 14:04 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 01/04/2026 13:54 UTC Impacted Service(s) : Managed private Registry was temporarily unavailable in GRA region. Customers Impact : Some customers were temporarily unable to access and use their registries in the specified region. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Apr 01, 2026, 04:07 PM UTC
We are pleased to inform you that the incident affecting our Managed Private Registry offer in GRA has been resolved. Start time : 01/04/2026 13:54 UTC End time : 01/04/2026 14:04 UTC Root Cause : This incident is caused by another incident: https://public-cloud.status-ovhcloud.com/incidents/vfzbjp0jbm0t We apologize for any inconvenience caused and appreciate your understanding.
Minor March 31, 2026 [GRA1/7/11][Storage] - Block Storage incident notification 3h 45m GRA1, GRA3, GRA7
Started Mar 31, 2026, 02:42 PM UTC· resolved Mar 31, 2026, 06:28 PM UTC
- identified Mar 31, 2026, 02:42 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Storage offer on the specific regions GRA1, GRA7 and GRA11. Here are some supplementary details : Start time : 31/03/2026 14:08 UTC Impacted Service(s) : A low performance is being observed on Block Storage in the specified regions. Customers Impact : Some customers are facing latency when trying to access and use their Block Storage located in GRA1, GRA7 and GRA11. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- identified Mar 31, 2026, 05:22 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Our teams implemented a fix and the service is now recovering. Ongoing Actions : During the recovery, customers may experience slightly reduced performance. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Mar 31, 2026, 06:28 PM UTC
We are pleased to inform you that the incident affecting our Storage in GRA1, GRA7 and GRA11 regions has been resolved. Start time : 31/03/2026 14:08 UTC End time : 31/03/2026 18:25 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Notice March 30, 2026 [GRA11][Compute - Instance] - Some instances incident notification 3h 14m GRA11
Started Mar 30, 2026, 08:50 AM UTC· resolved Mar 30, 2026, 12:05 PM UTC
- identified Mar 30, 2026, 08:50 AM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer in the specific region. Here are some supplementary details : Start time : 30/03/2026 07:22 UTC Impacted Service(s) : Some instances are suddenly unreachable. Customers Impact : Some customers are temporarily unable to access and use their instances in the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Mar 30, 2026, 12:05 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offer has been resolved. Start time : 30/03/2026 07:22 UTC End time : 30/03/2026 12:00 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Major March 26, 2026 [GRA11][Compute Instance] - Public Cloud instances Incident Notification 3h 22m GRA11
Started Mar 26, 2026, 02:57 PM UTC· resolved Mar 26, 2026, 06:20 PM UTC
- investigating Mar 26, 2026, 02:57 PM UTC
We are currently investigating an incident affecting our Compute Instance offering, which is causing temporary availability issue in GRA11 region. Here are some supplementary details : Start time : 26/03/2026 10:25 UTC Impacted Service(s) : Some hosts in the specific region are temporarily unreachable. Customers Impact : Some customers are temporarily unable to access and use their Public Cloud instances in GRA11 region. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Mar 26, 2026, 06:20 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance has been resolved. Start time : 26/03/2026 10:25 UTC End time : 26/03/2026 18:15 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Major March 25, 2026 [GRA/SBG][Storage] - Swift Object Storage incident notification 16m GRA, SBG
Started Mar 25, 2026, 06:17 PM UTC· resolved Mar 25, 2026, 06:34 PM UTC
- investigating Mar 25, 2026, 06:17 PM UTC
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the GRA/SBG. Here are some supplementary details : Start time : 25/03/2026 17:24 UTC Impacted Service(s) : PUT request on the PCS services has been impacted. Customers Impact : Customers may encounter 498 errors when uploading files to their PCS services in GRA/SBG. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Mar 25, 2026, 06:34 PM UTC
We are pleased to inform you that the incident affecting our Storage has been resolved. Start time : 25/03/2026 17:24 UTC End time : 25/03/2026 18:00 UTC Root Cause : This incident was caused by a software configuration. We apologize for any inconvenience caused and appreciate your understanding.
Notice March 23, 2026 [GLOBAL][Identity, Security & Operations] - Logs Data Platform incident notification – BHS, GRA
Started Mar 23, 2026, 11:36 AM UTC· resolved Mar 23, 2026, 11:36 AM UTC
- resolved Mar 23, 2026, 11:36 AM UTC
We had an incident on Identity, Security & Operations offer which has now been resolved. Here are some supplementary details : Start time : 23/03/2026 09:11 UTC End time : 23/03/2026 11:26 UTC Impacted Service(s) : IAM authentication is currently not functionnal on Graylog / OSD / API Customers Impact : Some customers may have experienced difficulties accessing logs via Graylog/OSD/API. Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We thank you for your understanding and patience throughout this incident.
Major March 22, 2026 [GLOBAL][Compute - Instance] - IAM Login incident notification 4h 14m SGP1, WAW1, GRA1, DE1 and 21 more
Started Mar 22, 2026, 04:55 PM UTC· resolved Mar 22, 2026, 09:10 PM UTC
- identified Mar 22, 2026, 04:55 PM UTC
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in the GLOBAL region. Here are some supplementary details : Start time : 22/03/2026 10:55 UTC Impacted Service(s) : Some instances in the GLOBAL region are unreachable using IAM (Identity and Access Management). Customers Impact : Some customers are temporarily unable to login to their Public Cloud instances using IAM (Identity and Access Management). Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution.
- identified Mar 22, 2026, 06:09 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : A fix has been implemented by our teams. Ongoing Actions : Our teams are currently recovering impacted services. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- identified Mar 22, 2026, 07:56 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Our teams are still working on recovering the impacted services. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Mar 22, 2026, 09:10 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offer has been resolved. Start time : 22/03/2026 10:55 UTC End time : 22/03/2026 20:51 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Major March 19, 2026 [BHS1][Compute - Instance] - Some instances incident notification 37m BHS1
Started Mar 19, 2026, 06:49 PM UTC· resolved Mar 19, 2026, 07:26 PM UTC
- identified Mar 19, 2026, 06:49 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific region. Here are some supplementary details : Start time : 19/03/2026 18:16 UTC Impacted Service(s) : Some instances in the BHS1 region are unreachable. Customers Impact : Some customers are temporarily unable to access and use their instances in the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Mar 19, 2026, 07:26 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offer has been resolved. Start time : 19/03/2026 18:16 UTC End time : 19/03/2026 19:21 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Major March 18, 2026 [GRA11][Containers & Orchestration] - MKS Incident Notification 4h 31m GRA11
Started Mar 18, 2026, 04:02 PM UTC· resolved Mar 18, 2026, 08:34 PM UTC
- identified Mar 18, 2026, 04:02 PM UTC
We are currently investigating an incident affecting our MKS offering, which is causing temporary availability issue in GRA11. Here are some supplementary details : Start time : 18/03/2026 13:30 UTC Impacted Service(s) : The creation of new octavia loadbalancers through MKS may have delay. Customers Impact : No issue on existing loadbalancers. Root Cause : https://public-cloud.status-ovhcloud.com/incidents/4s4tt0lqmmk4 Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Mar 18, 2026, 08:34 PM UTC
We are pleased to inform you that the incident affecting our Containers & Orchestration has been resolved. Start time : 18/03/2026 13:30 UTC End time : 18/03/2026 20:08 UTC Root Cause : https://public-cloud.status-ovhcloud.com/incidents/4s4tt0lqmmk4 We apologize for any inconvenience caused and appreciate your understanding.
Major March 18, 2026 [GRA11][Network] - Load Balancer Incident Notification 5h 19m GRA11
Started Mar 18, 2026, 02:54 PM UTC· resolved Mar 18, 2026, 08:13 PM UTC
- investigating Mar 18, 2026, 02:54 PM UTC
We are currently investigating an incident affecting our Load Balancer Octavia offering, which is causing temporary issue in GRA11. Here are some supplementary details : Start time : 18/03/2026 13:30 UTC Impacted Service(s) : Pending operations are slowed down but the data plane is not impacted. Customers Impact : Customers may experience delays when performing load balancer management operations. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Mar 18, 2026, 08:13 PM UTC
We are pleased to inform you that the incident affecting our Load Balancer Octavia offering has been resolved. Start time : 18/03/2026 13:30 UTC End time : 18/03/2026 20:08 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Major March 16, 2026 [GLOBAL][Databases] - MongoDB Incident Notification 18h BHS, DE, GRA, EU-WEST-PAR and 7 more
Started Mar 16, 2026, 03:20 PM UTC· resolved Mar 17, 2026, 09:21 AM UTC
- investigating Mar 16, 2026, 03:20 PM UTC
We are currently investigating an incident affecting our MongoDB offering, which is causing temporary availability issue in GRA/DE/UK/RBX/MUM/WAW/SGP/SBG/BHS/EU-WEST-PAR/EU-SOUTH-MIL. Here are some supplementary details : Start time : 16/03/2026 14:00 UTC Impacted Service(s) : New service creation is temporarily unavailable. Existing database services continue to run. Customers Impact : Customers are temporarily unable to order new MongoDB services in regions GRA/DE/UK/RBX/MUM/WAW/SGP/SBG/BHS/EU-WEST-PAR/EU-SOUTH-MIL Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- investigating Mar 16, 2026, 03:21 PM UTC
We are continuing to investigate this issue.
- monitoring Mar 16, 2026, 08:05 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The teams have rolled out a fix that has resolved the issue. It is being closely monitored to ensure long-term stability. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Mar 17, 2026, 09:21 AM UTC
We are pleased to inform you that the incident affecting MongoDB services has been resolved. Start time : 16/03/2026 14:00 UTC End time : 16/03/2026 20:05 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Notice March 13, 2026 [US][Storage] - S3 Object Storage incident notification – US-EAST-VA-1, US-WEST-OR-1
Started Mar 13, 2026, 11:33 AM UTC· resolved Mar 13, 2026, 11:33 AM UTC
- resolved Mar 13, 2026, 11:33 AM UTC
We had an incident on Storage offer which has now been resolved. Here are some supplementary details : Start time : 13/03/2026 07:20 UTC End time : 13/03/2026 08:15 UTC Impacted Service(s) : Severe network traffic disruptions on the S3 object storage clusters between 7:20 and 7:30 UTC. From 7:30 to 8:15 UTC, network instability persisted, causing 500/503 errors and authentication problems. Customers Impact : Customers may have encountered 500/503 errors and authentication issues. Root Cause : This incident was caused by this incident : https://network.status-ovhcloud.com/incidents/dt09splp43wh We thank you for your understanding and patience throughout this incident.
Notice March 12, 2026 [GRA11][Containers & Orchestration] - Load Balancer/Managed Kubernetes Service incident notification – GRA11, GRA11
Started Mar 12, 2026, 07:43 PM UTC· resolved Mar 12, 2026, 07:43 PM UTC
- resolved Mar 12, 2026, 07:43 PM UTC
We had an incident on Containers & Orchestration offer that impacted the Load Balancer and Managed Kubernetes Service in GRA11 which has now been resolved. Here are some supplementary details : Start time : 12/03/2026 15:00 UTC End time : 12/03/2026 19:30 UTC Impacted Service(s) : Network perturbations were temporarily observed on the Load Balancer and Managed Kubernetes Service in GRA11. Customers Impact : Customers were temporarily facing issues using the Load Balancer and Managed Kubernetes Service in the specified region. Root Cause : This incident was caused by this incident: https://public-cloud.status-ovhcloud.com/incidents/2t9ck6jjtylr We thank you for your understanding and patience throughout this incident.
Major March 12, 2026 [GRA11][Compute - Instance] - New instances creation/Network configuration incident notification 2h 33m GRA11
Started Mar 12, 2026, 04:59 PM UTC· resolved Mar 12, 2026, 07:32 PM UTC
- investigating Mar 12, 2026, 04:59 PM UTC
We are currently experiencing an event affecting our offer. Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible. We apologize for any inconvenience caused and appreciate your understanding.
- investigating Mar 12, 2026, 05:02 PM UTC
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary functionality issue in the GRA11 region. Here are some supplementary details : Start time : 12/03/2026 15:00 UTC Impacted Service(s) : Creation of new Public cloud instances is temporarily unavailable. Also, network instabilities are being observed. Customers Impact : Customers are temporarily unable to create new Public Cloud instances and modify network configurations of their existing instances. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Mar 12, 2026, 07:32 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance in GRA11 has been resolved. Start time : 12/03/2026 15:00 UTC End time : 12/03/2026 19:30 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Major March 12, 2026 [GRA][Databases] - MongoDB Discovery incident notification 3d 23h GRA
Started Mar 12, 2026, 09:33 AM UTC· resolved Mar 16, 2026, 09:09 AM UTC
- identified Mar 12, 2026, 09:33 AM UTC
We are currently investigating an incident affecting our MongoDB Discovery offering in the GRA Region. Here are some supplementary details : Start time : 10/03/2026 23:40 UTC Impacted Service(s) : New service creation and management operations are temporarily unavailable. Existing database services continue to run but may be impacted due to degraded self-healing capabilities. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- monitoring Mar 13, 2026, 10:08 AM UTC
MongoDB Discovery offering has been fully restored since 13/03/2026 09:00 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 10/03/2026 23:40 UTC Impacted Service(s) : New service creation and management operations were temporarily unavailable. Existing database services continued to run but might have been impacted due to degraded self-healing capabilities. Root cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Mar 16, 2026, 09:09 AM UTC
We are pleased to inform you that the incident affecting our MongoDB Discovery offering has been resolved. Start time : 10/03/2026 23:40 UTC End time : 13/03/2026 09:00 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Major March 10, 2026 [GRA/DE/SBG/UK/BHS/WAW][Databases] - MongoDB incident notification 3h 16m BHS, DE, GRA, SBG and 2 more
Started Mar 10, 2026, 08:44 PM UTC· resolved Mar 11, 2026, 12:01 AM UTC
- investigating Mar 10, 2026, 08:44 PM UTC
We are currently investigating an incident affecting our MongoDB offering in the DE and GRA Region. Here are some supplementary details : Start time : 10/03/2026 16:40 UTC Impacted Service(s) : Management operations are temporarily unavailable (e.g., adding users, updating flavors). Existing database services remain operational and continue to serve customer workloads. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- identified Mar 10, 2026, 09:31 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our MongoDB offer on the specific GRA - DE - SBG - UK - BHS and WAW regions. Here are some supplementary details : Start time : 10/03/2026 16:40 UTC Impacted Service(s) : Management operations are temporarily unavailable (e.g., adding users, updating flavors). Existing database services remain operational and continue to serve customer workloads. Customers Impact : Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Mar 11, 2026, 12:01 AM UTC
We are pleased to inform you that the incident affecting our MongoDB offering has been resolved. Start time : 10/03/2026 16:40 UTC End time : 10/03/2026 23:40 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Major March 10, 2026 [GRA2][Storage] - CEPH incident notification 54m GRA2
Started Mar 10, 2026, 04:52 PM UTC· resolved Mar 10, 2026, 05:46 PM UTC
- investigating Mar 10, 2026, 04:52 PM UTC
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the GRA2. Here are some supplementary details : Start time : 10/03/2026 07:26 UTC Impacted Service(s) : Some CEPH volumes are not available in this region. Customers Impact : Customers may experience performance degradation and deterioration in their data redundancy. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- identified Mar 10, 2026, 04:57 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Our teams have replaced the faulty network equipment. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Mar 10, 2026, 05:46 PM UTC
We would like to inform you that the incident on our Storage Volume Snapshot (Ceph) offer has now been resolved. Here is detail for this incident : Start time : 10/03/2026 07:26 UTC End time : 10/03/2026 17:33 UTC Root Cause : This incident was caused by a network equipment issue. We thank you for your understanding and patience throughout this incident.
Major March 9, 2026 [GRA11][Network] - API Network incident notification 1h 1m GRA11, GRA11, GRA11
Started Mar 09, 2026, 04:11 PM UTC· resolved Mar 09, 2026, 05:12 PM UTC
No vendor updates were posted for this incident.
Major March 8, 2026 [GRA11][Network] - Network incident notification 12m GRA11
Started Mar 08, 2026, 10:44 PM UTC· resolved Mar 08, 2026, 10:56 PM UTC
No vendor updates were posted for this incident.
Major March 4, 2026 [GLOBAL][AI & Machine Learning] - LLama3.3-70B model incident notification 6d 22h AI & Machine Learning || AI Endpoint
Started Mar 04, 2026, 02:16 PM UTC· resolved Mar 11, 2026, 12:56 PM UTC
- investigating Mar 04, 2026, 02:16 PM UTC
We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary latency issue in the LLama3.3-70B model. Here are some supplementary details : Start time : 04/03/2026 10:00 UTC Impacted Service(s) : LLama3.3-70B model is experiencing performance issues. Customers Impact : Latency and unavailability can be observed on the customer side. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- identified Mar 06, 2026, 09:59 AM UTC
We have new informations regarding the incident that affected your service(s). Please find below an update on the situation: Update : The issue has been identified and is related to an unusually high load on the LLama3.3-70B model. Our teams are monitoring the situation and working to mitigate the impact. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- monitoring Mar 06, 2026, 03:23 PM UTC
Service has been fully restored since 06/03/2026 10:00 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 06/03/2026 15:22 UTC Impacted Service(s) : LLama3.3-70B model is experiencing performance issues. We apologize for any inconvenience caused and appreciate your understanding.
- identified Mar 09, 2026, 10:26 AM UTC
We have new information regarding the incident that affected your service(s). Please find below the latest update on the situation: Update : Latency is still being observed on the LLama3.3-70B model. Our teams are actively monitoring the situation to ensure long-term stability. Ongoing Actions : The root cause of the incident has been identified, and our teams remain fully mobilised to restore normal service as quickly as possible. We will continue to keep you informed about the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Mar 11, 2026, 12:56 PM UTC
We are pleased to inform you that the incident affecting our AI & Machine Learning offer has been resolved. Start time : 04/03/2026 10:00 UTC End time : 11/03/2026 07:00 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.