OVH.com logo
OVHcloud Public Cloud Status

Current status
Legend
  • Operational
  • Degraded performance
  • Partial Outage
  • Major Outage
  • Under maintenance
[GLOBAL][Databases] - PostgreSQL 18 incident notification
Update - Our provider is still working on resolving the issue affecting our PostgreSQL offering.
To avoid issues with geospatial features, we still strongly recommend postponing any upgrade to PostgreSQL version 18 and continuing to use PostgreSQL version 17, which remains compatible with PostGIS.

For any questions, please contact your usual point of contact or reach out to our support team.

We will keep you updated on the progress and resolution.
Apr 09, 2026 - 14:08 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.

Here are some supplementary details :
Start time : 16/03/2026 08:00 UTC
Impacted Service(s) : Customers may experience issues when upgrading to PostgreSQL version 18, as the PostGIS extension is currently not functional on this version, potentially preventing the use of geospatial features.
As a precaution, we strongly recommend postponing any upgrade to PostgreSQL version 18 and continuing to use PostgreSQL version 17, which remains compatible with PostGIS.
Root Cause : This incident is caused by our provider.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

If you have any questions, please contact your usual point of contact or reach out to our support team.

We will keep you updated on the progress and resolution.
Mar 30, 2026 - 12:36 UTC

About This Site

Welcome to the Public Cloud status page for real-time information on system performance and availability.

