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 590 (51%) |
Incidents, newest first
Notice August 15, 2026 [GRA3][Storage] - Block storage incident notification – GRA3
Started Aug 15, 2026, 02:36 PM UTC· resolved Aug 15, 2026, 02:36 PM UTC
- resolved Aug 15, 2026, 02:36 PM UTC
We had an incident on Storage offer which has now been resolved. Here are some supplementary details : Start time : 15/08/2026 13:25 UTC End time : 15/08/2026 14:10 UTC Impacted Service(s) : The Block Storage service is experiencing latency for some customers in the GRA3 region. Customers Impact : Customers may have temporarily experienced latency affecting their Block Storage services in the GRA3 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.
Major August 14, 2026 [GRA11][Storage] - File storage incident notification 13h 36m GRA11
Started Aug 14, 2026, 04:07 PM UTC· resolved Aug 15, 2026, 05:44 AM UTC
- identified Aug 14, 2026, 04:07 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Storage offer on the specific GRA11 region. Here are some supplementary details : Start time : 14/08/2026 14:43 UTC Impacted Service(s) : Some File storage are temporarily unavailable. Customers Impact : Some customers are temporarily unable to access their File storage. Root Cause : A service disruption occurred due to an unexpected infrastructure failure. 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 Aug 15, 2026, 05:44 AM UTC
We are pleased to inform you that the incident affecting our File storage offering has been resolved. Start time : 14/08/2026 14:43 UTC End time : 15/08/2026 05:25 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.
Major August 14, 2026 [GRA5/GRA9/GRA11][Compute - Instance] - Some instances incident notification 14h 16m GRA5, GRA9, GRA11
Started Aug 14, 2026, 03:26 PM UTC· resolved Aug 15, 2026, 05:43 AM UTC
- identified Aug 14, 2026, 03:26 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 GRA9/GRA11. Here are some supplementary details : Start time : 14/08/2026 14:43 UTC Impacted Service(s) : Some instances in the GRA9/GRA11 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure 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 Aug 14, 2026, 03: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 GRA5/GRA9/GRA11. Here are some supplementary details : Start time : 14/08/2026 14:43 UTC Impacted Service(s) : Some instances in the GRA5/GRA9/GRA11 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure 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 Aug 15, 2026, 05:43 AM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 14/08/2026 14:43 UTC End time : 15/08/2026 05:25 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.
Notice August 13, 2026 [EU-WEST-PAR][Storage] - Object storage incident notification 3h 49m EU-WEST-PAR-A, EU-WEST-PAR-B, EU-WEST-PAR-C
Started Aug 13, 2026, 10:53 AM UTC· resolved Aug 13, 2026, 02:42 PM UTC
- monitoring Aug 13, 2026, 10:53 AM UTC
We experienced an incident that has now been resolved. Service has been fully restored as of 13/08/2026 10:16 UTC. Monitoring remains active to ensure continued stability. Here are some supplementary details : Start time : 13/08/2026 09:15 UTC Impacted Service(s) : The object storage service temporarily encountered 503 errors. Customers Impact : Some customers may have temporarily encountered 503 errors with their Object Storage services in the EU-WEST-PAR region. Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Aug 13, 2026, 02:42 PM UTC
We are pleased to inform you that the incident affecting our Object Storage offering has been resolved. Start time : 13/08/2026 09:15 UTC End time : 13/08/2026 10:16 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.
Minor August 11, 2026 [GRA11][Public Cloud] - Barbican incident notification 19h 49m GRA11, GRA11
Started Aug 11, 2026, 12:18 PM UTC· resolved Aug 12, 2026, 08:08 AM UTC
- investigating Aug 11, 2026, 12:18 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Load Balancer offer in the specific GRA11 region. Here are some supplementary details : Start time : 07/08/2026 09:41 UTC Impacted Service(s) : There may be difficulties when creating Public Cloud instances on GRA11. Load balancer Octavia can also face issue. Customers Impact : Customers may experience difficulties when creating a load balancer or renewing a certificate. when creating a load balancer, renewing a certificate, or creating new encrypted volumes 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.
- investigating Aug 11, 2026, 12:25 PM UTC
We are continuing to investigate this issue.
- resolved Aug 12, 2026, 08:08 AM UTC
We are pleased to inform you that the incident affecting our Load Balancer offer has been resolved. Start time : 07/08/2026 09:41 UTC End time : 11/08/2026 11:11 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 August 10, 2026 [EU/APAC][Storage] - Encrypted Volume Incident notification 21h 11m AP-SOUTHEAST-SYD-2, AP-SOUTH-MUM-1, DE1, EU-SOUTH-MIL-A and 18 more
Started Aug 10, 2026, 03:16 PM UTC· resolved Aug 11, 2026, 12:27 PM UTC
- investigating Aug 10, 2026, 03:16 PM UTC
We are currently investigating an incident affecting our Storage offering, which is causing temporary issue in the EU and APAC Region. Here are some supplementary details : Start time : 07/08/2026 09:41 UTC Impacted Service(s) : Creation of encrypted volumes is degraded. Customers Impact : Some customers may experience difficulties when creating encrypted volumes 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.
Minor August 7, 2026 [BHS][Compute - Instance] - Compute Instance Incident Notification 3h 19m BHS1
Started Aug 07, 2026, 03:26 PM UTC· resolved Aug 07, 2026, 06:45 PM UTC
- investigating Aug 07, 2026, 03:26 PM UTC
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in BHS region. Here are some supplementary details : Start time : 07/08/2026 14:44 UTC Impacted Service(s) : Some instances in the BHS region are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified 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 Aug 07, 2026, 06:45 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 07/08/2026 14:14 UTC End time : 07/08/2026 15:57 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Minor August 5, 2026 [BHS5][Storage] - Ceph volumes incident notification 19h 36m BHS5
Started Aug 05, 2026, 05:32 PM UTC· resolved Aug 06, 2026, 01:08 PM UTC
- identified Aug 05, 2026, 05:32 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Storage offer on the specific BHS5 region. Here are some supplementary details : Start time : 05/08/2026 17:00 UTC Impacted Service(s) : Some Ceph volumes are experiencing temporary performance degradation in this region. Customers Impact : Customers may experience performance degradation and reduced data redundancy. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.
- identified Aug 06, 2026, 12:15 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 to solve the incident. 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 Aug 06, 2026, 01:08 PM UTC
We are pleased to inform you that the incident affecting our Storage offering has been resolved. Start time : 05/08/2026 17:00 UTC End time : 06/08/2026 13: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 August 5, 2026 [DE1][Storage] - Some CEPH volumes incident notification – DE1
Started Aug 05, 2026, 03:33 PM UTC· resolved Aug 05, 2026, 03:33 PM UTC
- resolved Aug 05, 2026, 03:33 PM UTC
We had an incident on Storage offer which has now been resolved. Here are some supplementary details : Start time : 05/08/2026 11:46 UTC End time : 05/08/2026 13:35 UTC Impacted Service(s) : Some CEPH volumes were not available in this region Customers Impact : Customers might have experienced performance degradation and deterioration in their data redundancy Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.
Major August 5, 2026 [AP-SOUTH-MUM-1][Compute - Instance] - Compute - API instances incident notification 2h 29m AP-SOUTH-MUM-1
Started Aug 05, 2026, 03:11 PM UTC· resolved Aug 05, 2026, 05:41 PM UTC
- identified Aug 05, 2026, 03:11 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 AP-SOUTH-MUM-1 region. Here are some supplementary details : Start time : 05/08/2026 14:18 UTC Impacted Service(s) : Some instances or API services may temporarily experience network disruptions. Customers Impact : Some customers may temporarily experience network disruptions on their instances or API services Root Cause : A service disruption occurred due to an unexpected infrastructure failure 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 Aug 05, 2026, 05:41 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 05/08/2026 14:18 UTC End time : 05/08/2026 15:14 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.
Major August 3, 2026 [GLOBAL][Data & Analytics] - Data Platform Incident Notification 1h 18m Data & Analytics || Data Platform
Started Aug 03, 2026, 02:14 PM UTC· resolved Aug 03, 2026, 03:33 PM UTC
- investigating Aug 03, 2026, 02:14 PM UTC
We are currently experiencing an event affecting our Data & Analytics offer. Start time : 03/08/2026 13:47 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 Aug 03, 2026, 02:50 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on the specific GLOBAL region. Here are some supplementary details : Start time : 03/08/2026 13:47 UTC Impacted Service(s) : DPE jobs and query execution are experiencing degraded performance, resulting in delays and possible failures. Customers Impact : Customers may experience delays and intermittent failures when running DPE jobs and processing queries. Root Cause : This incident is caused by a software issue. 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 Aug 03, 2026, 03:33 PM UTC
We are pleased to inform you that the incident affecting our Data & Analytics offering has been resolved. Start time : 03/08/2026 13:47 UTC End time : 03/08/2026 14:00 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Notice July 29, 2026 [GRA][Storage] - Object Storage incident notification – GRA
Started Jul 29, 2026, 01:06 PM UTC· resolved Jul 29, 2026, 01:06 PM UTC
- resolved Jul 29, 2026, 01:06 PM UTC
We had an incident on our Object Storage offer in GRA region which has now been resolved. Here are some supplementary details : Start time : 29/07/2026 06:00 UTC End time : 29/07/2026 11:00 UTC Impacted Service(s) : Slowness and 504 error were observed for object storage located in GRA. Customers Impact : Customers were temporarily facing slowness and 504 error when trying to access and use their objects 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.
Major July 28, 2026 [WAW1][Compute - Instance] - Some instances incident notification 8m WAW1
Started Jul 28, 2026, 05:12 PM UTC· resolved Jul 28, 2026, 05:21 PM UTC
- identified Jul 28, 2026, 05:12 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 WAW1 region. Here are some supplementary details : Start time : 28/07/2026 17:06 UTC Impacted Service(s) : Some instances in the WAW1 region are 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 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 Jul 28, 2026, 05:21 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 28/07/2026 17:06 UTC End time : 28/07/2026 17:12 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 July 27, 2026 [GRA11][Network] - Load Balancer incident notification 1d 2h GRA11, GRA11
Started Jul 27, 2026, 12:52 PM UTC· resolved Jul 28, 2026, 03:15 PM UTC
- identified Jul 27, 2026, 12:52 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer in the specific GRA11 region. Here are some supplementary details : Start time : 27/07/2026 07:41 UTC Impacted Service(s) : Creation of Public Cloud instances on GRA11 LoadBalancer is temporarily unavailable. Customers Impact : Customers are temporarily unable to create new Public Cloud instances on LoadBalancer. 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 Jul 28, 2026, 11:25 AM 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 currently working on a fix to resolve the issue. 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 Jul 28, 2026, 12:13 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The majority of customers are no longer impacted by the incident. 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 Jul 28, 2026, 03:15 PM UTC
We are pleased to inform you that the incident affecting our Load Balancer offering has been resolved. Start time : 27/07/2026 07:41 UTC End time : 28/07/2026 14:45 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Major July 27, 2026 [UK1][Compute - Instance] - Some instances incident notification 2h 5m UK1
Started Jul 27, 2026, 06:33 AM UTC· resolved Jul 27, 2026, 08:39 AM UTC
- identified Jul 27, 2026, 06:33 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 UK1 region. Here are some supplementary details : Start time : 27/07/2026 06:19 UTC Impacted Service(s) : Some instances in the UK1 region are 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 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 Jul 27, 2026, 08:39 AM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering in UK1 region has been resolved. Start time : 27/07/2026 06:19 UTC End time : 27/07/2026 07: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 July 23, 2026 [EU-WEST-PAR][Storage] - Object storage S3 Standard Incident Notification 17h 43m EU-WEST-PAR-A, EU-WEST-PAR-B, EU-WEST-PAR-C
Started Jul 23, 2026, 07:14 PM UTC· resolved Jul 24, 2026, 12:58 PM UTC
- investigating Jul 23, 2026, 07:14 PM UTC
We are currently investigating an incident affecting our Storage offering, which is causing temporary issue in the EU-WEST-PAR region. Here are some supplementary details : Start time : 23/07/2026 18:00 UTC Impacted Service(s) : Intermittent HTTP 503 errors may affect object upload and download operations. Customers Impact : Customers may experience issues downloading or uploading their objects due to 503 errors. 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 Jul 23, 2026, 11:30 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The services s are operational again since 23/07/2026 23:15 UTC. Ongoing Actions : Our team will monitor the situation. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Jul 24, 2026, 12:58 PM UTC
We are pleased to inform you that the incident affecting our Storage offering has been resolved. Start time : 23/07/2026 18:00 UTC End time : 23/07/2026 23: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 July 23, 2026 [GRA1/3/9/11][Compute - Instance] - Some Instances Incident Notification 29m GRA1, GRA3, GRA9, GRA11
Started Jul 23, 2026, 06:05 PM UTC· resolved Jul 23, 2026, 06:34 PM UTC
- identified Jul 23, 2026, 06:05 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 GRA1/3/9/11 regions. Here are some supplementary details : Start time : 23/07/2026 17:52 UTC Impacted Service(s) : Some instances in the GRA1/3/9/11 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. 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 Jul 23, 2026, 06:34 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 23/07/2026 17:52 UTC End time : 23/07/2026 17:58 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 July 20, 2026 [GLOBAL][Databases] - Database incident notification 1d 2h BHS, BHS, BHS, DE and 35 more
Started Jul 20, 2026, 07:48 AM UTC· resolved Jul 21, 2026, 10:19 AM UTC
- identified Jul 20, 2026, 07:48 AM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Databases offer on the specific GRA11 Region. Here are some supplementary details : Start time : 19/07/2026 18:00 UTC Impacted Service(s) : Some Database are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their Database located on the specified region. Root Cause : This incident is caused by a hardware issue. 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 Jul 20, 2026, 04:33 PM UTC
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Databases are temporarily unavailable in GLOBAL region. 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 Jul 20, 2026, 08:35 PM UTC
Please find an update of this incident below : Update: Database access is being progressively restored in all regions, with the exception of GRA11. Pending orders are now being progressively delivered. As a precaution, new orders remain temporarily suspended. Ongoing Actions : Our teams continue to restore the remaining impacted region and are closely monitoring the situation. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- monitoring Jul 20, 2026, 10:15 PM UTC
Update: Database access has been restored across all regions. Our teams are continuing to work on the remaining impacted databases in GRA11. Pending orders are being delivered, and new orders are no longer suspended. Monitoring remains in place to ensure long-term stability. We apologize for any inconvenience caused and appreciate your understanding and patience.
- resolved Jul 21, 2026, 10:19 AM UTC
We are pleased to inform you that the incident affecting our Databases offering has been resolved. Start time : 19/07/2026 18:00 UTC End time : 21/07/2026 08: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 July 19, 2026 [GRA11][Compute - Instance] - Instance creation incident notification 1h 26m GRA11
Started Jul 19, 2026, 05:50 PM UTC· resolved Jul 19, 2026, 07:16 PM UTC
- identified Jul 19, 2026, 05:50 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 GRA11. Here are some supplementary details : Start time : 19/07/2026 16:50 UTC Impacted Service(s) : Creation of Public Cloud instances in GRA11 region is temporarily unavailable. Customers Impact : Customers are temporarily unable to create new Public Cloud instances. Instances created during the incident will remain stuck in a "building"/"spawning" state and will not become operational. Once the incident is resolved, customers are advised to delete these instances and create new ones. Root Cause : This incident is caused by our provider. 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 Jul 19, 2026, 07:16 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering in GRA11 has been resolved. Start time : 19/07/2026 16:50 UTC End time : 19/07/2026 19:14 UTC Root Cause : This incident was caused by our provider. We apologize for any inconvenience caused and appreciate your understanding.
Major July 19, 2026 [GRA][AI & Machine Learning] - AI Deploy/Training/Notebooks incident notification 4m GRA, GRA, AI & Machine Learning || AI Endpoint
Started Jul 19, 2026, 02:27 PM UTC· resolved Jul 19, 2026, 02:31 PM UTC
- investigating Jul 19, 2026, 02:27 PM UTC
We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary issue in the GRA region. Here are some supplementary details : Start time : 19/07/2026 12:40 UTC Impacted Service(s) : AI Deploy, AI Training and AI Notebooks are temporarily unavailable. Customers Impact : Customers are temporarily unable to access and use models in the specified offers. 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 Jul 19, 2026, 02:31 PM UTC
We are pleased to inform you that the incident affecting our AI & Machine Learning offering on AI Deploy, AI Training and AI Notebooks has been resolved. Start time : 19/07/2026 12:40 UTC End time : 19/07/2026 14:30 UTC Root Cause : This incident was caused by our provider. We apologize for any inconvenience caused and appreciate your understanding.
Major July 16, 2026 [BHS/GRA][Identity, Security & Operations] - Logs Data Platform incident notification 58m BHS, GRA
Started Jul 16, 2026, 12:03 PM UTC· resolved Jul 16, 2026, 01:02 PM UTC
- investigating Jul 16, 2026, 12:03 PM UTC
We are currently experiencing an incident affecting our Logs Data Platform service, which is causing temporary availability issues. Please find the details of this incident below : Start time : 15/07/2026 18:00 UTC Impacted Service(s) : The WebSocket connection on Logs Data Platform is temporarily unavailable. Customers Impact : Customers are temporarily unable to use the Logs Data Platform WebSocket connection. 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 Jul 16, 2026, 01:02 PM UTC
We are pleased to inform you that the incident affecting our Logs Data Platform service has been resolved. Start time : 15/07/2026 18:00 UTC End time : 16/07/2026 13:00 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Minor July 14, 2026 [WAW][Object Storage] - Object Storage Swift Incident Notification 1h 32m WAW
Started Jul 14, 2026, 08:08 AM UTC· resolved Jul 14, 2026, 09:40 AM UTC
- investigating Jul 14, 2026, 08:08 AM UTC
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the region WAW. Here are some supplementary details : Start time : 14/07/2026 07:49 UTC Impacted Service(s) : Object Storage S3. Customers Impact : Customers may experience connection problems while trying to access Object Storage S3 in WAW. 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 Jul 14, 2026, 08:38 AM UTC
We have determined the origin of the issue affecting our Object Storage Swift offer in WAW. Here are some supplementary details : Start time : 14/07/2026 07:59 UTC Impacted Service(s) : Object Storage Swift is temporarily unavailable. Customers Impact : Customers may experience connection problems while trying to access Object Storage Swift in WAW. 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 Jul 14, 2026, 09:40 AM UTC
We are pleased to inform you that the incident affecting our Object Storage Swift offering has been resolved. Start time : 14/07/2026 07:49 UTC End time : 14/07/2026 08: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 July 13, 2026 [BHS1/BHS5][Compute - Instance] - Some Instances Incident Notification 7h 59m BHS1, BHS5
Started Jul 13, 2026, 05:22 PM UTC· resolved Jul 14, 2026, 01:21 AM UTC
- identified Jul 13, 2026, 05:22 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 BHS1/BHS5 regions. Here are some supplementary details : Start time : 13/07/2026 19:34 UTC Impacted Service(s) : Some instances in the BHS1/BHS5 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. 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 Jul 13, 2026, 05:33 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 BHS1/BHS5 regions. Here are some supplementary details : Start time : 13/07/2026 19:34 UTC Impacted Service(s) : Some instances in the BHS1/BHS5 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. 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 Jul 14, 2026, 01:21 AM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 13/07/2026 16:55 UTC End time : 13/07/2026 22:55 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 July 10, 2026 [EU-WEST-PAR][Containers & Orchestration] - Managed Private Registry incident notification 2h 47m EU-WEST-PAR
Started Jul 10, 2026, 09:30 PM UTC· resolved Jul 11, 2026, 12:18 AM UTC
- identified Jul 10, 2026, 09:30 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Managed Private Registry service on the EU-WEST-PAR region. Here are some supplementary details : Start time : 10/07/2026 20:20 UTC Impacted Service(s) : Registries are temporarily unavailable. Customers Impact : Customers are temporarily facing issues when trying to use connect to Harbor UI, pull or push new images. Root Cause : This incident is caused by a hardware issue. 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 Jul 11, 2026, 12:18 AM UTC
We are pleased to inform you that the incident affecting our Managed Private Registry service has been resolved. Start time : 10/07/2026 20:20 UTC End time : 11/07/2026 00:10 UTC Root Cause : This incident was caused by this maintenance : https://public-cloud.status-ovhcloud.com/incidents/m5qn00qgl9zh We apologize for any inconvenience caused and appreciate your understanding.
Major July 9, 2026 [EU-WEST-PAR][Containers & Orchestration] - Loadbalancer/API/Instance provisioning incident notification 5h 48m EU-WEST-PAR
Started Jul 09, 2026, 08:07 PM UTC· resolved Jul 10, 2026, 01:55 AM UTC
- investigating Jul 09, 2026, 08:07 PM UTC
We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary issue in the EU-WEST-PAR region. Here are some supplementary details : Start time : 09/07/2026 19:20 UTC Impacted Service(s) : Public Cloud API is temporarily facing perturbations. Creation or modification of any LoadBalancer can have issues. Customers Impact : Customers are temporarily facing issues when trying to use the API, create or modify their Loadbalancer. 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 Jul 09, 2026, 08:19 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our DNS offer on the specific region. Here are some supplementary details : Start time : 09/07/2026 19:20 UTC Impacted Service(s) : Public Cloud API is temporarily facing perturbations. Creation or modification of any LoadBalancer can have issues. Customers Impact : Customers are temporarily facing issues when trying to use the API, create or modify their Loadbalancer. Root Cause : This incident is caused by a software issue. 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 Jul 10, 2026, 01:55 AM UTC
We are pleased to inform you that the incident affecting our Load Balancer service has been resolved. Start time : 09/07/2026 19:20 UTC End time : 10/07/2026 01:50 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.