Public Cloud Outage History
Public Cloud degraded · 1 active incident · 1 long-running issue View live status →Pingoru has recorded 222 incidents for Public Cloud: 221 in the last 12 months and 78 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 28 | 56 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 | 258 of 744 (35%) |
| September 2026 | 21 | 394 of 720 (55%) |
| October 2026 | 30 | 323 of 744 (43%) |
| November 2026 | 11 | 99 of 152 (65%) |
Incidents, newest first
Major November 5, 2026 [GRA6][Storage] - Instance Backup incident notification 1h 41m GRA6
Started Nov 05, 2026, 04:00 PM UTC· resolved Nov 05, 2026, 05:41 PM UTC
- investigating Nov 05, 2026, 04:00 PM UTC
We are currently experiencing an incident affecting our Public Cloud Instance Backup offering, which is causing temporary availability issues in the GRA6 region. Please find the details of this incident below : Start time : 05/11/2026 15:26 UTC Impacted Service(s) : Instance Backup and image management are temporarily unstable in the specified region. Customers Impact : Customers may experience failures when creating backups or managing their images. Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Minor November 5, 2026 [EU-WEST-PAR-B][Storage] - Block Storage incident notification 1d 1h EU-WEST-PAR-B
Started Nov 05, 2026, 03:26 PM UTC· resolved Nov 06, 2026, 04:45 PM UTC
- investigating Nov 05, 2026, 03:26 PM UTC
We are currently experiencing an incident affecting our Block Storage offering, which is causing temporary latency issues in the EU-WEST-PAR-B region. Please find the details of this incident below : Start time : 03/11/2026 04:00 UTC Impacted Service(s) : Some Block Storage volumes in the EU-WEST-PAR-B region are experiencing degraded performance. Customers Impact : Customers may experience increased latency and reduced performance on their volumes located in the specified region. Ongoing Actions : Our teams are actively working to improve the performance of the storage infrastructure. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- identified Nov 06, 2026, 01:02 PM UTC
We are currently experiencing an incident affecting our Block Storage offering in the EU-WEST-PAR-B region. The root cause has been identified. Please find the details of this incident below : Start time : 03/11/2026 04:00 UTC Impacted Service(s) : Some Block Storage volumes in the EU-WEST-PAR-B region are experiencing degraded performance. Customers Impact : Customers may experience increased latency and reduced performance on their volumes located in the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : Our teams are actively working 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 Nov 06, 2026, 04:45 PM UTC
We would like to inform you that the incident affecting our Block Storage offering has now been resolved. Please find the details of this incident below : Start time : 03/11/2026 04:00 UTC End time : 06/11/2026 16:39 UTC Impacted Service(s) : Some Block Storage volumes in the EU-WEST-PAR-B region experienced degraded performance. Customers Impact : Customers may have experienced increased latency and reduced performance on their volumes located in the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.
Minor November 5, 2026 [EU-WEST-PAR-A][Storage] - Block Storage incident notification 21h 47m EU-WEST-PAR-A
Started Nov 05, 2026, 03:09 PM UTC· resolved Nov 06, 2026, 12:57 PM UTC
- investigating Nov 05, 2026, 03:09 PM UTC
We are currently experiencing an incident affecting our Public Cloud Block Storage offering, which is causing temporary latency issues in the EU-WEST-PAR-A region. Please find the details of this incident below : Start time : 04/11/2026 05:00 UTC Impacted Service(s) : Some Block Storage volumes in the EU-WEST-PAR-A region are experiencing performance degradation. Customers Impact : Customers may experience increased latency and reduced performance on their volumes located in the specified region. Ongoing Actions : Our teams are actively working to improve the performance of the storage infrastructure. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Nov 06, 2026, 12:57 PM UTC
We are pleased to inform you that the incident affecting our Storage offering has been resolved. Start time : 04/11/2026 05:00 UTC End time : 06/11/2026 12:40 UTC Root Cause : This incident was caused by a hardware issue. We apologize for any inconvenience caused and appreciate your understanding.
Major November 4, 2026 [DE1][Network] - Load Balancer incident notification 6h 26m DE1
Started Nov 04, 2026, 10:16 AM UTC· resolved Nov 04, 2026, 04:42 PM UTC
- investigating Nov 04, 2026, 10:16 AM UTC
We are currently experiencing an incident affecting our Public Cloud Network offering, which is causing temporary availability issues in the DE1 region. Please find the details of this incident below : Start time : 04/11/2026 05:30 UTC Impacted Service(s) : The Network API in the DE1 region is temporarily unstable. Creation or modification of any Load Balancer can have issues. Customers Impact : Customers may experience API errors when performing network administrative actions, and are temporarily unable to create or resize their Load Balancers. Running services remain unaffected. Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Nov 04, 2026, 04:42 PM UTC
We would like to inform you that the incident affecting our Public Cloud Network offering in the DE1 region has now been resolved. Please find the details of this incident below : Start time : 04/11/2026 05:30 UTC End time : 04/11/2026 16:30 UTC Impacted Service(s) : The Network API in the DE1 region was temporarily unstable. Creation or modification of Load Balancers may have encountered issues. Customers Impact : Customers may have experienced API errors when performing network administrative actions, and were temporarily unable to create or resize their Load Balancers. Running services remained unaffected. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.
Notice November 3, 2026 [DE1][Network] - Load balancer incident notification 1h 20m DE1
Started Nov 03, 2026, 05:58 PM UTC· resolved Nov 03, 2026, 07:19 PM UTC
- identified Nov 03, 2026, 05:58 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Network offer on the specific DE1. Here are some supplementary details : Start time : 03/11/2026 17:00 UTC Impacted Service(s) : The load balancer delivery service in the DE1 region is temporarily unavailable. Customers Impact : Customers are temporarily unable to use and create Loadbalancers in the DE1 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 Nov 03, 2026, 07:19 PM UTC
We would like to inform you that the incident affecting our Network offering has now been resolved. Please find the details of this incident below : Start time : 03/11/2026 17:00 UTC End time : 03/11/2026 19:13 UTC Impacted Service(s) : The Load Balancer delivery service in the DE1 region was temporarily unavailable. Customers Impact : Customers were temporarily unable to use and create Loadbalancers in the DE1 region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.
Minor November 3, 2026 [GRA11][Network] - Network API incident notification 54m GRA11, GRA11, GRA11
Started Nov 03, 2026, 02:53 PM UTC· resolved Nov 03, 2026, 03:48 PM UTC
- investigating Nov 03, 2026, 02:53 PM UTC
We are currently experiencing an incident affecting our Network offering, which is causing temporary availability issues in the GRA11 region. Please find the details of this incident below : Start time : 03/11/2026 09:13 UTC Impacted Service(s) : The Network API for public network and private network (vRack) is temporarily unstable in the specified region. Customers Impact : Customers may experience API errors when creating, modifying or managing their public and private network (vRack) configurations. Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- investigating Nov 03, 2026, 02:58 PM UTC
Please find an update of this incident below : Update : Managed Kubernetes Service in the GRA11 region is also impacted by this incident. Customers may experience API errors when creating, modifying or managing their Kubernetes clusters. Ongoing Actions : 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 Nov 03, 2026, 03:48 PM UTC
We are pleased to inform you that the incident affecting our Network offering has been resolved. Start time : 03/11/2026 09:13 UTC End time : 03/11/2026 15:31 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Minor November 3, 2026 [DE1][Network] - Network API incident notification 2h 52m DE1, DE1, DE1
Started Nov 03, 2026, 10:06 AM UTC· resolved Nov 03, 2026, 12:59 PM UTC
- investigating Nov 03, 2026, 10:06 AM UTC
We are currently experiencing an incident affecting our Network offering, which is causing temporary availability issues in the DE1 region. Please find the details of this incident below : Start time : 03/11/2026 08:10 UTC Impacted Service(s) : The Network API for public network and private network (vRack) is temporarily unstable in the specified region. Customers Impact : Customers may experience API errors when creating, modifying or managing their public and private network (vRack) configurations. Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- investigating Nov 03, 2026, 11:26 AM UTC
Please find an update of this incident below : Update : Managed Kubernetes Service in the DE1 region is also impacted by this incident. Customers may experience API errors when creating, modifying or managing their Kubernetes clusters. Ongoing Actions : 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 Nov 03, 2026, 12:59 PM UTC
We would like to inform you that the incident affecting our Network offering in the DE1 region has now been resolved. Please find the details of this incident below : Start time : 03/11/2026 08:10 UTC End time : 03/11/2026 12:53 UTC Impacted Service(s) : The Network API for public network and private network (vRack) was temporarily unstable in the specified region. Customers Impact : Customers may have experienced API errors when creating, modifying or managing their public and private network (vRack) configurations. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.
Notice November 3, 2026 [GRA][AI & Machine Learning] - AI Notebooks, AI Training, AI Deploy incident notification 50m BHS, BHS, BHS, GRA and 2 more
Started Nov 03, 2026, 07:08 AM UTC· resolved Nov 03, 2026, 07:58 AM UTC
- resolved Nov 03, 2026, 09:23 AM UTC
We would like to inform you that an incident affected our AI & Machine Learning offering. This incident has since been resolved. Please find the details of this incident below : Start time : 31/10/2026 07:08 UTC End time : 31/10/2026 07:58 UTC Impacted Service(s) : AI Notebooks, AI Training and AI Deploy services were temporarily unavailable. Customers Impact : Customers were temporarily unable to create, manage or access their notebooks, training jobs and AI applications. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.
Minor November 2, 2026 [DE1][Network] - Public network incident notification 2h 50m DE1
Started Nov 02, 2026, 03:44 PM UTC· resolved Nov 02, 2026, 06:35 PM UTC
- identified Nov 02, 2026, 03:44 PM UTC
We are currently experiencing an incident affecting our Public Cloud offering in the DE1 region. The root cause has been identified. Please find the details of this incident below : Start time : 02/11/2026 09:22 UTC Impacted Service(s) : Some network administrative tasks may be temporarily slowed down. This does not affect instances. Customers Impact : Customers may experience errors or delays when creating or modifying the network configuration of their instances. Root Cause : This incident is caused by a software issue. Ongoing Actions : Our teams are actively working 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 Nov 02, 2026, 04:24 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Our technical team is actively working on the incident. We currently have an ETA of 02/11/2026 19:00 UTC. We will update this page if we receive any further information before then. 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 Nov 02, 2026, 06:35 PM UTC
We would like to inform you that the incident affecting our Public Cloud offering has now been resolved. Please find the details of this incident below : Start time : 02/11/2026 09:22 UTC End time : 02/11/2026 18:32 UTC Impacted Service(s) : Some network administrative tasks may have been temporarily slowed down. This did not affect instances. Customers Impact : Customers may have experienced errors or delays when creating or modifying the network configuration of their instances. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.
Major November 1, 2026 [SBG5/7][Compute - Instance] - Compute Instance Incident Notification 1h 44m SBG5, SBG7
Started Nov 01, 2026, 05:56 PM UTC· resolved Nov 01, 2026, 07:41 PM UTC
- identified Nov 01, 2026, 05:56 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offering in the specific SBG5 region. Here are some supplementary details : Start time : 01/11/2026 17:55 UTC Impacted Service(s) : Some instances in the SBG5 region are temporarily unreachable. Customers Impact : Some customers are temporarily unable to access instances located in the specified region. Root Cause : A service disruption occurred due to an unexpected 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 Nov 01, 2026, 06:48 PM UTC
We have new information regarding the incident that affects your service(s). Please find below an update on the situation : Update : Some instances in the SBG7 region are temporarily unreachable as well. 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 Nov 01, 2026, 07:41 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 01/11/2026 17:55 UTC End time : 01/11/2026 19:30 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Major October 29, 2026 [RBX][Compute - Instance] - Instances incident notification 20m RBX-A
Started Oct 29, 2026, 03:52 PM UTC· resolved Oct 29, 2026, 04:13 PM UTC
- identified Oct 29, 2026, 03:52 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 RBX region]. Here are some supplementary details : Start time : 29/10/2026 15:43 UTC Impacted Service(s) : Some instances in the RBX region are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on 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 Oct 29, 2026, 04:13 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 29/10/2026 15:43 UTC End time : 29/10/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.
Minor October 29, 2026 [EU-WEST-PAR][Containers & Orchestration] - MKS cluster incident notification 3h 52m EU-WEST-PAR
Started Oct 29, 2026, 03:36 PM UTC· resolved Oct 29, 2026, 07:28 PM UTC
- identified Oct 29, 2026, 03:36 PM UTC
We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary functionality issue in the EU-WEST-PAR region. Here are some supplementary details : Start time : 29/10/2026 10:00 UTC Impacted Service(s) : New MKS cluster delivery is currently unavailable on the specific region. Customers Impact : Customers are currently unable to create new MKS clusters. 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 Oct 29, 2026, 07:28 PM UTC
We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved. Start time : 29/10/2026 10:00 UTC End time : 29/10/2026 16:18 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Minor October 29, 2026 [EU][Network] - vRack issue incident notification 2h 22m DE1, GRA1, GRA3, GRA5 and 11 more
Started Oct 29, 2026, 10:02 AM UTC· resolved Oct 29, 2026, 12:24 PM UTC
- investigating Oct 29, 2026, 10:02 AM UTC
We are currently experiencing an event affecting our Network offer. Start time : 29/10/2026 10:00 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.
- identified Oct 29, 2026, 10:53 AM UTC
We are currently investigating an incident affecting our Network offering, which is causing temporary latency issue in the EU region. Here are some supplementary details : Start time : 29/10/2026 05:15 UTC Impacted Service(s) : vRack issue on EU region Customers Impact : Customers may experienced some issue to create instance with vRack port, management tasks carried out via vRack may be affected. 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 Oct 29, 2026, 12:24 PM UTC
We are pleased to inform you that the incident affecting our Network offering has been resolved. All vRack tasks are running correctly. Start time : 29/10/2026 05:15 UTC End time : 29/10/2026 12:20 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 October 27, 2026 [RBX8][Compute - Instance] - Instance incident notification 6h 20m RBX-A
Started Oct 27, 2026, 08:44 AM UTC· resolved Oct 27, 2026, 03:05 PM UTC
- identified Oct 27, 2026, 08:44 AM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific RBX8 Region. Here are some supplementary details : Start time : 27/10/2026 07:49 UTC Impacted Service(s) : Some instances in the RBX8 region are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified region. Root Cause : This incident is caused by this maintenance : https://network.status-ovhcloud.com/incidents/f629kcrn2cvg 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 Oct 27, 2026, 11:23 AM UTC
We have new information regarding this incident that affected your service(s). Please find below an update on the situation: Update : The fix has been implemented. Some instances are operational again, and the remaining instances will be operational soon. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Oct 27, 2026, 03:05 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering in the RBX8 region has been resolved. Start time : 27/10/2026 07:49 UTC End time : 27/10/2026 14:18 UTC Root Cause : This incident was caused by this maintenance : https://network.status-ovhcloud.com/incidents/f629kcrn2cvg We apologize for any inconvenience caused and appreciate your understanding.
Minor October 27, 2026 [EU-WEST-PAR-A][Storage] - Volume Ceph incident notification 1d 3h EU-WEST-PAR-A
Started Oct 27, 2026, 07:30 AM UTC· resolved Oct 28, 2026, 10:44 AM UTC
- investigating Oct 27, 2026, 07:30 AM UTC
We are currently investigating an incident affecting our Storage offering, which is causing temporary latency issue in our Public Cloud Volume (Ceph) offering in the EU-WEST-PAR-A zone. Here are some supplementary details : Start time : 27/10/2026 00:00 UTC Impacted Service(s) : Some Volumes experience degraded performance in the specified zone. Customers Impact : Customers may have latencies and degradation on their Volumes. Ongoing Actions : Customers may experience high latency on their volumes. Volumes remained available throughout We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- identified Oct 27, 2026, 01:32 PM UTC
We are currently experiencing an incident affecting our Public Cloud Volume (Ceph) offering in the EU-WEST-PAR-A zone. The root cause has been identified. Please find the details of this incident below : Start time : 27/10/2026 00:00 UTC Impacted Service(s) : Some volumes are experiencing degraded performance in the specified zone. Customers Impact : Customers may experience high latency on their volumes. Volumes remain available. Root Cause : This incident is caused by a software issue. Ongoing Actions : Our teams are actively working 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 Oct 27, 2026, 04:22 PM UTC
We would like to inform you that our service has been fully restored as of 27/10/2026 16:16 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : Start time : 27/10/2026 00:00 UTC Impacted Service(s) : Some volumes experienced degraded performance in the EU-WEST-PAR-A zone. Customers Impact : Customers may have experienced high latency on their volumes. Volumes remained available throughout the incident. Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Oct 28, 2026, 10:44 AM UTC
We are pleased to inform you that the incident affecting our Public Cloud Volume (Ceph) offering has been resolved. Start time : 27/10/2026 00:00 UTC End time : 27/10/2026 16:30 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Notice October 26, 2026 [EU-WEST-PAR-A][Storage] - Volume Ceph incident notification – EU-WEST-PAR-A
Started Oct 26, 2026, 01:07 PM UTC· resolved Oct 26, 2026, 01:07 PM UTC
- resolved Oct 26, 2026, 01:07 PM UTC
We would like to inform you that an incident affected our Public Cloud Volume (Ceph) offering in the EU-WEST-PAR-A zone. This incident has since been resolved. Please find the details of this incident below : Start time : 25/10/2026 00:00 UTC End time : 26/10/2026 00:00 UTC Impacted Service(s) : Some Volumes experienced degraded performance in the specified zone. Customers Impact : Customers may have experienced high latency on their volumes. Volumes remained available throughout the incident. We thank you for your understanding and patience throughout this incident.
Major October 24, 2026 [GRA][Public Cloud] - Instance incident notification 12h 19m GRA1
Started Oct 24, 2026, 03:30 PM UTC· resolved Oct 25, 2026, 03:49 AM UTC
- investigating Oct 24, 2026, 03:30 PM UTC
We are currently experiencing an incident affecting our Public Cloud offering in the GRA region. Please find the details of this incident below : Start time : 24/10/2026 14:54 UTC Impacted Service(s) : Some instances in the GRA region are unavailable. Customers Impact : Customers are temporarily unable to access their instances located on the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : Our teams are actively working 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 Oct 24, 2026, 03:32 PM UTC
The issue has been identified and a fix is being implemented.
- identified Oct 24, 2026, 05:43 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Most of the services are now 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 Oct 25, 2026, 03:49 AM UTC
We are pleased to inform you that the incident affecting our Public Cloud offering has been resolved. Start time : 24/10/2026 14:54 UTC End time : 25/09/2026 00: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.
Minor October 21, 2026 [GRA1][Storage] - Block Storage incident notification 2h 49m GRA1
Started Oct 21, 2026, 10:37 AM UTC· resolved Oct 21, 2026, 01:26 PM UTC
- identified Oct 21, 2026, 10:37 AM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Storage offer on the specific GRA1 region. Here are some supplementary details : Start time : 21/10/2026 09:30 UTC Impacted Service(s) : The Block Storage service in the GRA1 region is temporarily experiencing degraded performance. Customers Impact : Customers may temporarily experience degraded performance on their Block Storage services. 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 Oct 21, 2026, 12:16 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Our technical team is still working to resolve the incident, which should be resolved shortly. 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 Oct 21, 2026, 01:26 PM UTC
We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 21/10/2026 09:30 UTC End time : 21/10/2026 13: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.
Minor October 21, 2026 [GLOBAL][AI & Machine Learning] - AI Endpoint Incident Notification 4h 39m AI & Machine Learning || AI Endpoint
Started Oct 21, 2026, 07:27 AM UTC· resolved Oct 21, 2026, 12:07 PM UTC
- investigating Oct 21, 2026, 07:27 AM UTC
We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary availability issue on AI Endpoint . Here are some supplementary details : Start time : 21/10/2026 07:00 UTC Impacted Service(s) : AI Endpoints may have some performance issue. Customers Impact : Customers may temporarily experience slowness when using the AI endpoints. 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.
- monitoring Oct 21, 2026, 08:07 AM UTC
Service has been fully restored since 21/10/2026 08:04 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 21/10/2026 07:00 UTC Impacted Service(s) : AI Endpoints may have had some performance issues. Customers Impact : Customers may have temporarily experienced slowness when using the AI endpoints. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Oct 21, 2026, 12:07 PM UTC
We are pleased to inform you that the incident affecting our AI & Machine Learning offering has been resolved. Start time : 21/10/2026 07:00 UTC End time : 21/10/2026 08:04 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 October 20, 2026 [RBX-A][Public Cloud] Block Storage incident notification 1h 44m RBX-A
Started Oct 20, 2026, 09:20 AM UTC· resolved Oct 20, 2026, 11:05 AM UTC
- identified Oct 20, 2026, 09:20 AM UTC
We are currently experiencing an incident affecting our Block Storage offering in the RBX-A region. Please find the details of this incident below : Start time : 20/10/2026 08:48 UTC Impacted Service(s) : Block Storage volumes hosted on the RBX-A were unavailable between 08:48 and 09:00 UTC and are currently experiencing reduced performance. Customers Impact : Customers were temporarily unable to access their Block Storage volumes between 08:48 and 09:00 UTC. Since 09:00 UTC, customers may experience degraded performance on their volumes while the cluster is recovering. Root Cause : This incident is caused by a hardware issue. Ongoing Actions : Our teams are actively working to restore full performance 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 Oct 20, 2026, 11:05 AM UTC
We would like to inform you that the incident affecting our Public Cloud offering has now been resolved. Please find the details of this incident below : Start time : 20/10/2026 08:48 UTC End time : 20/10/2026 10:26 UTC Impacted Service(s) : Block Storage volumes hosted on the PCI-RBX-A-volumes_2 cluster in the RBX-A region were unavailable between 08:48 and 09:00 UTC, followed by reduced performance until 10:26 UTC. Customers Impact : Customers were temporarily unable to access their Block Storage volumes between 08:48 and 09:00 UTC, and may have experienced degraded performance on their volumes until 10:26 UTC while the cluster was recovering. Root Cause : This incident was caused by a hardware issue. We thank you for your understanding and patience throughout this incident.
Minor October 17, 2026 [GLOBAL][Cloud Databases] - MYSQL Database incident notification 10h 5m BHS, DE, GRA, EU-SOUTH-MIL and 9 more
Started Oct 17, 2026, 08:48 AM UTC· resolved Oct 17, 2026, 06:54 PM UTC
- investigating Oct 17, 2026, 08:48 AM UTC
We are currently investigating an incident affecting our Cloud Databases offering, which is causing temporary latency issue in the Global Region. Here are some supplementary details : Start time : 16/10/2026 22:16 UTC Impacted Service(s) : New MySQL services are taking longer than usual to become available. Existing services are not affected. Customers Impact : Customers are temporarily unable to access the new MySQL services. 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 Oct 17, 2026, 06:54 PM UTC
We are pleased to inform you that the incident affecting our Cloud Databases offering has been resolved. Start time : 16/10/2026 22:16 UTC End time : 17/10/2026 11:30 UTC Root Cause : This incident was caused by our provider. We apologize for any inconvenience caused and appreciate your understanding.
Minor October 16, 2026 [GRA11][Public Cloud] - Network API incident notification 1d 3h GRA11, GRA11, GRA11, GRA11 and 1 more
Started Oct 16, 2026, 04:13 PM UTC· resolved Oct 17, 2026, 08:06 PM UTC
- investigating Oct 16, 2026, 04:13 PM UTC
We are currently experiencing an incident affecting our Public Cloud offering, which is causing temporary latency issues in the GRA11 region. Please find the details of this incident below : Start time : 16/10/2026 12:30 UTC Impacted Service(s) : The Public Cloud Network API in the GRA11 region is currently experiencing slowness, affecting operations on Floating IP, Gateway, Load Balancer, Private network (vRack) and Public network. Existing network configurations continue to operate normally. Customers Impact : Customers may experience latency and slowness, or encounter errors, when modifying network configurations or creating new resources. Existing resources and running instances remain unaffected. Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- monitoring Oct 16, 2026, 04:27 PM UTC
We would like to inform you that our service has been fully restored as of 16/10/2026 at 15:30 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : Start time : 16/10/2026 12:30 UTC Impacted Service(s) : The Public Cloud Network API in the GRA11 region experienced slowness, affecting operations on Floating IP, Gateway, Load Balancer, Private network (vRack) and Public network. Existing network configurations continued to operate normally. Customers Impact : Customers may have experienced latency and slowness, or encountered errors, when modifying network configurations or creating new resources. Existing resources and running instances remained unaffected. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Oct 17, 2026, 08:06 PM UTC
We are pleased to inform you that the incident affecting our Public Cloud Network API in the GRA11 region has been resolved. Start time : 16/10/2026 12:30 UTC End time : 16/10/2026 15:30 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 October 15, 2026 [AP-SOUTH-MUM-1][Storage] - S3 Object Storage incident notification 19h 56m AP-SOUTH-MUM-1
Started Oct 15, 2026, 12:24 PM UTC· resolved Oct 16, 2026, 08:21 AM UTC
- monitoring Oct 15, 2026, 12:24 PM UTC
Service has been fully restored since 15/10/2026 11:35 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 15/10/2026 11:30 UTC Impacted Service(s) : Disconnection and 503 errors observed on S3 Object Storage. Customers Impact : Customers were temporarily facing disconnection and 503 errors when trying to access and use their objects located in AP-SOUTH-MUM-1. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/h9zynmg40bbz We apologize for any inconvenience caused and appreciate your understanding.
- identified Oct 15, 2026, 03:28 PM UTC
We are currently experiencing an incident affecting our Object Storage offering in the AP-SOUTH-MUM-1 region. The root cause has been identified. Please find the details of this incident below : Start time : 15/10/2026 11:30 UTC Impacted Service(s) : S3 Object Storage is experiencing disconnections and 503 errors in the AP-SOUTH-MUM-1 region. Customers Impact : Customers may experience disconnections and 503 errors when accessing, uploading or retrieving their objects stored in the specified region. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/h9zynmg40bbz Ongoing Actions : Our teams are actively working 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 Oct 16, 2026, 08:21 AM UTC
We are pleased to inform you that the incident affecting our Object Storage offering in AP-SOUTH-MUM-1 region has been resolved. Start time : 15/10/2026 11:30 UTC End time : 15/10/2026 15:05 UTC Root Cause : This incident was caused by another incident : https://network.status-ovhcloud.com/incidents/h9zynmg40bbz We apologize for any inconvenience caused and appreciate your understanding.
Notice October 15, 2026 [AP-SOUTH-MUM-1][Storage] - S3 Object Storage incident notification 1h 8m AP-SOUTH-MUM-1
Started Oct 15, 2026, 06:40 AM UTC· resolved Oct 15, 2026, 07:49 AM UTC
- monitoring Oct 15, 2026, 06:40 AM UTC
Service has been fully restored since 15/10/2026 06:10 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 15/10/2026 06:02 UTC Impacted Service(s) : Disconnection and 503 errors observed on S3 Object Storage. Customers Impact : Customers were temporarily facing disconnection and 503 errors when trying to access and use their objects located in AP-SOUTH-MUM-1. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/qss8stslpv68 We apologize for any inconvenience caused and appreciate your understanding.
- resolved Oct 15, 2026, 07:49 AM UTC
We are pleased to inform you that the incident affecting our S3 Object Storage offering in AP-SOUTH-MUM-1 region has been resolved. Start time : 15/10/2026 06:02 UTC End time : 15/10/2026 06:10 UTC Root Cause : This incident was caused by another incident : https://network.status-ovhcloud.com/incidents/qss8stslpv68 We apologize for any inconvenience caused and appreciate your understanding.
Major October 14, 2026 [GRA9/GRA11][Public Cloud] - Network API incident notification 37m GRA9, GRA9, GRA11, GRA11
Started Oct 14, 2026, 02:46 PM UTC· resolved Oct 14, 2026, 03:24 PM UTC
- investigating Oct 14, 2026, 02:46 PM UTC
We are currently experiencing an incident affecting our Public Cloud offering, which is causing temporary latency issues in the GRA9 and GRA11 regions. Please find the details of this incident below : Start time : 14/10/2026 08:00 UTC Impacted Service(s) : The OpenStack Network API in the GRA9 and GRA11 regions is experiencing increased latency. Customers Impact : Customers may experience slowness when performing network operations through the API or Horizon, such as creating or modifying networks, ports, floating IPs or security groups. Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Oct 14, 2026, 03:24 PM UTC
We are pleased to inform you that the incident affecting our Public Cloud offering has been resolved. Start time : 14/10/2026 08:00 UTC End time : 14/10/2026 15:22 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.