Uptime over the past 90 days. View historical uptime.
AI & Machine Learning || AI Dashboard Operational
AI & Machine Learning || AI Deploy Operational
BHS Operational
GRA Operational
AI & Machine Learning || AI Endpoint Operational
AI & Machine Learning || AI Notebooks Operational
BHS Operational
GRA Operational
AI & Machine Learning || AI Training Operational
BHS Operational
GRA Operational
Compute - Instance || BHS Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
Compute - Instance || ERI Operational
UK1 Operational
Compute - Instance || EU-SOUTH-MIL Operational
EU-SOUTH-MIL-A Operational
EU-SOUTH-MIL-B Operational
EU-SOUTH-MIL-C Operational
Compute - Instance || EU-WEST-PAR Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
Compute - Instance || GRA Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
Compute - Instance || India Operational
AP-SOUTH-MUM-1 Operational
Compute - Instance || LIM Operational
DE1 Operational
Compute - Instance || RBX Operational
RBX-A Operational
Compute - Instance || SGP Operational
SGP1 Operational
SGP2 Operational
Compute - Instance || SBG Operational
SBG5 Operational
SBG7 Operational
Compute - Instance || SYD Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
Compute - Instance || USA Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
Compute - Instance || WAW Operational
WAW1 Operational
Containers & Orchestration || Load Balancer Operational
AP-SOUTH-MUM Operational
BHS5 Operational
DE1 Operational
EU-WEST-PAR Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
RBX-A Operational
SBG5 Operational
SGP1 Operational
SYD1 Operational
WAW1 Operational
UK1 Operational
US-EAST-VA Operational
US-WEST-OR Operational
Containers & Orchestration || Managed Kubernetes Service Operational
AP-SOUTH-MUM Operational
BHS5 Operational
EU-WEST-LIM Operational
EU-SOUTH-MIL Operational
EU-WEST-PAR Operational
RBX Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
SBG5 Operational
SGP1 Operational
SYD1 Operational
WAW1 Operational
UK1 Operational
US-EAST-VA Operational
US-WEST-OR Operational
Containers & Orchestration || Managed Private Registry Operational
AP-SOUTH-MUM Operational
BHS Operational
DE Operational
EU-SOUTH-MIL Operational
EU-WEST-PAR Operational
GRA Operational
VA Operational
Containers & Orchestration || Managed Rancher Service Operational
Containers & Orchestration || Workflow Management Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
RBX-A Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SGP2 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
WAW1 Operational
WAW2 Operational
US-EAST-VA Operational
US-WEST-OR Operational
AP-SOUTH-MUM Operational
Databases || MongoDB Operational
90 days ago
99.91 % uptime
Today
BHS Operational
DE Operational
GRA Operational
EU-WEST-PAR Operational
SBG Operational
SGP Operational
UK Operational
WAW Operational
EU-SOUTH-MIL Operational
90 days ago
99.91 % uptime
Today
RBX Operational
AP-SOUTH-MUM Operational
US-EAST-VA Operational
US-WEST-OR Operational
Databases || MySQL Operational
BHS Operational
DE Operational
GRA Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
EU-WEST-PAR Operational
RBX Operational
SBG Operational
SGP Operational
US-EAST-VA Operational
UK Operational
US-WEST-OR Operational
WAW Operational
Databases || PostgreSQL Operational
BHS Operational
DE Operational
GRA Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
EU-WEST-PAR Operational
RBX Operational
SBG Operational
SGP Operational
UK Operational
US-EAST-VA Operational
US-WEST-OR Operational
WAW Operational
Databases || Valkey Operational
BHS Operational
DE Operational
GRA Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
EU-WEST-PAR Operational
RBX Operational
SBG Operational
SGP Operational
US-EAST-VA Operational
UK Operational
US-WEST-OR Operational
WAW Operational
Data & Analytics || ClickHouse Operational
EU-WEST-PAR Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
Data & Analytics || Data Platform Operational
Data & Analytics || Dashboards Operational
BHS Operational
DE Operational
GRA Operational
EU-WEST-PAR Operational
SBG Operational
SGP Operational
UK Operational
WAW Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
RBX Operational
US-EAST-VA Operational
US-WEST-OR Operational
Data & Analytics || Kafka Operational
BHS Operational
DE Operational
GRA Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
EU-WEST-PAR Operational
RBX Operational
SBG Operational
SGP Operational
UK Operational
US-EAST-VA Operational
US-WEST-OR Operational
WAW Operational
Data & Analytics || Kafka Connect Operational
BHS Operational
DE Operational
GRA Operational
EU-WEST-PAR Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
RBX Operational
SBG Operational
SGP Operational
UK Operational
US-EAST-VA Operational
US-WEST-OR Operational
WAW Operational
Data & Analytics || Kafka MirrorMaker Operational
BHS Operational
DE Operational
GRA Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
EU-WEST-PAR Operational
RBX Operational
SBG Operational
SGP Operational
UK Operational
WAW Operational
US-EAST-VA Operational
US-WEST-OR Operational
Data & Analytics || OpenSearch Operational
BHS Operational
DE Operational
GRA Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
EU-WEST-PAR Operational
RBX Operational
SBG Operational
SGP Operational
US-EAST-VA Operational
UK Operational
US-WEST-OR Operational
WAW Operational
Identity, Security & Operations || Authentication Operational
Identity, Security & Operations || Barbican Operational
AP-SOUTH-MUM Operational
AP-SOUTHEAST-SYD-2 Operational
BHS5 Operational
DE1 Operational
EU-SOUTH-MIL Operational
EU-WEST-PAR Operational
GRA9 Operational
RBX-A Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
UK1 Operational
US-WEST-OR Operational
US-EAST-VA Operational
WAW1 Operational
Management || Horizon Operational
Identity, Security & Operations || Key Management Service Operational
AP-SOUTHEAST-SGP Operational
AP-SOUTHEAST-SYD Operational
CA-EAST-TOR Operational
CA-EAST-BHS Operational
EU-CENTRAL-WAW Operational
EU-SOUTH-MIL Operational
EU-WEST-ERI Operational
EU-WEST-GRA Operational
EU-WEST-LIM Operational
EU-WEST-PAR Operational
EU-WEST-RBX Operational
EU-WEST-SBG Operational
Identity, Security & Operations || Logs Data Platform Operational
BHS Operational
GRA Operational
LocalZones || AF-CENTRAL Operational
AF-CENTRAL-LZ-ABJ Operational
LocalZones || AF-NORTH Operational
AF-NORTH-LZ-RBA Operational
LocalZones || AP-SOUTH-MUM Operational
LocalZones || EU-CENTRAL Operational
EU-CENTRAL-LZ-BUH Operational
EU-CENTRAL-LZ-PRG Operational
EU-CENTRAL-LZ-SOF Operational
LocalZones || EU-NORTH Operational
EU-NORTH-LZ-CPH Operational
EU-NORTH-LZ-HEL Operational
EU-NORTH-LZ-OSL Operational
EU-NORTH-LZ-STO Operational
LocalZones || EU-SOUTH Operational
EU-SOUTH-LZ-LIS Operational
EU-SOUTH-LZ-MAD Operational
EU-SOUTH-LZ-MIL Operational
LocalZones || EU-WEST Operational
EU-WEST-LZ-AMS Operational
EU-WEST-LZ-BRU Operational
EU-WEST-LZ-DLN Operational
EU-WEST-LZ-LUX Operational
EU-WEST-LZ-MNC Operational
EU-WEST-LZ-MRS Operational
EU-WEST-LZ-VIE Operational
EU-WEST-LZ-ZRH Operational
LocalZones || US-CENTRAL Operational
US-CENTRAL-LZ-SLC Operational
US-CENTRAL-LZ-STL Operational
LocalZones || US-EAST Operational
US-EAST-LZ-ATL Operational
US-EAST-LZ-BOS Operational
US-EAST-LZ-CHI Operational
US-EAST-LZ-DAL Operational
US-EAST-LZ-MIA Operational
US-EAST-LZ-NYC Operational
LocalZones || US-WEST Operational
US-WEST-LZ-DEN Operational
US-WEST-LZ-LAX Operational
US-WEST-LZ-PAO Operational
US-WEST-LZ-PHX Operational
US-WEST-LZ-SEA Operational
Network || Floating IP Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
AP-SOUTH-MUM-1 Operational
RBX-A Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
WAW1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
EU-SOUTH-MIL-A Operational
EU-SOUTH-MIL-B Operational
EU-SOUTH-MIL-C Operational
Network || Gateway Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
WAW1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
AP-SOUTH-MUM-1 Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
RBX-A Operational
EU-SOUTH-MIL-A Operational
EU-SOUTH-MIL-B Operational
EU-SOUTH-MIL-C Operational
Network || Load Balancer Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
WAW1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
AP-SOUTH-MUM-1 Operational
RBX-A Operational
EU-SOUTH-MIL-A Operational
EU-SOUTH-MIL-B Operational
EU-SOUTH-MIL-C Operational
Network || Private network (vRack) Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
RBX-A Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SGP2 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
WAW1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
AP-SOUTH-MUM-1 Operational
RBX-A Operational
EU-SOUTH-MIL-A Operational
EU-SOUTH-MIL-B Operational
EU-SOUTH-MIL-C Operational
Network || Public network Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
RBX-A Operational
SBG1 Operational
SBG3 Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SGP2 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
WAW1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
AP-SOUTH-MUM-1 Operational
RBX-A Operational
EU-SOUTH-MIL-A Operational
EU-SOUTH-MIL-B Operational
EU-SOUTH-MIL-C Operational
Quantum || Emulators Operational
BHS Operational
GRA Operational
Quantum || QPUs Operational
BHS Operational
GRA Operational
Storage || Block storage Operational
AP-SOUTHEAST-SYD-2 Operational
AP-SOUTH-MUM-1 Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
EU-SOUTH-MIL-A Operational
EU-SOUTH-MIL-B Operational
EU-SOUTH-MIL-C Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA6 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
RBX-A Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
UK1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
WAW1 Operational
YNM1 Operational
Storage || Cloud Archive Operational
DE Operational
GRA Operational
UK Operational
WAW Operational
BHS Operational
SYD Operational
SGP Operational
US-EAST-VA Operational
US-WEST-OR Operational
Storage || Cold Archive Operational
RBX-ARCHIVE Operational
Storage || Instance Backup Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
WAW1 Operational
AP-SOUTH-MUM-1 Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
RBX-A Operational
Storage || Object storage Operational
BHS Operational
GRA Operational
DE Operational
RBX Operational
SBG Operational
SGP Operational
SYD Operational
UK Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
WAW Operational
YYZ Operational
LIM Operational
AP-SOUTH-MUM-1 Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
YNM1 Operational
EU-SOUTH-MIL-B Operational
EU-SOUTH-MIL-A Operational
EU-SOUTH-MIL-C Operational
Storage || Volume Backup Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
WAW1 Operational
AP-SOUTH-MUM-1 Operational
RBX-A Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
EU-SOUTH-MIL Operational
Storage || Volume Snapshot (Ceph) Operational
DE1 Operational
GRA1 Operational
GRA2 Operational
GRA3 Operational
GRA5 Operational
GRA6 Operational
GRA4 Operational
GRA7 Operational
GRA8 Operational
GRA9 Operational
GRA11 Operational
RBX-A Operational
SBG5 Operational
SBG6 Operational
SBG7 Operational
SBG8 Operational
SGP1 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
UK2 Operational
WAW1 Operational
WAW2 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
AP-SOUTH-MUM-1 Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
EU-SOUTH-MIL Operational
RBX-A Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

