Public Cloud Outage History

Public Cloud is up right now

Pingoru has recorded 205 incidents for Public Cloud: 205 in the last 12 months and 70 in the last 90 days.

Source: public-cloud.status-ovhcloud.com

205incidents recorded
205last 12 months
70last 90 days
48 hourstypical duration
Incidents per month
02040AprMayJunJulAugSepOct24
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct51%
Pingoru began tracking Public Cloud in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20262857 of 720 (8%)
May 202620285 of 744 (38%)
June 202631268 of 720 (37%)
July 202628235 of 744 (32%)
August 202622288 of 744 (39%)
September 202621397 of 720 (55%)
October 202624300 of 584 (51%)

Incidents, newest first

Major September 25, 2026 [US-EAST-VA][Storage] - Object Storage incident notification 3d 21h US-EAST-VA-1

Started Sep 25, 2026, 05:00 PM UTC· resolved Sep 29, 2026, 02:37 PM UTC

  1. investigating Sep 25, 2026, 05:00 PM UTC

    We are currently experiencing an incident affecting our Object Storage offering, which is causing temporary latency and availability issues in the US-EAST-VA region. Please find the details of this incident below : Start time : 25/09/2026 11:00 UTC Impacted Service(s) : Object Storage High Performance and Standard are temporarily facing perturbations in the US-EAST-VA region. Customers Impact : Customers may experience increased latency and 503 errors when accessing their data located in the specified region. 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.

  2. monitoring Sep 25, 2026, 06:41 PM UTC

    We would like to inform you that our service has been fully restored as of 25/09/2026 at 18:20 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : Start time : 25/09/2026 11:00 UTC Impacted Service(s) : Object Storage High Performance and Standard were temporarily facing perturbations in the US-EAST-VA region. Customers Impact : Customers may have experienced increased latency and 503 errors when accessing their data located in the specified region. Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Sep 29, 2026, 02:37 PM UTC

    We are pleased to inform you that the incident affecting our Storage offering has been resolved. Start time : 25/09/2026 11:00 UTC End time : 29/09/2026 14:22 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major September 25, 2026 [US-EAST-VA-1][AI & Machine Learning] - AI Endpoint incident notification 42m AI & Machine Learning || AI Endpoint

Started Sep 25, 2026, 04:27 PM UTC· resolved Sep 25, 2026, 05:09 PM UTC

  1. investigating Sep 25, 2026, 04:27 PM UTC

    We are currently experiencing an incident affecting our AI & Machine Learning offering, which is causing temporary availability and latency issuesissues on AI Endpoint s3.us-east-va.perf.cloud.ovh.us. Please find the details of this incident below : Start time : 25/09/2026 11:00 UTC Impacted Service(s) : Endpoint s3.us-east-va.perf.cloud.ovh.us is temporarily facing perturbations. Customers Impact : Customers may experience latency and 503 errors when accessing their service. 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.

Read the full incident report →

Major September 24, 2026 [EU-SOUTH-MIL-B][Public Cloud] - Block Storage incident notification 8m EU-SOUTH-MIL-B

Started Sep 24, 2026, 09:07 AM UTC· resolved Sep 24, 2026, 09:15 AM UTC

  1. investigating Sep 24, 2026, 09:07 AM UTC

    We are currently experiencing an incident affecting our Public Cloud offering, which is causing temporary availability issues on Block Storage in the EU-SOUTH-MIL-B zone. Please find the details of this incident below : Start time : 24/09/2026 08:25 UTC Impacted Service(s) : Some Block Storage volumes in the EU-SOUTH-MIL-B zone are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their data located on the impacted Block Storage volumes in the specified zone. 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.

  2. resolved Sep 24, 2026, 09:15 AM 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 : 24/09/2026 08:25 UTC End time : 24/09/2026 09:11 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.

Read the full incident report →

Major September 23, 2026 [EU-WEST-PAR][Containers & Orchestration] - Managed Kubernetes Service incident notification 1d 18h EU-WEST-PAR

