[GLOBAL][Public Cloud] - AI & Machine Learning maintenance notification
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 22, 2026 - 14:50 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our AI & Machine Learning.

Start time : 22/07/2026 13:00 UTC
End time : 31/07/2026 13:30 UTC
Service impact : Customer may have timeout on their nodes.
Service improvement : As part of our continuous improvement policy of our services, we will upgrade our public cloud nodes underlying OS from Ubuntu.

Thank you for your understanding.
Jul 22, 2026 14:50 - Jul 31, 2026 13:30 UTC
[GLOBAL][Databases] - PostgreSQL 18 and PostGIS Compatibility Issue
Monitoring - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : PostGIS support for PostgreSQL 18 was introduced in a newer PostGIS version. However, an identified defect carries a risk of data corruption for geospatial data, so we have chosen not to enable it on our offer yet. We are waiting for a PostGIS release that fixes this issue before allowing PostGIS to be used on PostgreSQL 18.
As a reminder, this only affects customers using the PostGIS extension. PostgreSQL instances that do not use PostGIS are not impacted.
In the meantime, we still strongly recommend that PostGIS users postpone any upgrade to PostgreSQL 18 and remain on PostgreSQL 17, which is fully compatible with PostGIS.
Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 08, 2026 - 14:22 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : PostGIS support for PostgreSQL 18 was introduced in a newer PostGIS version. However, an identified defect carries a risk of data corruption for geospatial data, so we have chosen not to enable it on our offer yet. We are waiting for a PostGIS release that fixes this issue before allowing PostGIS to be used on PostgreSQL 18.
As a reminder, this only affects customers using the PostGIS extension. PostgreSQL instances that do not use PostGIS are not impacted.
In the meantime, we still strongly recommend that PostGIS users postpone any upgrade to PostgreSQL 18 and remain on PostgreSQL 17, which is fully compatible with PostGIS.
Ongoing Actions : We are closely monitoring the situation while the PostGIS team works on a resolution.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 11, 2026 - 08:45 UTC
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 and have determined origin of the issue to PostGIS plugin, affecting our PostgreSQL offer when using this specific plugin in version 3.5 and PG18.

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 PostGIS extension current version 3.5.
Ongoing Actions : The PostGIS team needs to fix this bug and release a new version of the extension (v3.6). In the meantime, our services remain fully functional without PostGIS.

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 Under Maintenance
BHS Under Maintenance
GRA Under Maintenance
Compute - Instance || BHS Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
BHS7 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
GRA4 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
SBG3 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
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
DE1 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
100.0 % 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
100.0 % 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 || File storage Operational
AP-SOUTH-MUM-1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
EU-SOUTH-MIL Operational
EU-WEST-PAR Operational
GRA1 Operational
GRA3 Operational
GRA5 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
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 Aug 3, 2026 12:00-15:00 UTC

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

Start time : 03/08/2026 12:00 UTC
End time : 03/08/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 Jul 15, 2026 - 23:39 UTC

[BHS3/5][Storage] - File storage maintenance notification Aug 4, 2026 07:00-14:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our file storage infrastructure.

Start time : 04/08/2026 07:00 UTC
End time : 04/08/2026 14:00 UTC
Service impact : None.
Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our file storage infrastructure.

Thank you for your understanding.
Posted on Jul 23, 2026 - 15:19 UTC

[BHS3/5][Storage] - File storage maintenance notification Aug 4, 2026 12:00-18:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our file storage infrastructure.

Start time : 04/08/2026 12:00 UTC
End time : 04/08/2026 18:00 UTC
Service impact : None.
Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our file storage infrastructure.

Thank you for your understanding.
Posted on Jul 23, 2026 - 15:20 UTC

[EU/CA][Containers & Orchestration] - Managed Kubernetes Service maintenance notification Aug 4, 2026 16:00-19:00 UTC

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

Start time : 04/08/2026 16:00 UTC
End time : 04/08/2026 19:00 UTC
Service impact : During the maintenance window, customers will temporarily be unable to manage their MKS clusters. However, the MKS clusters themselves, as well as the workloads running on them, will remain available.
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our MKS infrastructure.

Thank you for your understanding.
Posted on Jul 28, 2026 - 14:26 UTC

[BHS3/5][Storage] - File storage maintenance notification Aug 5, 2026 07:00-14:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our file storage infrastructure.

Start time : 05/08/2026 07:00 UTC
End time : 05/08/2026 14:00 UTC
Service impact : None.
Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our file storage infrastructure.

Thank you for your understanding.
Posted on Jul 23, 2026 - 15:25 UTC

[BHS3/5][Storage] - File storage maintenance notification Aug 5, 2026 12:00-18:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our file storage infrastructure.

Start time : 05/08/2026 12:00 UTC
End time : 05/08/2026 18:00 UTC
Service impact : None.
Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our file storage infrastructure.

Thank you for your understanding.
Posted on Jul 23, 2026 - 15:26 UTC

[DE1][Storage] - File storage maintenance notification Aug 6, 2026 07:00-14:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our file storage infrastructure.

Start time : 06/08/2026 07:00 UTC
End time : 06/08/2026 14:00 UTC
Service impact : None.
Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our file storage infrastructure.

Thank you for your understanding.
Posted on Jul 23, 2026 - 15:30 UTC

[GRA3][Storage] - File storage maintenance notification Aug 6, 2026 12:00-18:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our file storage infrastructure.

