Public Cloud Outage History

Public Cloud degraded · 2 active incidents View live status →

Public Cloud had 146 outages in the last 2 years totaling 221h 32m of downtime — averaging 6 incidents per month.

There were 146 Public Cloud outages since October 30, 2025 totaling 221h 32m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://public-cloud.status-ovhcloud.com

Major September 16, 2026

[GRA7/GRA9/GRA11][Compute - Instance] - Some instances incident notification

Detected by Pingoru
Sep 16, 2026, 02:53 AM UTC
Resolved
Sep 16, 2026, 03:52 AM UTC
Duration
59m
Affected: GRA7GRA9GRA11
Timeline · 3 updates
  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

Detected by Pingoru
Sep 13, 2026, 12:51 PM UTC
Resolved
Sep 13, 2026, 03:15 PM UTC
Duration
2h 24m
Affected: DE1
Timeline · 2 updates
  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

Detected by Pingoru
Sep 13, 2026, 09:24 AM UTC
Resolved
Sep 13, 2026, 10:39 AM UTC
Duration
1h 14m
Affected: GRA1GRA3GRA9GRA11
Timeline · 2 updates
  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

Detected by Pingoru
Sep 10, 2026, 10:22 PM UTC
Resolved
Sep 11, 2026, 10:04 PM UTC
Duration
23h 41m
Affected: SBG5SBG7
Timeline · 4 updates
  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

Detected by Pingoru
Sep 06, 2026, 10:13 AM UTC
Resolved
Sep 06, 2026, 11:48 AM UTC
Duration
1h 35m
Affected: GRA11
Timeline · 2 updates
  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

Detected by Pingoru
Sep 03, 2026, 03:39 PM UTC
Resolved
Sep 03, 2026, 07:01 PM UTC
Duration
3h 22m
Affected: GRA1GRA11
Timeline · 3 updates
  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

Detected by Pingoru
Sep 03, 2026, 10:18 AM UTC
Resolved
Sep 04, 2026, 07:40 AM UTC
Duration
21h 22m
Affected: BHSDEGRAEU-WEST-PARSBGSGPUKWAWEU-SOUTH-MILRBXAP-SOUTH-MUMUS-EAST-VAUS-WEST-OR
Timeline · 3 updates
  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

Detected by Pingoru
Aug 31, 2026, 05:09 PM UTC
Resolved
Aug 31, 2026, 06:09 PM UTC
Duration
59m
Affected: GRA5GRA7GRA9GRA11
Timeline · 3 updates
  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

Detected by Pingoru
Aug 28, 2026, 11:19 PM UTC
Resolved
Aug 28, 2026, 11:19 PM UTC
Duration
Affected: GRA1
Timeline · 1 update
  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 →

Major August 25, 2026

[GLOBAL][Data & Analytics] - Cloud Database Incident Notification

Detected by Pingoru
Aug 25, 2026, 09:25 PM UTC
Resolved
Aug 27, 2026, 01:08 PM UTC
Duration
1d 15h
Affected: BHSBHSBHSBHSBHSEU-WEST-PARDEDEDEDEDEEU-SOUTH-MILGRAGRAGRAGRAGRAAP-SOUTH-MUMEU-WEST-PAREU-WEST-PAREU-SOUTH-MILEU-SOUTH-MILEU-SOUTH-MILSBGAP-SOUTH-MUMEU-SOUTH-MILAP-SOUTH-MUMAP-SOUTH-MUMEU-WEST-PAREU-WEST-PAREU-WEST-PARSGPAP-SOUTH-MUMUKRBXRBXRBXRBXSBGWAWSBGSBGSBGSGPSGPSGPSGPEU-SOUTH-MILUKUKUKAP-SOUTH-MUMWAWUKRBXWAWWAWWAW
Timeline · 3 updates
  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

Detected by Pingoru
Aug 25, 2026, 06:21 PM UTC
Resolved
Aug 25, 2026, 08:45 PM UTC
Duration
2h 23m
Affected: Identity, Security & Operations || Authentication
Timeline · 3 updates
  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

Detected by Pingoru
Aug 25, 2026, 06:24 AM UTC
Resolved
Aug 25, 2026, 07:11 AM UTC
Duration
47m
Affected: GRA3
Timeline · 2 updates
  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

Detected by Pingoru
Aug 23, 2026, 11:45 PM UTC
Resolved
Aug 23, 2026, 11:57 PM UTC
Duration
11m
Affected: GRA3
Timeline · 4 updates
  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