Started Sep 23, 2026, 02:57 PM UTC· resolved Sep 25, 2026, 09:15 AM UTC

  1. identified Sep 23, 2026, 02:57 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific EU-WEST-PAR region. Here are some supplementary details : Start time : 23/09/2026 14:00 UTC Impacted Service(s) : Public Cloud services hosted in the EU-WEST-PAR region, including customer networks, are experiencing increased latency and packet loss. Customers Impact : Customers are experiencing latency and packet drops when accessing their Public Cloud services and networks hosted in the EU-WEST-PAR region. Root Cause : This incident is caused by this maintenance : https://public-cloud.status-ovhcloud.com/incidents/r4trfs4g4lxc 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.

  2. monitoring Sep 24, 2026, 07:20 AM UTC

    Service has been fully restored. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 23/09/2026 14:00 UTC Impacted Service(s) : Public Cloud services hosted in the EU-WEST-PAR region, including customer networks, experienced increased latency and packet loss. Customers Impact : Customers experienced latency and packet drops when accessing their Public Cloud services and networks hosted in the EU-WEST-PAR region. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Sep 25, 2026, 09:15 AM UTC

    We are pleased to inform you that the incident affecting our Containers & Orchestration offer on the specific EU-WEST-PAR region has been resolved. Start time : 23/09/2026 14:00 UTC End time : 24/09/2026 07:20 UTC Root Cause : The root cause of this incident was related to the incident described in the following status page : https://public-cloud.status-ovhcloud.com/incidents/r4trfs4g4lxc We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major September 23, 2026 [EU-WEST-PAR][Network] - Public network incident notification 1d 18h EU-WEST-PAR-A, EU-WEST-PAR-B, EU-WEST-PAR-C

Started Sep 23, 2026, 02:28 PM UTC· resolved Sep 25, 2026, 09:14 AM UTC

  1. identified Sep 23, 2026, 02:28 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Network offer on the specific EU-WEST-PAR region. Here are some supplementary details : Start time : 23/09/2026 14:00 UTC Impacted Service(s) : Public Cloud services hosted in the EU-WEST-PAR region, including customer networks, experience increased latency and packet loss. Customers Impact : Customers experience latency and packet drops when accessing their Public Cloud services and networks hosted in the EU-WEST-PAR 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.

  2. monitoring Sep 23, 2026, 05:29 PM UTC

    Service has been fully restored since 23/09/2026 17:19 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 23/09/2026 14:00 UTC Impacted Service(s) : Public Cloud services hosted in the EU-WEST-PAR region, including customer networks, experienced increased latency and packet loss. Customers Impact : Customers experienced latency and packet drops when accessing their Public Cloud services and networks hosted in the EU-WEST-PAR region. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Sep 25, 2026, 09:14 AM UTC

    We are pleased to inform you that the incident affecting our Network offer on the specific EU-WEST-PAR region has been resolved. Start time : 23/09/2026 14:00 UTC End time : 24/09/2026 17:19 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Notice September 23, 2026 [EU-WEST-PAR][Identity, Security & Operations] - Key Management Service incident notification – EU-WEST-PAR

Started Sep 23, 2026, 09:32 AM UTC· resolved Sep 23, 2026, 09:32 AM UTC

  1. resolved Sep 23, 2026, 09:32 AM UTC

    We would like to inform you that an incident occurred in the EU-WEST-PAR region. This incident has now been resolved. Please find the details of this incident below : Start time : 22/09/2026 17:20 UTC End time : 23/09/2026 09:00 UTC Impacted Service(s) : The Key Management Service experienced increased latency and packet loss. Customers Impact : Customers experienced latency and packet drops when using the Key Management Service 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.

Read the full incident report →

Minor September 22, 2026 [WAW][Storage] - Block Storage Incident Notification 16h 47m WAW1

Started Sep 22, 2026, 04:32 PM UTC· resolved Sep 23, 2026, 09:20 AM UTC

  1. identified Sep 22, 2026, 04:32 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Block Storage offer in WAW1 Here are some supplementary details : Start time : 22/09/2026 13:07 UTC Impacted Service(s) : Some Block Storage services are temporarily unavailable. Customers Impact : Some customers may temporarily experience degraded performance on their block storage services. Root Cause : https://network.status-ovhcloud.com/incidents/jy9dbvzlrzyw 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.

  2. monitoring Sep 22, 2026, 05:37 PM UTC

    Since 16:45 UTC, the actions taken have improved the situation and restored all services. Monitoring remains active to ensure long-term stability. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Sep 23, 2026, 09:20 AM UTC

    We are pleased to inform you that the incident affecting our Storage offering has been resolved. Start time : 23/09/2026 13:07 UTC End time : 23/09/2026 17:09 UTC Root Cause : https://network.status-ovhcloud.com/incidents/jy9dbvzlrzyw We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major September 22, 2026 [GRA5/7/9/11][Public Cloud] - Some Instances incident notification 3h 30m GRA5, GRA7, GRA9, GRA11