Start time : 06/08/2026 12:00 UTC
End time : 06/08/2026 18:00 UTC
Service impact : None.
Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our file storage infrastructure.

Thank you for your understanding.
Posted on Jul 23, 2026 - 15:28 UTC

[AP-SOUTHEAST-SYD2][Public Cloud] - Planned decommission of the region Aug 15, 2026 06:00-16:00 UTC

Start time : 15/08/2026 06:00 UTC
End time : 15/08/2026 16:00 UTC
Service impact : Public Cloud instances hosted in the AP-SOUTHEAST-SYD-2 region
Service improvement : As part of the continuous evolution of our Public Cloud offering, OVHcloud will progressively phase out the AP-SOUTHEAST-SYD-2 region in Sydney and focus future developments on the SYD1 region.
Services hosted in AP-SOUTHEAST-SYD-2 will enter maintenance mode before a definitive shutdown in the coming months.
Affected customers must manually migrate their workloads and data to the SYD1 region to avoid service disruption.

Required customer actions
Customers are required to:
- Create new instances in the SYD1 region
- Manually migrate applications, services, and data
- Validate workloads on the new infrastructure
- Stop and delete old instances once migration is completed

We strongly recommend performing backups before starting the migration process.
Migration documentation:
https://help.ovhcloud.com/csm/en-ie-public-cloud-compute-migration-between-az?id=kb_article_view&sysparm_article=KB0073126

To compensate for the inconvenience, OVHcloud will automatically apply a credit corresponding to one month of the affected services usage.
Posted on May 28, 2026 - 09:48 UTC

[GLOBAL][Data & Analytics] - Data Platform maintenance notification Aug 17, 2026 12:00-15:00 UTC

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

Start time : 17/08/2026 12:00 UTC
End time : 17/08/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 Jul 15, 2026 - 23:42 UTC

[GRA/BHS][Identity, Security & Operations] - Logs Data Platform maintenance notification Sep 16, 2026 10:30-19:30 UTC

As part of maintenance for the Logs Data Platform, we will replace the certificates for your Data-gathering tools on 16 September 2026, as the current intermediate certificate expires on 20 September 2026.

Start time : 16/09/2026 10:30 UTC
End time : 16/09/2026 19:30 UTC
Service impact : Customers who send their logs directly to the clusters are not affected by this maintenance and can disregard the rest of this message (Customer's log ingestion endpoint looks like gra1.logs.ovh.com:12202, no action is required).
However, customers who use an endpoint such as gra1-65d66a0a68728d746bbebbab.gra1.logs.ovh.com:6514 are affected by this maintenance and we recommend them to follow the relevant action plan below.

Case 1 — The customer's log forwarder agent performs no certificate verification
Customers who keep this behavior will not be impacted by the maintenance. No action is required.

Case 2 — The customer's log forwarder agent validates only the intermediate chain
1. Import the new certificate chain (as soon as possible). The new chain (self-signed, valid for 10 years) is already available in the OVHcloud Manager, on the home page of the customer's Logs Data Platform service. Customers should import it into their configuration before 16 September 2026.
2. Keep the old chain in place temporarily. Until 16 September 2026, customers should leave the old chain in their configuration so the agent accepts both chains (old + new) during the transition window, avoiding any surprise.
3. After 16 September 2026, once the maintenance is complete, customers should remove the old chain and keep only the new one (valid for 10 years).

Case 3 — The customer's log forwarder agent validates the intermediate + Data-gathering-tool certificate chain
1. Create a new Data-gathering tool in the Logs Data Platform project, replicating the exact configuration of the previous one.
2. Import the full certificate chain (intermediate + new self-signed certificate). Customers should go to the Data-gathering tools page, then open the "Useful information" section to obtain it.
3. Update the log forwarder agent configuration to push logs to this new Data-gathering tool.
4. Delete the old Data-gathering tool.
Service improvement : This maintenance renews the certificate chain that secures your log ingestion, ensuring uninterrupted and secure log delivery. The new chain is self-signed and valid for 10 years.

Thank you for your understanding.
Posted on Jul 03, 2026 - 09:47 UTC

Jul 30, 2026

[RBX-A][Storage] - File storage maintenance notification
Completed - The scheduled maintenance has been completed.
Jul 30, 15:27 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 30, 12:00 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our file storage infrastructure.

Start time : 30/07/2026 12:00 UTC
End time : 30/07/2026 18:00 UTC
Service impact : None.
Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our file storage infrastructure.

Thank you for your understanding.
Jul 23, 14:36 UTC
[RBX-A][Storage] - File storage maintenance notification
Completed - We would like to inform you that the maintenance on our file storage infrastructure is now completed.
All services are operational.

Thank you for your patience throughout this maintenance.
Jul 30, 09:43 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 30, 07:00 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our file storage infrastructure.

Start time : 30/07/2026 07:00 UTC
End time : 30/07/2026 14:00 UTC
Service impact : None.
Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our file storage infrastructure.

Thank you for your understanding.
Jul 23, 14:34 UTC

Jul 29, 2026

[GRA][Storage] - Object Storage incident notification
Resolved - We had an incident on our Object Storage offer in GRA region which has now been resolved.

Here are some supplementary details :

Start time : 29/07/2026 06:00 UTC
End time : 29/07/2026 11:00 UTC
Impacted Service(s) : Slowness and 504 error were observed for object storage located in GRA.
Customers Impact : Customers were temporarily facing slowness and 504 error when trying to access and use their objects in the specified region.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We thank you for your understanding and patience throughout this incident.
Jul 29, 13:06 UTC
[RBX-A][Storage] - File storage maintenance notification
Completed - We would like to inform you that the maintenance on our storage infrastructure is now completed.
All services are operational.

Thank you for your patience throughout this maintenance.
Jul 29, 09:38 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 29, 07:00 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our file storage infrastructure.

Start time : 29/07/2026 07:00 UTC
End time : 29/07/2026 14:00 UTC
Service impact : None.
Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our file storage infrastructure.

Thank you for your understanding.
Jul 23, 14:01 UTC
[GRA][Public Cloud] - Network Maintenance Notification
Completed - All services are operational.
Jul 29, 03:25 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 28, 20:01 UTC
Update - The following maintenance windows have been rescheduled:

Start time : 28/07/2026 20:00 UTC
End time : 29/07/2026 04:00 UTC
Service impact : Customers hosted in the GRA1/3/5/7/9/11 regions zone may experience IPv4/IPv6 packet loss for up to 1 hour, during network infrastructure maintenance on the Public Cloud environment.
Service improvement : As part of our continuous improvement policy, we will be performing maintenance on the Public Cloud network infrastructure in the GRA regions to reinforce redundancy.

Thank you for your understanding.
Jul 27, 14:08 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our Public Cloud infrastructure.

Start time : 29/07/2026 20:00 UTC
End time : 30/07/2026 04:00 UTC
Service impact : Customers hosted in the GRA1/3/5/7/9/11 regions zone may experience IPv4/IPv6 packet loss for up to 1 hour, during network infrastructure maintenance on the Public Cloud environment.
Service improvement : As part of our continuous improvement policy, we will be performing maintenance on the Public Cloud network infrastructure in the GRA regions to reinforce redundancy.

Thank you for your understanding.
Jul 24, 16:02 UTC
[GRA][Public Cloud] - Network Maintenance Notification
Completed - All services are operational.
Jul 29, 03:25 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 28, 20:00 UTC
Update - The following maintenance windows have been rescheduled:

Start time : 28/07/2026 20:00 UTC
End time : 29/07/2026 04:00 UTC
Service impact : Customers hosted in the GRA1/3/5/7/9/11 regions zone may experience IPv4/IPv6 packet loss for up to 1 hour, during network infrastructure maintenance on the Public Cloud environment.
Service improvement : As part of our continuous improvement policy, we will be performing maintenance on the Public Cloud network infrastructure in the GRA regions to reinforce redundancy.

Thank you for your understanding.
Jul 27, 14:04 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our Public Cloud infrastructure.

Start time : 29/07/2026 20:00 UTC
End time : 30/07/2026 04:00 UTC
Service impact : Customers hosted in the GRA1/3/5/7/9/11 regions zone may experience IPv4/IPv6 packet loss for up to 1 hour, during network infrastructure maintenance on the Public Cloud environment.
Service improvement : As part of our continuous improvement policy, we will be performing maintenance on the Public Cloud network infrastructure in the GRA regions to reinforce redundancy.

Thank you for your understanding.
Jul 24, 15:55 UTC

Jul 28, 2026

[WAW1][Compute - Instance] - Some instances incident notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved.

Start time : 28/07/2026 17:06 UTC
End time : 28/07/2026 17:12 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 28, 17:21 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 WAW1 region.

Here are some supplementary details :
Start time : 28/07/2026 17:06 UTC
Impacted Service(s) : Some instances in the WAW1 region are unreachable.
Customers Impact : Some customers are temporarily unable to access instances located in the specified region.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 28, 17:12 UTC
[GLOBAL][Storage] - Object Storage S3 maintenance notification
Completed - The scheduled maintenance has been completed.
Jul 28, 16:56 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 28, 16:40 UTC
Scheduled - As part of our continuous improvement and security enhancement efforts, we are rolling out a security fix for our Object Storage S3 offering.

This update addresses an authorization validation issue related to AWS Signature Version 4 (SigV4).

Previously, requests could include additional x-amz-* headers that were not included in the signature validation process.
In some cases, this could allow a presigned URL request to be modified by adding unsigned, meaningful headers (such as x-amz-copy-source), potentially altering the intended operation.

Following this update, our gateway will enforce the same behavior as AWS S3: all x-amz-* headers included in a request must be part of the SignedHeaders list.

Requests containing unsigned x-amz-* headers will now be rejected.

Start time : 27/07/2026 08:00 UTC
End time : 28/07/2026 10:00 UTC
Service impact : Customers using properly signed SigV4 requests will not experience any impact. Customers relying on unsigned x-amz-* headers in their requests may need to update their request signing process to ensure all x-amz-* headers are included in the signature.

This is tracked upstream as OpenStack Swift bug [#2158733]
(https://bugs.launchpad.net/swift/+bug/2158733) affecting Swift ≥ 2.18.0.

What you will see

A request with an unsigned `x-amz-*` header now returns **HTTP 403** with :
```xml

AccessDenied

There were headers present in the request which were not signed
x-amz-storage-class

```
The HeadersNotSigned element names the offending header, so it is easy to diagnose.

Are you affected?

- **Standard SDKs (boto3, AWS SDKs) and the AWS CLI: not affected.** They already sign every `x-amz-*` header they send. Keep your SDK reasonably up to date and you have nothing to do.
- **You may be affected if** you build requests by hand, or generate a presigned URL and then attach extra `x-amz-*` headers (storage class, ACL, tagging, user metadata, copy-source, SDK checksum headers…) at request time.
Those headers must be part of the signature.
- **One exception:** `x-amz-content-sha256` does not need to be listed in `SignedHeaders` its value already *is* the payload hash bound into the signature. (`x-amz-date` **does** have to be signed.)

How to presign requests correctly

The rule is the same in every language: **put the `x-amz-*` headers into the signing step, and make the caller replay exactly those headers** — never add an `x-amz-*` header to an already-generated presigned URL.



Python (boto3)

**Do sign the headers at generation time** — pass them to
`generate_presigned_url` via `Params` so boto3 folds them into the signature:

```python
import boto3

s3 = boto3.client("s3", endpoint_url="https://s3..example.com")

url = s3.generate_presigned_url(
"put_object",
Params={
"Bucket": "my-bucket",
"Key": "my-object",
"StorageClass": "STANDARD_IA", # -> signed x-amz-storage-class
"ACL": "private", # -> signed x-amz-acl
"Metadata": {"team": "backup"}, # -> signed x-amz-meta-team
},
ExpiresIn=3600,
)

# The caller must send EXACTLY those headers with the PUT:
import requests
requests.put(
url,
data=b"...payload...",
headers={
"x-amz-storage-class": "STANDARD_IA",
"x-amz-acl": "private",
"x-amz-meta-team": "backup",
},
)
```

**Do NOT** presign a bare request and bolt an `x-amz-*` header on afterwards:

```python
# WRONG — the header is not covered by the signature -> 403 AccessDenied
url = s3.generate_presigned_url(
"put_object",
Params={"Bucket": "my-bucket", "Key": "my-object"},
ExpiresIn=3600,
)
requests.put(url, data=b"...", headers={"x-amz-storage-class": "STANDARD_IA"})
```

**Direct (non-presigned) calls need no change** — the SDK signs everything for
you:

```python
s3.put_object(
Bucket="my-bucket", Key="my-object", Body=b"...",
StorageClass="STANDARD_IA", Metadata={"team": "backup"},
)
```

Go (aws-sdk-go-v2)

Set the headers on the input so the presigner signs them. The returned
`req.SignedHeader` lists the headers the caller **must** replay verbatim:

```go
import (
"bytes"
"context"
"net/http"
"time"

"github.com/aws/aws-sdk-go-v2/aws"
"github.com/aws/aws-sdk-go-v2/service/s3"
"github.com/aws/aws-sdk-go-v2/service/s3/types"
)

presigner := s3.NewPresignClient(client)
req, err := presigner.PresignPutObject(context.TODO(), &s3.PutObjectInput{
Bucket: aws.String("my-bucket"),
Key: aws.String("my-object"),
StorageClass: types.StorageClassStandardIa, // -> signed x-amz-storage-class
ACL: types.ObjectCannedACLPrivate, // -> signed x-amz-acl
Metadata: map[string]string{"team": "backup"}, // -> signed x-amz-meta-team
}, s3.WithPresignExpires(time.Hour))

// Replay req.SignedHeader as-is; do not add or drop any x-amz-* header.
httpReq, _ := http.NewRequest(req.Method, req.URL, bytes.NewReader(payload))
httpReq.Header = req.SignedHeader.Clone()
// ... send httpReq with your HTTP client ...
```

Direct (non-presigned) calls need no change — the SDK signs every `x-amz-*`
header:

```go
_, err := client.PutObject(context.TODO(), &s3.PutObjectInput{
Bucket: aws.String("my-bucket"),
Key: aws.String("my-object"),
Body: bytes.NewReader(payload),
StorageClass: types.StorageClassStandardIa,
Metadata: map[string]string{"team": "backup"},
})
```

JavaScript / TypeScript (aws-sdk-js-v3)

Put the headers on the command; `getSignedUrl` folds them into the signature.
The caller must send exactly those headers:

```javascript
import { S3Client, PutObjectCommand } from "@aws-sdk/client-s3";
import { getSignedUrl } from "@aws-sdk/s3-request-presigner";

const s3 = new S3Client({ endpoint: "https://s3..example.com" });

const command = new PutObjectCommand({
Bucket: "my-bucket",
Key: "my-object",
StorageClass: "STANDARD_IA", // -> signed x-amz-storage-class
ACL: "private", // -> signed x-amz-acl
Metadata: { team: "backup" }, // -> signed x-amz-meta-team
});

const url = await getSignedUrl(s3, command, { expiresIn: 3600 });

// The caller must send EXACTLY those headers with the PUT:
await fetch(url, {
method: "PUT",
body: payload,
headers: {
"x-amz-storage-class": "STANDARD_IA",
"x-amz-acl": "private",
"x-amz-meta-team": "backup",
},
});
```

Direct (non-presigned) calls need no change — the SDK signs every `x-amz-*`
header:

```javascript
await s3.send(new PutObjectCommand({
Bucket: "my-bucket", Key: "my-object", Body: payload,
StorageClass: "STANDARD_IA", Metadata: { team: "backup" },
}));
```

Java (AWS SDK for Java v2)

Set the headers on the `PutObjectRequest`; the presigner signs them. The caller
must replay `presigned.signedHeaders()` verbatim:

```java
import java.time.Duration;
import java.util.Map;
import software.amazon.awssdk.services.s3.model.ObjectCannedACL;
import software.amazon.awssdk.services.s3.model.PutObjectRequest;
import software.amazon.awssdk.services.s3.model.StorageClass;
import software.amazon.awssdk.services.s3.presigner.S3Presigner;
import software.amazon.awssdk.services.s3.presigner.model.PresignedPutObjectRequest;
import software.amazon.awssdk.services.s3.presigner.model.PutObjectPresignRequest;

try (S3Presigner presigner = S3Presigner.create()) {
PutObjectRequest objectRequest = PutObjectRequest.builder()
.bucket("my-bucket")
.key("my-object")
.storageClass(StorageClass.STANDARD_IA) // -> signed x-amz-storage-class
.acl(ObjectCannedACL.PRIVATE) // -> signed x-amz-acl
.metadata(Map.of("team", "backup")) // -> signed x-amz-meta-team
.build();

PresignedPutObjectRequest presigned = presigner.presignPutObject(
PutObjectPresignRequest.builder()
.signatureDuration(Duration.ofHours(1))
.putObjectRequest(objectRequest)
.build());

// presigned.url() is the URL; the caller MUST send presigned.signedHeaders()
// (x-amz-storage-class, x-amz-acl, x-amz-meta-team, ...) unchanged.
}
```

Direct (non-presigned) calls need no change — the SDK signs every `x-amz-*`
header:

```java
s3.putObject(
PutObjectRequest.builder()
.bucket("my-bucket").key("my-object")
.storageClass(StorageClass.STANDARD_IA)
.metadata(Map.of("team", "backup"))
.build(),
RequestBody.fromBytes(payload));
```

Rust (aws-sdk-s3)

Set the headers on the operation builder before `.presigned(...)`; the caller
must replay `presigned.headers()` verbatim:

```rust
use std::time::Duration;
use aws_sdk_s3::presigning::PresigningConfig;
use aws_sdk_s3::types::{ObjectCannedAcl, StorageClass};

let presigned = client
.put_object()
.bucket("my-bucket")
.key("my-object")
.storage_class(StorageClass::StandardIa) // -> signed x-amz-storage-class
.acl(ObjectCannedAcl::Private) // -> signed x-amz-acl
.metadata("team", "backup") // -> signed x-amz-meta-team
.presigned(PresigningConfig::expires_in(Duration::from_secs(3600))?)
.await?;

// presigned.uri() is the URL; the caller MUST send presigned.headers()
// (x-amz-storage-class, x-amz-acl, x-amz-meta-team, ...) unchanged.
```

Direct (non-presigned) calls need no change — the SDK signs every `x-amz-*`
header:

```rust
client
.put_object()
.bucket("my-bucket")
.key("my-object")
.body(payload.into())
.storage_class(StorageClass::StandardIa)
.metadata("team", "backup")
.send()
.await?;
```

Browser-based POST uploads

Use `generate_presigned_post` (or the equivalent in your SDK) — the fields are covered by the signed policy document, so this pattern is already correct.


Action required

Review any code that (a) hand-crafts SigV4 requests, or (b) adds `x-amz-*`
headers to a presigned URL after it was generated. Move those headers into the
signing step as shown above. If you rely on standard SDKs, no action is needed.

References

- OpenStack Swift bug [#2158733](https://bugs.launchpad.net/swift/+bug/2158733)
(OSSA-2026, CVEs pending)
- AWS S3 documentation: [Signature Calculations for the Authorization Header](https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html)

Thank you for your understanding.
Jul 28, 16:36 UTC
[SBG5/7][Storage] - File storage maintenance notification
Completed - The scheduled maintenance has been completed.
Jul 28, 15:23 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 28, 12:00 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our file storage infrastructure.

Start time : 28/07/2026 12:00 UTC
End time : 28/07/2026 18:00 UTC
Service impact : None.
Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our file storage infrastructure.

Thank you for your understanding.
Jul 23, 13:58 UTC
[GRA11][Network] - Load Balancer incident notification
Resolved - We are pleased to inform you that the incident affecting our Load Balancer offering has been resolved.

Start time : 27/07/2026 07:41 UTC
End time : 28/07/2026 14:45 UTC
Root Cause : This incident was caused by a software issue.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 28, 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 : The majority of customers are no longer impacted by the incident.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

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

Please find below an update on the situation:
Update : Our teams are currently working on a fix to resolve the issue.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 28, 11:25 UTC
Identified - 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 : 27/07/2026 07:41 UTC
Impacted Service(s) : Creation of Public Cloud instances on GRA11 LoadBalancer is temporarily unavailable.
Customers Impact : Customers are temporarily unable to create new Public Cloud instances on LoadBalancer.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 27, 12:52 UTC
[SBG5/7][Storage] - File storage maintenance notification
Completed - The scheduled maintenance has been completed.
Jul 28, 09:41 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 28, 07:00 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our file storage infrastructure.

Start time : 28/07/2026 07:00 UTC
End time : 28/07/2026 15:00 UTC
Service impact : None.
Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our file storage infrastructure.

Thank you for your understanding.
Jul 23, 13:55 UTC
[GRA4][Public Cloud] - CEPH Storage maintenance notification
Completed - The scheduled maintenance has been completed.
Jul 28, 08:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 28, 05:30 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our Public Cloud Storage services.

Start time : 28/07/2026 05:30 UTC
End time : 28/07/2026 14:30 UTC
Service impact : None.
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our CEPH Storage in the GRA4 region.

Thank you for your understanding.
Jul 24, 20:18 UTC

Jul 27, 2026

[GLOBAL][Data & Analytics] - Data Platform maintenance notification
Completed - The scheduled maintenance has been completed.
Jul 27, 15:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 27, 13:00 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our Data Platform offer.

Start time : 27/07/2026 13:00 UTC
End time : 27/07/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.
Jul 22, 19:58 UTC
[UK1][Compute - Instance] - Some instances incident notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering in UK1 region has been resolved.

Start time : 27/07/2026 06:19 UTC
End time : 27/07/2026 07:40 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 27, 08:39 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 UK1 region.

Here are some supplementary details :

Start time : 27/07/2026 06:19 UTC
Impacted Service(s) : Some instances in the UK1 region are unreachable.
Customers Impact : Some customers are temporarily unable to access instances located in the specified region.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 27, 06:33 UTC

Jul 26, 2026

No incidents reported.

Jul 25, 2026

No incidents reported.

Jul 24, 2026

[EU-WEST-PAR][Storage] - Object storage S3 Standard Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Storage offering has been resolved.

Start time : 23/07/2026 18:00 UTC
End time : 23/07/2026 23:15 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 24, 12:58 UTC
Monitoring - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : The services are operational again since 23/07/2026 23:15 UTC.
Ongoing Actions : Our team will monitor the situation.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 23, 23:30 UTC
Investigating - We are currently investigating an incident affecting our Storage offering, which is causing temporary issue in the EU-WEST-PAR region.

Here are some supplementary details :

Start time : 23/07/2026 18:00 UTC
Impacted Service(s) : Intermittent HTTP 503 errors may affect object upload and download operations.
Customers Impact : Customers may experience issues downloading or uploading their objects due to 503 errors.
Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 23, 19:14 UTC

Jul 23, 2026

[GRA1/3/9/11][Compute - Instance] - Some Instances Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved.

Start time : 23/07/2026 17:52 UTC
End time : 23/07/2026 17:58 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 23, 18: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 GRA1/3/9/11 regions.

Here are some supplementary details :

Start time : 23/07/2026 17:52 UTC
Impacted Service(s) : Some instances in the GRA1/3/9/11 regions are unreachable.
Customers Impact : Some customers are temporarily unable to access instances located on the specified regions.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 23, 18:05 UTC

Jul 22, 2026

[GLOBAL][Storage] - Block storage maintenance notification
Completed - The scheduled maintenance has been completed.
Jul 22, 10:55 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 20, 11:25 UTC
Scheduled - As part of our continuous improvement plan, maintenance is scheduled on our Block Storage offer in regions listed below :

DE1
EU-WEST-PAR-A
GRA11
GRA3
GRA5
GRA7
GRA9
RBX-A
SBG5
SYD1
US-WEST-OR

Start time : 20/07/2026 10:00 UTC
End time : 23/07/2026 13: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.
Jul 20, 11:21 UTC

Jul 21, 2026

[DE1][Storage] - File storage maintenance notification
Completed - We would like to inform you that the maintenance on our file storage is now completed.
All services are operational.

Thank you for your patience throughout this maintenance.
Jul 21, 14:32 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 21, 07:00 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our file storage infrastructure.

Start time : 21/07/2026 07:00 UTC
End time : 21/07/2026 14:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our file storage infrastructure.

Thank you for your understanding.
Jul 16, 05:38 UTC
[GLOBAL][Storage] - Object Storage S3 maintenance notification
Completed - We would like to inform you that the maintenance on our Object Storage is now completed.
All services are operational.

Thank you for your patience throughout this maintenance.
Jul 21, 14:21 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 15, 07:00 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our Object Storage offer.

Start time : 15/07/2026 07:00 UTC
End time : 22/07/2026 16:00 UTC
Service impact : S3-compatible Object Storage endpoints will now support IPv6 in dual-stack mode (IPv4 and IPv6), while maintaining unchanged IPv4 connectivity. However, customers with misconfigured IPv6 networking may experience connectivity issues when accessing S3-compatible Object Storage.
Below you can find the table regarding the endpoints and records being added:

RegionDNSnew AAAA record
SBGs3.sbg.perf.cloud.ovh.net
s3.sbg.io.cloud.ovh.net		2001:41d0:404:700::1
 s3-website.sbg.perf.cloud.ovh.net
s3-website.sbg.io.cloud.ovh.net		2001:41d0:404:700::2
GRAs3.gra.perf.cloud.ovh.net
s3.gra.io.cloud.ovh.net		2001:41d0:304:c00::1
 s3-website.gra.perf.cloud.ovh.net
s3-website.gra.io.cloud.ovh.net		2001:41d0:304:c00::2
BHSs3.bhs.perf.cloud.ovh.net
s3.bhs.io.cloud.ovh.net		2607:5300:205:700::1
 s3-website.bhs.perf.cloud.ovh.net
s3-website.bhs.io.cloud.ovh.net		2607:5300:205:700::2
RBXs3.rbx.perf.cloud.ovh.net
s3.rbx.io.cloud.ovh.net		2001:41d0:20a:a00::1
 s3-website.rbx.perf.cloud.ovh.net
s3-website.rbx.io.cloud.ovh.net		2001:41d0:20a:a00::2
UKs3.uk.perf.cloud.ovh.net
s3.uk.io.cloud.ovh.net		2001:41d0:804:100::1
 s3-website.uk.perf.cloud.ovh.net
s3-website.uk.io.cloud.ovh.net		2001:41d0:804:100::2
DEs3.de.perf.cloud.ovh.net
s3.de.io.cloud.ovh.net		2001:41d0:705:4200::1
 s3-website.de.perf.cloud.ovh.net
s3-website.de.io.cloud.ovh.net		2001:41d0:705:4200::2
WAWs3.waw.perf.cloud.ovh.net
s3.waw.io.cloud.ovh.net		2001:41d0:622::1
 s3-website.waw.perf.cloud.ovh.net
s3-website.waw.io.cloud.ovh.net		2001:41d0:622::2
CA-EAST-TORs3.ca-east-tor.perf.cloud.ovh.net
s3.ca-east-tor.io.cloud.ovh.net		2607:5300:304::1
 s3-website.ca-east-tor.perf.cloud.ovh.net
s3-website.ca-east-tor.io.cloud.ovh.net		2607:5300:304::2
SGPs3.sgp.perf.cloud.ovh.net
s3.sgp.io.cloud.ovh.net		2402:1f00:8002:300::1
 s3-website.sgp.perf.cloud.ovh.net
s3-website.sgp.io.cloud.ovh.net		2402:1f00:8002:300::2
AP-SOUTHEAST-SYDs3.ap-southeast-syd.perf.cloud.ovh.net
s3.ap-southeast-syd.io.cloud.ovh.net		2402:1f00:8102:400::1
 s3-website.ap-southeast-syd.perf.cloud.ovh.net
s3-website.ap-southeast-syd.io.cloud.ovh.net		2402:1f00:8102:400::2
AP-SOUTH-MUMs3.ap-south-mum.perf.cloud.ovh.net
s3.ap-south-mum.io.cloud.ovh.net		2402:1f00:8303:200::1
 s3-website.ap-south-mum.perf.cloud.ovh.net
s3-website.ap-south-mum.io.cloud.ovh.net		2402:1f00:8303:200::2
EU-WEST-PARs3.eu-west-par.io.cloud.ovh.net2001:41d0:a0b:500::1
 s3-website.eu-west-par.io.cloud.ovh.net2001:41d0:a0b:500::2
EU-SOUTH-MILs3.eu-south-mil.io.cloud.ovh.net2001:41d0:2005:200::1
 s3-website.eu-south-mil.io.cloud.ovh.net2001:41d0:2005:200::2
US-EAST-VAs3.us-east-va.perf.cloud.ovh.net
s3.us-east-va.io.cloud.ovh.net		2604:2dc0:101:500::1
 s3-website.us-east-va.perf.cloud.ovh.net
s3-website.us-east-va.io.cloud.ovh.net		2604:2dc0:101:500::2
US-WEST-ORs3.us-west-or.perf.cloud.ovh.net
s3.us-west-or.io.cloud.ovh.net		2604:2dc0:202:400::1
 s3-website.us-west-or.perf.cloud.ovh.net
s3-website.us-west-or.io.cloud.ovh.net		2604:2dc0:202:400::2

Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Object Storage S3 infrastructure.

Thank you for your understanding.
Jun 22, 12:19 UTC
[GLOBAL][Databases] - Database incident notification
Resolved - We are pleased to inform you that the incident affecting our Databases offering has been resolved.

Start time : 19/07/2026 18:00 UTC
End time : 21/07/2026 08:00 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 21, 10:19 UTC
Monitoring - Update: Database access has been restored across all regions. Our teams are continuing to work on the remaining impacted databases in GRA11.
Pending orders are being delivered, and new orders are no longer suspended.

Monitoring remains in place to ensure long-term stability.

We apologize for any inconvenience caused and appreciate your understanding and patience.
Jul 20, 22:15 UTC
Update - Please find an update of this incident below :

Update: Database access is being progressively restored in all regions, with the exception of GRA11.
Pending orders are now being progressively delivered. As a precaution, new orders remain temporarily suspended.

Ongoing Actions : Our teams continue to restore the remaining impacted region and are closely monitoring the situation.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 20, 20:35 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : Customers are temporarily unable to access and fork their databases.
Please note that no data has been lost, and all data remains intact.
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.
Jul 20, 16:33 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Databases offering

Here are some supplementary details :

Start time : 19/07/2026 18:00 UTC
Impacted Service(s) : Some Database are temporarily unavailable.
Customers Impact : Customers are temporarily unable to access their Database located on the specified region.
Root Cause : 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.
Jul 20, 07:48 UTC

Jul 20, 2026

[GRA5/7/9/11][Compute - Instance] - Some instances incident notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved.

Start time : 20/07/2026 15:02 UTC
End time : 20/07/2026 15: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.
Jul 20, 15:57 UTC
Monitoring - Service has been fully restored since 20/07/2026 15:10 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 20/07/2026 15:02 UTC
Impacted Service(s) : Some instances in the GRA5, GRA7, GRA9 and GRA11 regions were unreachable.
Customers Impact : Some customers were temporarily unable to access instances located on the specified regions.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 20, 15:24 UTC
[GLOBAL][Data & Analytics] - Data Platform maintenance notification
Completed - The scheduled maintenance has been completed.
Jul 20, 13:13 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 20, 12:00 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our Data Platform offer.

Start time : 20/07/2026 12:00 UTC
End time : 20/07/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.
Jul 8, 15:33 UTC
[GLOBAL][Public Cloud] - Mandatory Maintenance
Completed - We would like to inform you that the maintenance on our Public Cloud Infrastructure is now completed.

End time : 20/07/2026 07:00 UTC

All services are operational.

Consult this page for more information about this maintenance : https://blog.ovhcloud.com/cve-2026-53359-januscape-patching-campaign-lessons-learned-from-remediating-a-kvm-flaw-across-tens-of-thousands-of-machines/

Thank you for your patience throughout this maintenance.
Jul 20, 12:08 UTC
Update - Scheduled maintenance is still in progress. We will provide updates as necessary.
Jul 10, 13:55 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 10, 09:05 UTC
Scheduled - Please be informed we will be performing a mandatory maintenance to upgrade our Public Cloud Infrastructure.

During this maintenance window, services will be impacted for approximately 30 minutes or less.

Start time : 10/07/2026 08:00 UTC

Important information :
• If instances do not return by the end of the maintenance window, please try a simple reboot on your end first. If this does not work, please raise an incident to Support to address the issue.

Thank you for your understanding.
Jul 10, 09:03 UTC
[EU/BHS][Databases] - Maintenance notification
Completed - We would like to inform you that the maintenance on our Public Cloud Databases is now completed.
All services are operational.

Thank you for your patience throughout this maintenance.
Jul 20, 07:50 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 10, 13:44 UTC
Scheduled - Please be informed we will be performing a mandatory maintenance to upgrade our Public Cloud Databases.

Start time : 10/07/2026 09:58 UTC
Service impact : Single-node (non-HA) services will be temporarily unavailable during the operation, whereas redundant, high-availability multi-node services fail over automatically and remain available.
Management operations (create, delete, update, and upgrade) may experience slower processing times during this period.
We recommend our high-availability offerings for customers who require uninterrupted service continuity.
Service improvement : This upgrade strengthens the reliability and performance of our Public Cloud databases.

Thank you for your understanding.
Jul 10, 13:43 UTC

Jul 19, 2026

[GRA11][Compute - Instance] - Instance creation incident notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering in GRA11 has been resolved.

Start time : 19/07/2026 16:50 UTC
End time : 19/07/2026 19:14 UTC
Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 19, 19:16 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 GRA11.

Here are some supplementary details :

Start time : 19/07/2026 16:50 UTC
Impacted Service(s) : Creation of Public Cloud instances in GRA11 region is temporarily unavailable.
Customers Impact : Customers are temporarily unable to create new Public Cloud instances.
Instances created during the incident will remain stuck in a "building"/"spawning" state and will not become operational.
Once the incident is resolved, customers are advised to delete these instances and create new ones.
Root Cause : This incident is caused by our provider.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 19, 17:50 UTC
[GRA11][Compute - Instance] - Instance creation incident notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering in GRA11 has been resolved.

Start time : 19/07/2026 08:00 UTC
End time : 19/07/2026 15:32 UTC
Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 19, 15:36 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 GRA11.

Here are some supplementary details :

Start time : 19/07/2026 08:00 UTC
Impacted Service(s) : Creation of Public Cloud instances in GRA11 region is temporarily unavailable.
Customers Impact : Customers are temporarily unable to create new Public Cloud instances.
Instances created during the incident will remain stuck in a "building"/"spawning" state and will not become operational.
Once the incident is resolved, customers are advised to delete these instances and create new ones.
Root Cause : This incident is caused by our provider.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 19, 13:26 UTC
[GRA][AI & Machine Learning] - AI Deploy/Training/Notebooks incident notification
Resolved - We are pleased to inform you that the incident affecting our AI & Machine Learning offering on AI Deploy, AI Training and AI Notebooks has been resolved.

Start time : 19/07/2026 12:40 UTC
End time : 19/07/2026 14:30 UTC
Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 19, 14:31 UTC
Investigating - We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary issue in the GRA region.

Here are some supplementary details :

Start time : 19/07/2026 12:40 UTC
Impacted Service(s) : AI Deploy, AI Training and AI Notebooks are temporarily unavailable.
Customers Impact : Customers are temporarily unable to access and use models in the specified offers.
Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 19, 14:27 UTC

Jul 18, 2026

No incidents reported.

Jul 17, 2026

No incidents reported.

Jul 16, 2026

[BHS/GRA][Identity, Security & Operations] - Logs Data Platform incident notification
Resolved - We are pleased to inform you that the incident affecting our Logs Data Platform service has been resolved.

Start time : 15/07/2026 18:00 UTC
End time : 16/07/2026 13:00 UTC
Root Cause : This incident was caused by a software issue.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 16, 13:02 UTC
Investigating - We are currently experiencing an incident affecting our Logs Data Platform service, which is causing temporary availability issues.

Please find the details of this incident below :
Start time : 15/07/2026 18:00 UTC
Impacted Service(s) : The WebSocket connection on Logs Data Platform is temporarily unavailable.
Customers Impact : Customers are temporarily unable to use the Logs Data Platform WebSocket connection.
Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it. 

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 16, 12:03 UTC
← Incident History Powered by Atlassian Statuspage