Public Cloud Outage History

Public Cloud is up right now

Public Cloud had 84 outages in the last 2 years totaling 724h 0m of downtime — averaging 3.5 incidents per month.

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

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

Minor June 17, 2026

[EU-WEST-PAR][Public Cloud] - Network connectivity issues notification

Detected by Pingoru
Jun 17, 2026, 01:23 PM UTC
Resolved
Jun 17, 2026, 02:44 PM UTC
Duration
1h 21m
Affected: EU-WEST-PAR-AEU-WEST-PAR-BEU-WEST-PAR-AEU-WEST-PAR-CEU-WEST-PAR-BEU-WEST-PAR-C
Timeline · 2 updates
  1. identified Jun 17, 2026, 01:23 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Public Cloud offer on the specific EU-WEST-PAR region. Here are some supplementary details : Start time : 09/06/2026 07:00 UTC Impacted Service(s) : Nodes located in EU-WEST-PAR region may experience packets drop while communicating with their controlplanes and the Internet. Customers Impact : Customer are temporarily facing connectivity issues with their nodes 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.

  2. resolved Jun 17, 2026, 02:44 PM UTC

    We are pleased to inform you that the incident affecting our Public Cloud offering has been resolved. Start time : 15/06/2026 23:00 UTC End time : 17/06/2026 14:25 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Notice June 17, 2026

[GRA7][Containers & Orchestration] - Managed Kubernetes Service incident notification

Detected by Pingoru
Jun 17, 2026, 08:21 AM UTC
Resolved
Jun 17, 2026, 08:21 AM UTC
Duration
Affected: GRA7
Timeline · 1 update
  1. resolved Jun 17, 2026, 08:21 AM UTC

    We had an incident on Containers & Orchestration offer in GRA7 region which has now been resolved. Here are some supplementary details : Start time : 17/06/2026 07:40 UTC End time : 17/06/2026 08:10 UTC Impacted Service(s) : Managed Kubernetes Service's API was temporarily unavailable. Customers Impact : Customers were temporarily unable to use the API of Managed Kubernetes Service. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.

Read the full incident report →

Major June 15, 2026

[DE1][Compute - Instance] - Some instances incident notification

Detected by Pingoru
Jun 15, 2026, 08:46 AM UTC
Resolved
Jun 15, 2026, 09:58 AM UTC
Duration
1h 11m
Affected: DE1
Timeline · 2 updates
  1. identified Jun 15, 2026, 08:46 AM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the DE1 region. Here are some supplementary details : Start time : 15/06/2026 08:36 UTC Impacted Service(s) :Some instances in the DE1 region are unreachable. Customers Impact : Customers are temporarily unable to access and use their 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 Jun 15, 2026, 09:58 AM UTC

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

Read the full incident report →

Major June 11, 2026

[GRA][Data & Analytics] - Data Platform Incident Notification

Detected by Pingoru
Jun 11, 2026, 12:32 PM UTC
Resolved
Jun 11, 2026, 04:16 PM UTC
Duration
3h 43m
Affected: Data & Analytics || Data Platform
Timeline · 2 updates
  1. investigating Jun 11, 2026, 12:32 PM UTC

    We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary availability issue in GLOBAL regions. Here are some supplementary details : Start time : 11/06/2026 09:00 UTC Impacted Service(s) : Some jobs cannot be executed on the Data Platform. Customers Impact : Some customers cannot run some jobs, causing delays in data processing and dependent workflows. 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 Jun 11, 2026, 04:16 PM UTC

    We are pleased to inform you that the incident affecting our Data & Analytics offering has been resolved. Start time : 10/06/2026 12:00 UTC End time : 11/06/2026 13:00 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 June 10, 2026

[SBG5][Storage] - Block storage incident notification

Detected by Pingoru
Jun 10, 2026, 01:25 AM UTC
Resolved
Jun 10, 2026, 08:26 AM UTC
Duration
7h 1m
Affected: SBG5
Timeline · 3 updates
  1. identified Jun 10, 2026, 01:25 AM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Block storage offer in SBG5. Please find the details of this incident below : Start time : 10/06/2026 00:50 UTC Impacted Service(s) : Block storage service is experiencing degraded performance. Customers Impact : Customers may experience increased latency, slower response times, or intermittent errors when accessing or managing data stored on the affected Block Storage. 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 Jun 10, 2026, 01:30 AM UTC

    Service has been fully restored since 10/06/2026 01:26 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 10/06/2026 00:50 UTC Impacted Service(s) : Block Storage service experienced degraded performance. Customers Impact : Customers may have experienced increased latency, slower response times, or intermittent errors when accessing or managing data stored on the affected Block Storage. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Jun 10, 2026, 08:26 AM UTC

    We are pleased to inform you that the incident affecting our Block storage offering has been resolved. Start time : 10/06/2026 00:50 UTC End time : 10/06/2026 07:10 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 June 9, 2026