Started Sep 22, 2026, 09:24 AM UTC· resolved Sep 22, 2026, 12:55 PM UTC

  1. investigating Sep 22, 2026, 09:24 AM UTC

    We are currently experiencing an incident affecting our Public Cloud offering in the GRA5/6/7/8/9/11 regions. The root cause has been identified. Here are some supplementary details : Start time : 22/09/2026 08:33 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 regions. Root Cause : This incident is caused by an unexpected 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.

  2. identified Sep 22, 2026, 09:46 AM UTC

    We are currently experiencing an incident affecting our Public Cloud offering in the GRA5/7/9/11 regions. The root cause has been identified. Here are some supplementary details : Start time : 22/09/2026 08:33 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 regions. Root Cause : This incident is caused by an unexpected 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.

  3. resolved Sep 22, 2026, 12:55 PM UTC

    We are pleased to inform you that the incident affecting our Public Cloud offering has been resolved. Start time : 22/09/2026 08:33 UTC End time : 22/09/2026 10:11 UTC Root Cause : This incident was caused by an unexpected infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major September 16, 2026 [GRA7/GRA9/GRA11][Compute - Instance] - Some instances incident notification 59m GRA7, GRA9, GRA11

Started Sep 16, 2026, 02:53 AM UTC· resolved Sep 16, 2026, 03:52 AM UTC

  1. investigating Sep 16, 2026, 02:53 AM UTC

    We are currently experiencing an event affecting our Compute - Instance offer. Start time : 16/09/2026 02:41 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.

  2. identified Sep 16, 2026, 03:14 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 GRA7, GRA9 and GRA11 region. Here are some supplementary details : Start time : 16/09/2026 02:41 UTC Impacted Service(s) : Some instances in the GRA7, GRA9 and 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.

  3. resolved Sep 16, 2026, 03:52 AM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 16/09/2026 02:41 UTC End time : 16/09/2026 03:21 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Minor September 13, 2026 [DE1][Storage] - Ceph volumes incident notification 2h 24m DE1

Started Sep 13, 2026, 12:51 PM UTC· resolved Sep 13, 2026, 03:15 PM UTC

  1. identified Sep 13, 2026, 12:51 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Storage offer on the specific DE1 region. Here are some supplementary details : Start time : 13/09/2026 12:43 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.

  2. resolved Sep 13, 2026, 03:15 PM UTC

    We are pleased to inform you that the incident affecting our Storage offering has been resolved. Start time : 13/09/2026 12:43 UTC End time : 13/09/2026 15:11 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major September 13, 2026 [GRA1/3/9/11][Public Cloud] - Instances incident notification 1h 14m GRA1, GRA3, GRA9, GRA11

Started Sep 13, 2026, 09:24 AM UTC· resolved Sep 13, 2026, 10:39 AM UTC

  1. identified Sep 13, 2026, 09:24 AM UTC

    We are currently experiencing an incident affecting our Public Cloud offering in the GRA1/3/9/11 regions. The root cause has been identified. Please find the details of this incident below : Start time : 13/09/2026 09:02 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 regions. Root Cause : This incident is caused by an unexpected 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.

  2. resolved Sep 13, 2026, 10:39 AM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 13/09/2026 09:02 UTC End time : 13/09/2026 10:06 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major September 10, 2026 [SBG5/7][Compute - Instance] - Some Instances Incident Notification 23h 41m SBG5, SBG7