[Global][Data & Analytics ] - Data Platform maintenance notification May 18, 2026 12:00-15:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our Data Platform offer.

Here are the details of the maintenance:
Start time : 18/05/2026 12:00 UTC
End time : 18/05/2026 15:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Data Platform infrastructure.

Thank you for your understanding.
Posted on May 05, 2026 - 21:41 UTC

[Containers & Orchestration] - Managed Rancher Service maintenance notification May 20, 2026 08:30-16:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our Data Platform offer.

Start time : 20/05/2026 08:30 UTC
End time : 20/05/2026 16:00 UTC
Service impact : None
Service improvement : We are currently performing an infrastructure maintenance and upgrade operation to ensure continued reliability and long-term platform support.The changes are being deployed progressively and are expected to be completed without service interruption.

Thank you for your understanding.
Posted on May 13, 2026 - 14:59 UTC

[GRA9/GRA11][Public Cloud] - Compute Instance (A10 Flavor) Maintenance Notification May 25, 2026 07:00-11:00 UTC

As part of our continuous improvement plan, we will be carrying out a maintenance on our electrical infrastructure in GRA9/GRA11 regions.

Start time : 25/05/2026 07:00 UTC
End time : 25/05/2026 11:00 UTC
Service impact : Instances will be unavailable during the maintenance. The only flavor impacted is A10.
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our electrical infrastructure.