[GRA1/3/9][Compute - Instance] - Some instances incident notification

Detected by Pingoru
Jun 09, 2026, 01:50 PM UTC
Resolved
Jun 10, 2026, 01:05 AM UTC
Duration
11h 14m
Affected: GRA1GRA3GRA9
Timeline · 4 updates
  1. identified Jun 09, 2026, 01: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 GRA1/3/9 regions. Here are some supplementary details : Start time : 09/06/2026 13:35 UTC Impacted Service(s) : All or some instances in the GRA1/3/9 regions are unreachable. Customers Impact : Some customers are temporarily unable to access and use their Public Cloud instances located in 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 Jun 09, 2026, 04:51 PM 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 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.

  3. identified Jun 09, 2026, 10:00 PM UTC

    Ongoing Actions : Our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  4. resolved Jun 10, 2026, 01:05 AM UTC

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

Read the full incident report →

Major June 6, 2026

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

Detected by Pingoru
Jun 06, 2026, 04:28 PM UTC
Resolved
Jun 06, 2026, 07:00 PM UTC
Duration
2h 32m
Affected: GRA5GRA7GRA11
Timeline · 2 updates
  1. identified Jun 06, 2026, 04:28 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 GRA region. Here are some supplementary details : Start time : 06/06/2026 15:06 UTC Impacted Service(s) : Some instances in the GRA5 - GRA7 - GRA11 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 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 Jun 06, 2026, 07:00 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 06/06/2026 15:06 UTC End time : 06/06/2026 18:55 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 June 6, 2026

[DE][Containers & Orchestration] - Managed Private Registry incident notification

Detected by Pingoru
Jun 06, 2026, 11:23 AM UTC
Resolved
Jun 07, 2026, 08:05 AM UTC
Duration
20h 42m
Affected: DE
Timeline · 3 updates
  1. investigating Jun 06, 2026, 11:23 AM UTC

    We are currently investigating an incident affecting our Managed Private Registry offering, which is causing temporary availability issue in DE region. Please find the details of this incident below : Start time : 06/06/2026 05:35 UTC Impacted Service(s) : Some Registries may be unavailable. Customers Impact : Customers may experience issues performing registry-related operations. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  2. identified Jun 06, 2026, 04:23 PM UTC

    We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Some Registries in the LIM region are operational again. However, the performance of the some Registries may be temporarily degraded. 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 Jun 07, 2026, 08:05 AM UTC

    We are pleased to inform you that the incident affecting our Managed Private Registry offering has been resolved. Start time : 06/06/2026 05:35 UTC End time : 07/06/2026 08:00 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 June 5, 2026

[GRA1/3/7/9][Compute - Instance] - Some Instances Incident Notification

Detected by Pingoru
Jun 05, 2026, 08:28 PM UTC
Resolved
Jun 05, 2026, 09:00 PM UTC
Duration
32m
Affected: GRA1GRA3GRA7GRA9
Timeline · 2 updates
  1. investigating Jun 05, 2026, 08:28 PM UTC

    We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in GRA1/3/7/9 regions. Here are some supplementary details : Start time : 05/06/2026 20:14 UTC Impacted Service(s) : Some instances in the GRA1/3/7/9 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. 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 Jun 05, 2026, 09:00 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 05/06/2026 20:14 UTC End time : 05/06/2026 20: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.

Read the full incident report →

Minor June 4, 2026

[Global][PCI-Databases] - MongoDB incident notification