Started Sep 10, 2026, 10:22 PM UTC· resolved Sep 11, 2026, 10:04 PM UTC

  1. identified Sep 10, 2026, 10: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 SBG5 / SBG7 regions. Here are some supplementary details : Start time : 10/09/2026 22:13 UTC Impacted Service(s) : Some instances in the SBG5 / SBG7 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.

  2. identified Sep 11, 2026, 03:31 AM UTC

    We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Some instances are now accessible again. Ongoing Actions : Our teams are actively working to restore the remaining instances as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  3. identified Sep 11, 2026, 01:08 PM UTC

    We have new information regarding the incident that affects your service(s). Please find below an update on the situation : Update : Most instances are once again accessible. Impacted Service(s) : Some instances in the SBG5 / SBG7 regions are still temporarily unreachable. Customers Impact : Some customers are still temporarily unable to access instances located in the specified regions. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : Our teams are actively working to restore the remaining instances as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  4. resolved Sep 11, 2026, 10:04 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 10/09/2026 22:13 UTC End time : 11/09/2026 21: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.

Read the full incident report →

Major September 6, 2026 [GRA11][Containers & Orchestration] - Managed Kubernetes Service Incident Notification 1h 35m GRA11

Started Sep 06, 2026, 10:13 AM UTC· resolved Sep 06, 2026, 11:48 AM UTC

  1. investigating Sep 06, 2026, 10:13 AM UTC

    We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary availability issue in the GRA11 region. Here are some supplementary details : Start time : 06/09/2026 09:00 UTC Impacted Service(s) : The Managed Kubernetes Service cluster is experiencing high load. Customers Impact : Customers are experiencing degraded service performance and are currently unable to provision new resources. 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.

  2. resolved Sep 06, 2026, 11:48 AM UTC

    We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved. Start time : 06/09/2026 09:00 UTC End time : 06/09/2026 10:45 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Minor September 3, 2026 [GRA1/GRA11][Storage] - Block storage incident notification 3h 22m GRA1, GRA11

Started Sep 03, 2026, 03:39 PM UTC· resolved Sep 03, 2026, 07:01 PM UTC

  1. investigating Sep 03, 2026, 03:39 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Storage offer on the specific GRA1 and GRA11 region. Here are some supplementary details : Start time : 03/09/2026 15:16 UTC Impacted Service(s) : Some Block Storage services are temporarily unavailable. Customers Impact : Some customers may temporarily experience degraded performance on their block storage 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.

  2. identified Sep 03, 2026, 03:44 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Storage offer on the specific GRA1 and GRA11 region. Here are some supplementary details : Start time : 03/09/2026 15:16 UTC Impacted Service(s) : Some Block Storage services are temporarily unavailable. Customers Impact : Some customers may temporarily experience degraded performance on their block storage 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.

  3. resolved Sep 03, 2026, 07:01 PM UTC

    We are pleased to inform you that the incident affecting our Storage offering has been resolved. Start time : 03/09/2026 15:16 UTC End time : 03/09/2026 18:41 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major September 3, 2026 [GLOBAL][Databases] - MongoDB incident notification 21h 22m BHS, DE, GRA, EU-WEST-PAR and 9 more

Started Sep 03, 2026, 10:18 AM UTC· resolved Sep 04, 2026, 07:40 AM UTC

  1. investigating Sep 03, 2026, 10:18 AM UTC

    We are currently experiencing an incident affecting our MongoDB Database offering. Please find the details of this incident below : Start time : 25/08/2026 00:00 UTC Impacted Service(s) : MongoDB services are currently unable to perform their daily backups. Customers Impact : Customers using the affected MongoDB services are currently unable to perform their daily backups. Ongoing Actions : Our teams are investigating the issue to determine its root cause and restore the backup functionality. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  2. monitoring Sep 03, 2026, 02:04 PM UTC

    Service has been fully restored since 03/09/2026 13:00 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 25/08/2026 00:00 UTC Impacted Service(s) : MongoDB services were unable to perform their daily backups. Customers Impact : Customers using the affected MongoDB services were unable to perform their daily backups. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Sep 04, 2026, 07:40 AM UTC

    We are pleased to inform you that the incident affecting our MongoDB Database offering has been resolved. Start time : 25/08/2026 00:00 UTC End time : 03/09/2026 13: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.

Read the full incident report →

Major August 31, 2026 [GRA5/GRA7/GRA9/GRA11][Compute - Instance] - Compute Instance Incident Notification 59m GRA5, GRA7, GRA9, GRA11