Thank you for your understanding.
Posted on May 11, 2026 - 15:36 UTC

[GLOBAL][Containers & Orchestration] - End of life Kubernetes 1.30 notification May 26, 2026 07:00 - May 28, 2026 16:00 UTC

Update - We are sorry to inform you that this maintenance is postponed.

As part of our continuous improvement plan, maintenance is scheduled on our Managed Kubernetes Service.

Start time : 26/05/2026 07:00 UTC
End time : 28/05/2026 16:00 UTC
Service impact : Customers have to anticipate this maintenance in order to adapt to the new Kubernetes version.
Service improvement : As part of our continuous improvement policy, customers using Kubernetes version 1.30 will be migrated to version 1.31.

Thank you for your understanding.
Apr 15, 2026 - 14:18 UTC
Scheduled - As part of our continuous improvement plan, maintenance is scheduled on our Managed Kubernetes Service.

Start time : 26/05/2026 07:00 UTC
End time : 28/05/2026 16:00 UTC
Service impact : Customers have to anticipate this maintenance in order to adapt to the new Kubernetes version.
Service improvement : As part of our continuous improvement policy, customers using Kubernetes version 1.30 will be migrated to version 1.31.

Thank you for your understanding.
Mar 18, 2026 - 21:56 UTC

[RBX/SBG][Containers & Orchestration] - Managed Rancher Service maintenance notification Jun 8, 2026 07:30-16:00 UTC

As part of our continuous improvement plan, maintenance is scheduled on our Containers & Orchestration offer.

This may temporarily affect availability.

Start time : 08/06/2026 07:30 UTC
End time : 08/06/2026 16:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we need to upgrade Ranchers in version 2.11 to version 2.12. You can already manage the upgrade by yourself through OVHcloud Control panel or API.
The Rancher compatibility matrix with downstream clusters will change, indeed K8S version 1.30 will no longer be officially supported.
For more information regarding Managed Rancher Service supported versions and lifecycle policy, you can visit this page: KB0064608

Thank you for your understanding.
Posted on Apr 22, 2026 - 17:38 UTC
May 14, 2026

No incidents reported today.

May 13, 2026
[GRA][Compute - Instance] - Incident Notification
Resolved - 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 :A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
May 13, 11:43 UTC
Investigating - 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.
May 13, 09:44 UTC
May 12, 2026

No incidents reported.

May 11, 2026
[US-EAST-VA-1][Public Cloud] - Managed Kubernetes Service Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Managed Kubernetes Service offering has been resolved.

Start time : 11/05/2026 15:37 UTC
End time : 11/05/2026 18:41 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
May 11, 18:54 UTC
Investigating - We are currently investigating an incident affecting our Managed Kubernetes Service offering, which is causing temporary availability issue in the US-EAST-VA-1 region.

Here are some supplementary details :