Detected by Pingoru
Aug 22, 2026, 01:10 AM UTC
Resolved
Aug 22, 2026, 01:46 AM UTC
Duration
35m
Affected: GRA11
Timeline · 2 updates
  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

Detected by Pingoru
Aug 18, 2026, 02:34 PM UTC
Resolved
Aug 18, 2026, 04:06 PM UTC
Duration
1h 32m
Affected: GRA5GRA7GRA9GRA11
Timeline · 2 updates
  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

Detected by Pingoru
Aug 17, 2026, 10:36 AM UTC
Resolved
Aug 18, 2026, 11:35 AM UTC
Duration
1d
Affected: SBG
Timeline · 3 updates
  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 →

Notice August 15, 2026

[GRA3][Storage] - Block storage incident notification

Detected by Pingoru
Aug 15, 2026, 02:36 PM UTC
Resolved
Aug 15, 2026, 02:36 PM UTC
Duration
Affected: GRA3
Timeline · 1 update
  1. 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.

Read the full incident report →

Major August 14, 2026

[GRA11][Storage] - File storage incident notification

Detected by Pingoru
Aug 14, 2026, 04:07 PM UTC
Resolved
Aug 15, 2026, 05:44 AM UTC
Duration
13h 36m
Affected: GRA11
Timeline · 2 updates
  1. 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.

  2. 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.

Read the full incident report →

Major August 14, 2026

[GRA5/GRA9/GRA11][Compute - Instance] - Some instances incident notification

Detected by Pingoru
Aug 14, 2026, 03:26 PM UTC
Resolved
Aug 15, 2026, 05:43 AM UTC
Duration
14h 16m
Affected: GRA5GRA9GRA11
Timeline · 3 updates
  1. 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.

  2. 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.

  3. 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.

Read the full incident report →

Notice August 13, 2026

[EU-WEST-PAR][Storage] - Object storage incident notification

Detected by Pingoru
Aug 13, 2026, 10:53 AM UTC
Resolved
Aug 13, 2026, 02:42 PM UTC
Duration
3h 49m
Affected: EU-WEST-PAR-AEU-WEST-PAR-BEU-WEST-PAR-C
Timeline · 2 updates
  1. 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.

  2. 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.

Read the full incident report →

Minor August 11, 2026

[GRA11][Public Cloud] - Barbican incident notification

Detected by Pingoru
Aug 11, 2026, 12:18 PM UTC
Resolved
Aug 12, 2026, 08:08 AM UTC
Duration
19h 49m
Affected: GRA11GRA11
Timeline · 3 updates
  1. 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.

  2. investigating Aug 11, 2026, 12:25 PM UTC

    We are continuing to investigate this issue.

  3. 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.

Read the full incident report →

Minor August 10, 2026

[EU/APAC][Storage] - Encrypted Volume Incident notification

Detected by Pingoru
Aug 10, 2026, 03:16 PM UTC
Resolved
Aug 11, 2026, 12:27 PM UTC
Duration
21h 11m
Affected: AP-SOUTHEAST-SYD-2AP-SOUTH-MUM-1DE1EU-SOUTH-MIL-AEU-SOUTH-MIL-BEU-SOUTH-MIL-CEU-WEST-PAR-AEU-WEST-PAR-BEU-WEST-PAR-CGRA1GRA3GRA5GRA6GRA7GRA9GRA11RBX-ASBG5SBG7SGP1UK1WAW1
Timeline · 1 update
  1. 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.

Read the full incident report →

Minor August 7, 2026

[BHS][Compute - Instance] - Compute Instance Incident Notification

Detected by Pingoru
Aug 07, 2026, 03:26 PM UTC
Resolved
Aug 07, 2026, 06:45 PM UTC
Duration
3h 19m
Affected: BHS1
Timeline · 2 updates
  1. 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.

  2. 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.

Read the full incident report →

Minor August 5, 2026

[BHS5][Storage] - Ceph volumes incident notification

Detected by Pingoru
Aug 05, 2026, 05:32 PM UTC
Resolved
Aug 06, 2026, 01:08 PM UTC
Duration
19h 36m
Affected: BHS5
Timeline · 3 updates
  1. 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.

  2. 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.

  3. 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.

Read the full incident report →

Notice August 5, 2026

[DE1][Storage] - Some CEPH volumes incident notification

Detected by Pingoru
Aug 05, 2026, 03:33 PM UTC
Resolved
Aug 05, 2026, 03:33 PM UTC
Duration
Affected: DE1
Timeline · 1 update
  1. 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.

Read the full incident report →