Started Aug 31, 2026, 05:09 PM UTC· resolved Aug 31, 2026, 06:09 PM UTC

  1. investigating Aug 31, 2026, 05:09 PM UTC

    We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary issue in the GRA5/GRA7/GRA9/GRA11Region. Here are some supplementary details : Start time : 31/08/2026 16:49 UTC Impacted Service(s) : Some instances in the GRA3 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.

  2. investigating Aug 31, 2026, 05:13 PM UTC

    We are continuing to investigate this issue.

  3. resolved Aug 31, 2026, 06:09 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 31/08/2026 16:49 UTC End time : 31/08/2026 17:47 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Notice August 28, 2026 [GRA1][Compute - Instance] - Instance incident notification 8m GRA1

Started Aug 28, 2026, 11:03 PM UTC· resolved Aug 28, 2026, 11:11 PM UTC

  1. resolved Aug 28, 2026, 11:19 PM UTC

    We would like to inform you that an incident occurred in the GRA1 region. This incident has now been resolved. Please find the details of this incident below : Start time : 28/08/2026 23:03 UTC End time : 28/08/2026 23:11 UTC Impacted Service(s) : Some instances in the GRA1 region were unreachable. Customers Impact : Some customers were temporarily unable to access instances located on 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.

Read the full incident report →

Minor August 26, 2026 [EU-SOUTH-MIL][Containers & Orchestration] - Managed Private Registry incident notification 40d 16h EU-SOUTH-MIL

Started Aug 26, 2026, 03:00 PM UTC· resolved Oct 06, 2026, 07:53 AM UTC

  1. investigating Sep 18, 2026, 09:20 AM UTC

    We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary issue in the region. Here are some supplementary details : Start time : 18/09/2026 08:44 UTC Impacted Service(s) : Slowdowns or interruptions in the transmission of artifacts. Customers Impact : Customers may experience slowdowns or interruptions when sending artifacts. 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.

  2. investigating Oct 05, 2026, 06:43 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 still actively working on the incident. Ongoing Actions : Our teams are still 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.

  3. resolved Oct 06, 2026, 07:53 AM UTC

    We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved. Start time : 26/08/2026 15:00 UTC End time : 06/10/2026 07:00 UTC Root Cause : This incident was caused by a network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major August 25, 2026 [GLOBAL][Data & Analytics] - Cloud Database Incident Notification 1d 15h BHS, BHS, BHS, BHS and 54 more

Started Aug 25, 2026, 09:25 PM UTC· resolved Aug 27, 2026, 01:08 PM UTC

  1. identified Aug 25, 2026, 09:25 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer. Here are some supplementary details : Start time : 25/08/2026 14:00 UTC Impacted Service(s) : Ordering services in private network, resulting in delays and possible failures. Customers Impact : Customers may experience delays and intermittent failures when ordering new services. Existing services are not impacted. 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.

  2. identified Aug 26, 2026, 12:35 PM 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 now operational again, with some residual delays or intermittent failures possible. Most customers should now be able to order new services normally. Ongoing Actions : The incident has been identified, and our teams are actively working to restore the remaining impacted services as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Aug 27, 2026, 01:08 PM UTC

    We are pleased to inform you that the incident affecting our Data & Analytics offering has been resolved. Start time : 25/08/2026 14:00 UTC End time : 27/08/2026 13:02 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major August 25, 2026 [GLOBAL][Identity, Security & Operations] - User Management Incident Notification 2h 23m Identity, Security & Operations || Authentication

Started Aug 25, 2026, 06:21 PM UTC· resolved Aug 25, 2026, 08:45 PM UTC

  1. investigating Aug 25, 2026, 06:21 PM UTC

    We are currently investigating an incident affecting our Identity, Security & Operations offering, which is causing temporary availability issue in the global region Here are some supplementary details : Start time : 25/08/2026 17:52 UTC Impacted Service(s) : The user creation and approval service is temporarily unavailable. Customers Impact : Customers are temporarily unable to create new users or use the approval service. 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.

  2. identified Aug 25, 2026, 06:40 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Identity, Security & Operations offer on the specific global region Here are some supplementary details : Start time : 25/08/2026 18:38 UTC Impacted Service(s) : The user creation and approval service is temporarily unavailable. Customers Impact : Customers are temporarily unable to create new users or use the approval service. 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.

  3. resolved Aug 25, 2026, 08:45 PM UTC

    We are pleased to inform you that the incident affecting our Identity, Security & Operations offering has been resolved. Start time : 25/08/2026 17:52 UTC End time : 25/08/2026 20:40 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major August 25, 2026 [GRA5/6/7/8/9/11][Compute - Instance] - Instance incident notification 47m GRA3