Detected by Pingoru
Jun 04, 2026, 09:28 AM UTC
Resolved
Jun 05, 2026, 06:26 AM UTC
Duration
20h 57m
Affected: BHSDEGRAEU-WEST-PARSBGSGPUKWAWEU-SOUTH-MILRBXAP-SOUTH-MUMUS-EAST-VAUS-WEST-OR
Timeline · 4 updates
  1. investigating Jun 04, 2026, 09:28 AM UTC

    We are currently investigating an incident affecting our PCI-Databases offering, which is causing temporary degraded issue in the Global region. Here are some supplementary details : Start time : 03/06/2026 12:00 UTC Impacted Service(s) : Some MongoDB databases that initially run with 3 nodes may temporarily run with 2 nodes. Customers Impact : Customers with 3 node MongoDB services may temporarily operate with only 2 nodes. No latency or data loss is observed. 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 Jun 04, 2026, 09:33 AM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PCI-Databases offer on the specific global region. Here are some supplementary details : Start time : 03/06/2026 12:00 UTC Impacted Service(s) : Some MongoDB databases that initially run with 3 nodes may temporarily run with 2 nodes. Customers Impact : Customers with 3 node MongoDB services may temporarily operate with only 2 nodes. No latency or data loss is observed. 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. monitoring Jun 04, 2026, 12:07 PM UTC

    Service has been fully restored since 04/06/2026 12:00 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 03/06/2026 12:00 UTC Impacted Service(s) : Some MongoDB databases that initially ran with 3 nodes temporarily ran with 2 nodes Customers Impact : Customers with 3-node MongoDB services temporarily operated with only 2 nodes. No latency or data loss was observed 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 Jun 05, 2026, 06:26 AM UTC

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

Read the full incident report →

Major June 4, 2026

[GLOBAL][AI & Machine Learning] - Qwen3.5-397B-A17B incident notification

Detected by Pingoru
Jun 04, 2026, 07:46 AM UTC
Resolved
Jun 04, 2026, 12:22 PM UTC
Duration
4h 36m
Affected: AI & Machine Learning || AI Endpoint
Timeline · 2 updates
  1. identified Jun 04, 2026, 07:46 AM UTC

    We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary issue for the model Qwen3.5-397B-A17B. Here are some supplementary details : Start time : 03/06/2026 22:30 UTC Impacted Service(s) : The AI endpoint Qwen3.5-397B-A17B is not reachable. Customers Impact : Customers are temporarily unable to access their endpoint model. 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 Jun 04, 2026, 12:22 PM UTC

    We are pleased to inform you that the incident affecting our AI & Machine Learning offering has been resolved. Start time : 03/06/2026 22:30 UTC End time : 04/06/2026 10:10 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 June 3, 2026

PCI - EU-WEST-PAR - host1878809

Detected by Pingoru
Jun 03, 2026, 12:59 AM UTC
Resolved
Jun 03, 2026, 02:01 AM UTC
Duration
1h 2m
Timeline · 2 updates
  1. investigating Jun 03, 2026, 12:59 AM UTC

    Estimated time to recovery : 4 hour(s) Affected hosts host1878809 Affected instances The list of instances listed below are currently unavailable, due to hardware fault on the hypervisor(s) previously mentioned. We apologize for any inconvenience caused while we resolve this issue. 6366b462-028e-4155-bea5-060db8ae0be6

  2. resolved Jun 03, 2026, 02:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 2, 2026

[GRA][Identity, Security & Operations] - Logs Data Platform incident notification

Detected by Pingoru
Jun 02, 2026, 08:18 AM UTC
Resolved
Jun 02, 2026, 08:18 AM UTC
Duration
Affected: GRA
Timeline · 1 update
  1. resolved Jun 02, 2026, 08:18 AM UTC

    We had an incident on Logs Data Platform offer in GRA which has now been resolved. Here are some supplementary details : Start time : 02/06/2026 07:31 UTC End time : 02/06/2026 07:50 UTC Impacted Service(s) : The Logs Data Platform service were temporarily unavailable. Customers Impact : Customers were temporarily unable to use Logs Data Platform service. 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 May 30, 2026

[BHS7][Compute - Instance] - Compute Instance Incident Notification

Detected by Pingoru
May 30, 2026, 07:47 AM UTC
Resolved
May 30, 2026, 12:06 PM UTC
Duration
4h 18m
Affected: BHS1BHS3BHS5BHS7
Timeline · 3 updates
  1. investigating May 30, 2026, 07:47 AM UTC

    We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in BHS regions. Here are some supplementary details : Start time : 30/05/2026 07:32 UTC Impacted Service(s) : Some instances in the BHS regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. 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 May 30, 2026, 08:04 AM UTC

    We have determined the origin of the issue affecting our Compute - Instance offer in the specific BHS7 region. Here are some supplementary details : Start time : 30/05/2026 07:32 UTC Impacted Service(s) : Some instances in the BHS7 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 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 May 30, 2026, 12:06 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 30/05/2026 07:32 UTC End time : 30/05/2026 11:30 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 May 27, 2026

[BHS1/3][Compute - Instance] - Some instances incident notification

Detected by Pingoru
May 27, 2026, 05:57 PM UTC
Resolved
May 27, 2026, 05:57 PM UTC
Duration
Affected: BHS1BHS3
Timeline · 1 update
  1. resolved May 27, 2026, 05:57 PM UTC

    We had an incident on our Compute - Instance offer in BHS1 and BHS3 regions which has now been resolved. Here are some supplementary details : Start time : 27/05/2026 15:46 UTC End time : 27/05/2026 17:29 UTC Impacted Service(s) : Some instances in BHS1 and BHS3 regions were unreachable. Customers Impact : Some customers were temporarily unable to access and use their instances in the specified regions. 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 May 27, 2026

[AP-SOUTH-MUM/EU-SOUTH-MIL/EU-WEST-PAR/RBX][Containers & Orchestration] - Managed Kubernetes Service Incident Notification

Detected by Pingoru
May 27, 2026, 03:27 PM UTC
Resolved
May 28, 2026, 02:25 PM UTC
Duration
22h 58m
Affected: AP-SOUTH-MUMEU-SOUTH-MILEU-WEST-PARRBX
Timeline · 3 updates
  1. investigating May 27, 2026, 03:27 PM UTC

    We are currently experiencing an event affecting our Managed Kubernetes Service in AP-SOUTH-MUM / EU-SOUTH-MIL / EU-WEST-PAR / RBX regions. Start time : 27/05/2026 14:00 UTC Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible. We apologize for any inconvenience caused and appreciate your understanding.

  2. identified May 27, 2026, 04:02 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration - Managed Kubernetes Service in AP-SOUTH-MUM / EU-SOUTH-MIL / EU-WEST-PAR / RBX regions. Here are some supplementary details : Start time : 27/05/2026 14:00 UTC Impacted Service(s) : MKS cluster delivery and deletion is currently unavailable. Customers Impact : Customers are currently unable to create new MKS clusters and to add or edit nodepools. Root Cause : A service disruption is currently occurring due to an unexpected infrastructure malfunction. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved May 28, 2026, 02:25 PM UTC

    We are pleased to inform you that the incident affecting our Containers & Orchestration - Managed Kubernetes Service offering in AP-SOUTH-MUM / EU-SOUTH-MIL / EU-WEST-PAR / RBX regions has been resolved. Start time : 27/05/2026 14:00 UTC End time : 28/05/2026 13:56 UTC Root Cause : A service disruption is currently occurring due to an unexpected infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Minor May 25, 2026

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

Detected by Pingoru
May 25, 2026, 09:30 AM UTC
Resolved
May 25, 2026, 06:06 PM UTC
Duration
8h 36m
Affected: GRA1
Timeline · 3 updates
  1. investigating May 25, 2026, 09:30 AM UTC

    We are currently investigating an incident affecting our Storage offering, which is causing temporary latency issue in the GRA1 region. Here are some supplementary details : Start time : 25/05/2026 07:30 UTC Impacted Service(s) : Some Ceph volumes may temporarily experience degraded performance. Customers Impact : Some customers may temporarily experience degraded performance on their Ceph 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.

  2. monitoring May 25, 2026, 02:02 PM UTC

    Service has been fully restored since 25/05/2026 12:50 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 25/05/2026 07:30 UTC Impacted Service(s) : Some Ceph volumes may temporarily experience degraded performance. Customers Impact : Some customers may temporarily experience degraded performance on their Ceph volumes. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved May 25, 2026, 06:06 PM UTC

    We are pleased to inform you that the incident affecting our Storage offering has been resolved. Start time : 25/05/2026 07:30 UTC End time : 25/05/2026 12:50 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 →

Minor May 22, 2026

[GRA/RBX/DE][Storage and Backups] - Object Storage Incident Notification

Detected by Pingoru
May 22, 2026, 03:04 PM UTC
Resolved
Jun 15, 2026, 01:48 PM UTC
Duration
23d 22h
Affected: GRADERBX
Timeline · 4 updates
  1. investigating May 22, 2026, 03:04 PM UTC

    We are currently investigating an incident affecting our Storage and Backups offering, which is causing temporary functionality issue in GRA/RBX/DE regions Here are some supplementary details : Start time : 13/05/2026 00:00 UTC Impacted Service(s) : Delay in lifecycle rules execution for regions GRA, RBX and DE Customers Impact : Some customers might face delay in lifecycle rules execution in specified regions. 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 May 25, 2026, 08:58 AM UTC

    We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The incident is still under investigation by our technical teams, who are working to determine its cause and implement a fix. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  3. identified Jun 11, 2026, 10:05 AM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Storage and Backups offering in GRA/RBX/DE regions. Here are some supplementary details : Start time : 13/05/2026 00:00 UTC Impacted Service(s) : Delay in lifecycle rules execution for regions GRA, RBX and DE. Customers Impact : Some customers might face delay in lifecycle rules execution in specified regions. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : Processing has been improved and most of the backlog has been cleared. Some workloads with a very high number of pending events may still experience delays while we continue optimizing processing. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  4. resolved Jun 15, 2026, 01:48 PM UTC

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

Read the full incident report →

Major May 21, 2026

[BHS5][Compute - Instance] - Instances incident notification

Detected by Pingoru
May 21, 2026, 11:07 PM UTC
Resolved
May 21, 2026, 11:22 PM UTC
Duration
14m
Affected: BHS5
Timeline · 2 updates
  1. identified May 21, 2026, 11:07 PM UTC

    We are currently experiencing an incident affecting our Compute - Instance offering in the BHS5 Region The root cause has been identified. Please find the details of this incident below : Start time : 21/05/2026 22:45 UTC Impacted Service(s) : Some instances in the BHS5 region are unreachable. Customers Impact : Customers are temporarily unable to access and use their instances located on the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : Our teams are actively working to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  2. resolved May 21, 2026, 11:22 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 21/05/2026 22:45 UTC End time : 21/05/2026 23:14 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 May 20, 2026

[GLOBAL][AI & Machine Learning] - AI Endpoint incident notification

Detected by Pingoru
May 20, 2026, 09:34 AM UTC
Resolved
May 20, 2026, 03:39 PM UTC
Duration
6h 5m
Affected: AI & Machine Learning || AI Endpoint
Timeline · 2 updates
  1. investigating May 20, 2026, 09:34 AM UTC

    We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary availability issue on AI Endpoint . Here are some supplementary details : Start time : 19/05/2026 09:00 UTC Impacted Service(s) : The gpt-oss-120b model on AI Endpoints may have some performance issue. Customers Impact : Customers may have temporarily difficulties to use the gpt-oss-120b model on AI Endpoints. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  2. resolved May 20, 2026, 03:39 PM UTC

    We are pleased to inform you that the incident affecting our AI & Machine Learning offering for gpt-oss-120b model has been resolved. Start time : 19/05/2026 09:00 UTC End time : 20/05/2026 12:20 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 May 20, 2026

[SBG5][Compute - Instance] - Public Cloud Incident Notification

Detected by Pingoru
May 20, 2026, 09:21 AM UTC
Resolved
May 20, 2026, 10:36 AM UTC
Duration
1h 15m
Affected: GRA3SBG5
Timeline · 3 updates
  1. identified May 20, 2026, 09:21 AM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer in GRA3 region. Here are some supplementary details : Start time : 20/05/2026 08:54 UTC Impacted Service(s) : Some instances in the GRA3 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 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 May 20, 2026, 09:49 AM UTC

    Please find below an update on the situation: Update : Some Instances are once again reachable. Our team remains committed to restoring the missing instances as quickly as possible. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved May 20, 2026, 10:36 AM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 20/05/2026 08:54 UTC End time : 20/05/2026 10:16 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 May 19, 2026

[GRA5][Storage] - Block Storage incident notification

Detected by Pingoru
May 19, 2026, 05:01 AM UTC
Resolved
May 19, 2026, 06:09 AM UTC
Duration
1h 7m
Affected: GRA5
Timeline · 2 updates
  1. investigating May 19, 2026, 05:01 AM UTC

    We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the region GRA5. Here are some supplementary details : Start time : 19/05/2026 04:46 UTC Impacted Service(s) : The block storage service is temporarily unavailable for some customers in GRA5 region. Customers Impact : Some customers are temporarily unable to access and use their block Storage located in GRA5 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 May 19, 2026, 06:09 AM UTC

    We are pleased to inform you that the incident affecting our Block Storage offering in GRA5 region has been resolved. Start time : 19/05/2026 04:46 UTC End time : 19/05/2026 05: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.

Read the full incident report →

Major May 13, 2026

[GRA][Compute - Instance] - Incident Notification

Detected by Pingoru
May 13, 2026, 09:44 AM UTC
Resolved
May 13, 2026, 11:43 AM UTC
Duration
1h 59m
Affected: GRA5GRA7GRA9GRA11
Timeline · 2 updates
  1. investigating May 13, 2026, 09:44 AM UTC

    We are currently experiencing an event affecting our Compute - Instance offer GRA regions Start time : 13/05/2026 09:03 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. resolved May 13, 2026, 11:43 AM UTC

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