Start time : 11/05/2026 15:37 UTC
Impacted Service(s) : Some instances in the US-EAST-VA-1 region are unreachable.
Customers Impact : Management and creation of new Managed Kubernetes Service clusters is temporarily unavailable.
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.
May 11, 15:52 UTC
[EU-WEST-PAR][Containers & Orchestration] - Managed Kubernetes Service update
Completed - The scheduled maintenance has been completed.
May 11, 15:26 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 11, 09:00 UTC
Update - We will be undergoing scheduled maintenance during this time.
May 11, 08:48 UTC
Scheduled - As part of our continuous improvement plan, maintenance is scheduled on our Managed Kubernetes Service offer.

Start time : 11/05/2026 09:00 UTC
End time : 11/05/2026 15:30 UTC
Service impact : None
Service improvement : Following our continuous improvement policy, we are rolling out an update to all cluster in a supported versions (1.34, 1.35) with an update policy of ALWAYS_UPDATE to the latest patch version.

Thank you for your understanding.
May 11, 08:41 UTC
[GRA1][Public Cloud] - Compute - Instance Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering in GRA1 region has been resolved.

Start time : 11/05/2026 06:26 UTC
End time : 11/05/2026 11:45 UTC
Root Cause : A service disruption occurred due to an unexpected infrastructure failure.

We apologize for any inconvenience caused and appreciate your understanding.
May 11, 12:18 UTC
Identified - We have determined the origin of the issue affecting our Compute - Instance offer in GRA1 regions.

Here are some supplementary details :

Start time : 11/05/2026 06:26 UTC
Impacted Service(s) : Some instances in GRA1 regions are unreachable.
Customers Impact : Customers are temporarily unable to access instances in 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.
May 11, 06:40 UTC
[GRA2][Public Cloud] - Compute - Instance Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering in GRA2 has been resolved.

Start time : 11/05/2026 07:05 UTC
End time : 11/05/2026 11:45 UTC
Root Cause : A service disruption occurred due to an unexpected infrastructure failure.

We apologize for any inconvenience caused and appreciate your understanding.
May 11, 12:17 UTC
Identified - We have determined the origin of the issue affecting our Compute - Instance offer in GRA2 regions.

Here are some supplementary details :

Start time : 11/05/2026 07:05 UTC
Impacted Service(s) : Some instances in GRA2 regions are unreachable.
Customers Impact : Customers are temporarily unable to access instances in 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.
May 11, 07:16 UTC
May 10, 2026

No incidents reported.

May 9, 2026

No incidents reported.

May 8, 2026

No incidents reported.

May 7, 2026
[Global][Containers & Orchestration] - Managed Kubernetes Service update
Completed - The scheduled maintenance has been completed.
May 7, 09:31 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 5, 06:00 UTC
Scheduled - As part of our continuous improvement plan, maintenance is scheduled on our Managed Kubernetes Service offer.

Start time : 05/05/2026 06:00 UTC
End time : 07/05/2026 10:00 UTC
Service impact : None
Service improvement : Following our continuous improvement policy, we are rolling out an update to all cluster in a supported versions (1.33, 1.34, 1.35) with an update policy of ALWAYS_UPDATE to the latest patch version.

Thank you for your understanding.
May 4, 20:28 UTC
[WAW1][Compute - Instance] - Instance incident notification
Resolved - We would like to inform you that an incident occurred on our Compute - Instance offering in WAW1.
This incident has now been resolved.

Please find the details of this incident below :

Start time : 07/05/2026 07:42 UTC
End time : 07/05/2026 07:50 UTC
Impacted Service(s) : Some instances in the WAW1 region were unreachable.
Customers Impact : Customers were 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.

We apologize for any inconvenience caused and appreciate your understanding.
May 7, 07:55 UTC
May 6, 2026
[RBX-A/GRA3/GRA5/GRA7/GRA9/GRA11/SBG5][Storage] - Block storage maintenance notification
Completed - The scheduled maintenance has been completed.
May 6, 17:13 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 4, 09:00 UTC
Scheduled - As part of our continuous improvement plan, maintenance is scheduled on our Block Storage offer in the RBX-A/GRA3/GRA5/GRA7/GRA9/GRA11/SBG5 regions.

Start time : 04/05/2026 09:00 UTC
End time : 06/05/2026 17:00 UTC
Service impact : During the maintenance window, customers may experience a temporary performance degradation.
Service improvement : As part of our continuous improvement policy and to improve service quality, we will be doing a software upgrade on our Block Storage servers.

Thank you for your understanding.
Apr 30, 20:49 UTC
May 5, 2026
[Global][Data & Analytics ] - Data Platform Maintenance Notification
Completed - The scheduled maintenance has been completed.
May 5, 12:37 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 5, 12:00 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our Data Platform offer.

Here are the details of the maintenance:
Start time : 05/05/2026 12:00 UTC
End time : 05/05/2026 14:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Data Platform infrastructure.

Thank you for your understanding.
Apr 30, 12:39 UTC
May 4, 2026
[GRA1/GRA3/GRA5/GRA9][Public Cloud] - Compute - Instance Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Public Cloud offering has been resolved.

Start time : 04/05/2026 06:31 UTC
End time : 04/05/2026 15:13 UTC
Root Cause : A service disruption occurred due to an unexpected infrastructure failure.

We apologize for any inconvenience caused and appreciate your understanding.
May 4, 15:15 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : Our technical team continues to work on 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.
May 4, 10:46 UTC
Update - We have determined the origin of the issue affecting our Compute - Instance offer in GRA1/GRA3/GRA5/GRA9 regions.

Here are some supplementary details :

Start time : 04/05/2026 06:31 UTC
Impacted Service(s) : Some instances in GRA1/GRA3/GRA5/GRA9 regions are unreachable.
Customers Impact : Customers are temporarily unable to access instances in 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.
May 4, 07:32 UTC
Identified - We have determined the origin of the issue affecting our Compute - Instance offer in GRA1/GRA3/GRA5/GRA9 regions.

Here are some supplementary details :

Start time : 04/05/2026 06:31 UTC
Impacted Service(s) : Some instances in GRA1/GRA3/GRA5/GRA9 regions are unreachable.
Customers Impact : Customers are temporarily unable to access instances in 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.
May 4, 07:31 UTC
Investigating - We are currently experiencing an event affecting our Compute - Instance offer.

Start time : 04/05/2026 06:31 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.
May 4, 06:58 UTC
May 3, 2026
[LIM1][Compute - Instance] - Cloud Compute Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering in LIM1 has been resolved.

Start time : 02/05/2026 12:18 UTC
End time : 03/05/2026 19:58 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
May 3, 20:13 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : The remaining instances are still being worked on by our team.
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.
May 3, 03:08 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : Most instances are now operational again.
Ongoing Actions : Our team is working to fix the last remaining instances.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
May 2, 16:43 UTC
Update - We are continuing to work on a fix for this issue.
May 2, 16:24 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific region.

Here are some supplementary details :

Start time : 02/05/2026 12:18 UTC
Impacted Service(s) : Some instances in the LIM1 region are unreachable.
Customers Impact : Customers are temporarily unable to access instances located on the specified regions and Redis Database.
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.
May 2, 12:25 UTC
May 2, 2026
May 1, 2026
[ERI1][Compute - Instance] - Cloud Compute Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Dedicated Servers has been resolved.

Start time : 01/05/2026 07:19 UTC
End time : 01/05/2026 08:20 UTC
Root Cause : This incident was caused by a network equipment issue.

We apologize for any inconvenience caused and appreciate your understanding.
May 1, 08:34 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific region.

Here are some supplementary details :

Start time : 01/05/2026 07:19 UTC
Impacted Service(s) : Some instances in the ERI1 region are unreachable.
Customers Impact : 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.
May 1, 07:29 UTC
Apr 30, 2026
[FR][Data & Analytics] - Data Platform Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Data & Analytics offer has been resolved.

Start time : 30/04/2026 08:18 UTC
End time : 30/04/2026 19:14 UTC
Root Cause : This incident was caused by a software issue.

We apologize for any inconvenience caused and appreciate your understanding.
Apr 30, 19:24 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offering, which is causing temporary functionality issue in the FR region.

Here are some supplementary details :

Start time : 30/04/2026 08:18 UTC
Impacted Service(s) : Builds of APP or API are temporarily unavailable.
Customers Impact : Customers are temporarily unable to build API/APP.
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.
Apr 30, 13:06 UTC
[GLOBAL][Containers & Orchestration] - Managed Kubernetes Service event notification
Resolved - We are pleased to inform you that our teams released new versions to resolve the security event that affected our Managed Kubernetes Service.

Start time : 22/04/2026 08:15 UTC
End time : 30/04/2026 15:30 UTC
Root Cause : This incident was caused by a software issue.

Patched MKS versions are now available. We recommend updating your clusters as soon as possible, especially those running multi-tenant workloads.
Patched versions — Free plan

Kubernetes 1.30 (end of support): patch version 1.30.14-3
Kubernetes 1.31 (end of support): patch version 1.31.13-2
Kubernetes 1.32 (end of support): patch version 1.32.13-2
Kubernetes 1.33 (supported): patch version 1.33.10-2
Kubernetes 1.34 (supported): patch version 1.34.2-2
Kubernetes 1.35 (supported): patch version 1.35.2-2

Patched versions — Standard plan

Kubernetes 1.30 (end of support): patch version 1.30.14-12
Kubernetes 1.31 (end of support): patch version 1.31.13-9
Kubernetes 1.32 (end of support): patch version 1.32.13-3
Kubernetes 1.33 (supported): patch version 1.33.10-3
Kubernetes 1.34 (supported): patch version 1.34.6-3
Kubernetes 1.35 (supported): patch version 1.35.2-2

What customers need to do
All customers can apply the patch manually right now, regardless of their cluster's Kubernetes version or security update policy. We strongly recommend doing so as soon as possible.

Via the OVHcloud Control Panel: Public Cloud > Managed Kubernetes Service > Your cluster > Apply Patch
Via the OVHcloud API: POST /cloud/project/{serviceName}/kube/{kubeId}/update with the following request body:
{
"strategy": "LATEST_PATCH"
}

Automatic rollout
For clusters running a supported Kubernetes version (1.33, 1.34, 1.35) with the ALWAYS_UPDATE or MINIMAL_DOWNTIME security policy, OVHcloud will roll out the patch automatically over the coming days.
Clusters running end-of-support Kubernetes versions (1.30, 1.31, 1.32) will not be patched automatically by OVHcloud, even with an automatic security update policy. Customers running these versions must apply the patch manually using the versions listed above. We strongly recommend planning an upgrade to a supported Kubernetes minor version as soon as possible.
Customers using the NEVER_UPDATE policy must also apply the update manually. Given the severity of this CVE, OVHcloud may force-apply the security update if clusters remain unpatched after a notice period.
Apr 30, 16:16 UTC
Identified - We are currently experiencing an ongoing security event affecting our Managed Kubernetes Service. The source of the issue has been identified.

Start time : 22/04/2026 08:15 UTC
Impacted service(s) : Managed Kubernetes Service (MKS) worker nodes.
Customer impact : A recently disclosed security vulnerability may allow a user within a container to gain elevated access on the underlying node.
This issue is limited to individual clusters and does not impact other customers or the managed control plane.
Customers running shared or multi-tenant workloads within the same cluster should consider this issue with higher priority.
Other OVHcloud managed services (MPR, MRS) are patched transparently by OVHcloud, no customer action required.
Root Cause : This incident is caused by a software issue.
Workaround : A temporary mitigation is available to reduce the risk while we prepare a permanent fix.
Instructions are available in our dedicated blog post:
https://blog.ovhcloud.com/copy-fail-cve-2026-31431-how-to-rapidly-protect-ovhcloud-mks-clusters-from-the-linux-kernel-zero-day
Please note that applying this mitigation is optional and remains under your responsibility.
If the vulnerability has already been exploited on your cluster, this mitigation will not remediate any pre-existing compromise
Ongoing actions : Our teams are actively working on a permanent fix.
Updated versions are expected to be available later today.

We will share further details and update instructions as soon as they are ready.
We will keep you informed of any progress.

Thank you for your understanding.
Apr 30, 15:27 UTC
[EU][Network] - API Network incident notification
Resolved - We had an incident on our Public Cloud Network API offer in EU which has now been resolved.

Here are some supplementary details :

Start time : 30/04/2026 14:42 UTC
End time : 30/04/2026 14:57 UTC
Impacted Service(s) : The API for Public Cloud was temporarily unavailable.
Customers Impact : Customers were temporarily unable to create, start, manage their Public Cloud instances.
Root Cause : This incident was caused by a software issue.

We thank you for your understanding and patience throughout this incident.
Apr 30, 15:36 UTC
[Global][Data & Analytics ] - Data Platform maintenance notification
Completed - The current maintenance has been canceled and she will be rescheduled later.
Apr 30, 08:57 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our Data Platform offer.

Here are the details of the maintenance:
Start time : 04/05/2026 12:00 UTC
End time : 04/05/2026 15:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Data Platform infrastructure.

Thank you for your understanding.
Apr 14, 14:26 UTC
← Incident History Powered by Atlassian Statuspage