Started Aug 25, 2026, 06:24 AM UTC· resolved Aug 25, 2026, 07:11 AM UTC

  1. identified Aug 25, 2026, 06:24 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 GRA3 region. Here are some supplementary details : Start time : 25/08/2026 06:05 UTC Impacted Service(s) : Some instances in the GRA3 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.

  2. resolved Aug 25, 2026, 07:11 AM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 25/08/2026 06:05 UTC End time : 25/08/2026 07:03 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major August 23, 2026 [GRA3][Compute - Instance] - Compute Instance Incident Notification 11m GRA3

Started Aug 23, 2026, 11:45 PM UTC· resolved Aug 23, 2026, 11:57 PM UTC

  1. investigating Aug 23, 2026, 11:45 PM UTC

    We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary issue in the [Rack/Cluster/Room/Region/Geographical zone]. Here are some supplementary details : Start time : 23/08/2026 23:38 UTC Impacted Service(s) : Some instances in the GRA3 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.

  2. identified Aug 23, 2026, 11:46 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 [Rack/Cluster/Room/Region/Geographical zone]. Here are some supplementary details : Start time : 23/08/2026 23:38 UTC Impacted Service(s) : Some instances in the GRA3 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.

  3. identified Aug 23, 2026, 11:53 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 23/08/2026 23:38 UTC End time : 23/08/2026 23:49 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

  4. resolved Aug 23, 2026, 11:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 22, 2026 [GRA11][Public Cloud] - API incident notification 35m GRA11

Started Aug 22, 2026, 01:10 AM UTC· resolved Aug 22, 2026, 01:46 AM UTC

  1. monitoring Aug 22, 2026, 01:10 AM UTC

    Service has been fully restored since 22/08/2026 01:09 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 22/08/2026 00:53 UTC Impacted Service(s) : The API in the GRA11 region was temporarily unavailable. Customers Impact : Customers are having issues to create, start, or manage their instances located in the specified region. We apologize for any inconvenience caused and appreciate your understanding.

  2. resolved Aug 22, 2026, 01:46 AM UTC

    We are pleased to inform you that the incident affecting our Public Cloud offering has been resolved. Start time : 22/08/2026 00:53 UTC End time : 22/08/2026 01:09 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major August 18, 2026 [GRA5/7/9/11][Compute - Instance] - Some instances incident notification 1h 32m GRA5, GRA7, GRA9, GRA11

Started Aug 18, 2026, 02:34 PM UTC· resolved Aug 18, 2026, 04:06 PM UTC

  1. identified Aug 18, 2026, 02:34 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 regions. Here are some supplementary details : Start time : 18/08/2026 14:09 UTC Impacted Service(s) : Some instances in the GRA5/7/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.

  2. resolved Aug 18, 2026, 04:06 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering in GRA5/7/9/11 regions has been resolved. Start time : 18/08/2026 14:09 UTC End time : 18/08/2026 15: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.

Read the full incident report →

Notice August 17, 2026 [SBG][Storage] - Object Storage S3 incident notification 1d SBG

Started Aug 17, 2026, 10:36 AM UTC· resolved Aug 18, 2026, 11:35 AM UTC

  1. monitoring Aug 17, 2026, 10:36 AM UTC

    Service has been fully restored since 17/08/2026 10:12 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 17/08/2026 09:31 UTC Impacted Service(s) : 503 errors where temporarily present. Customers Impact : Customers were temporarily facing 503 errors when trying to access Object Storage S3 in SBG. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

  2. monitoring Aug 18, 2026, 07:59 AM UTC

    We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Ongoing Actions : Our team continues to closely monitor the situation to ensure the service remains stable and fully operational. We will keep you informed as soon as further information becomes available.

  3. resolved Aug 18, 2026, 11:35 AM UTC

    We are pleased to inform you that the incident affecting our Storage offering has been resolved. Start time : 17/08/2026 09:31 UTC End time : 18/08/2026 11:33 UTC Root Cause : This incident was caused by a network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →