OVHcloud Public Cloud Status

Current status
Legend
  • Operational
  • Degraded performance
  • Partial Outage
  • Major Outage
  • Under maintenance
Update - Please find below an update on the situation:

Update : Archive recovery is still underway.
We would like to clarify the situation regarding restorations.
In the meantime, if a customer needs to restore a bucket in "archiving" status, he must submit a support ticket (the criticality level is at the customer's discretion) so that we can perform the restoration.
Ongoing Actions : Our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

Jan 27, 2026 - 10:36 UTC
Update - Please find below an update on the situation:
Update : The completion rate has now returned to normal levels; however, a considerable amount of time will still be required to fully clear the backlog.
Ongoing Actions : Our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

Jan 08, 2026 - 16:42 UTC
Update - Please find below an update on the situation:
Update : We continue to see a backlog of archiving operations that began on  07 Nov 2025 10:00 UTC. The backlog is being processed, but the rate of completion remains below normal levels, resulting in extended latency for new archiving requests. No new tasks are being blocked, but they are progressing more slowly than expected.
Ongoing Actions : Our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

Dec 29, 2025 - 16:17 UTC
Update - Please find below an update on the situation:
Update : We are continuing our archiving efforts, though completion is taking longer than expected.
Ongoing Actions : Our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

Dec 26, 2025 - 21:12 UTC
Update - Please find below an update on the situation:
Update : We are still catching up on archiving, but it's slower than expected.
Ongoing Actions : Our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

Dec 17, 2025 - 10:37 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : Archiving tasks aren't stuck anymore but slowness is observed.
As soon as a customer request archiving, the data will be billed as if it were on tape even though it may take a while for the data to actually reach the tape.
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.

Dec 12, 2025 - 16:58 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : We are currently catching up on archiving, but we do not have an estimated time frame to share with you at this time.
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.

Dec 01, 2025 - 14:21 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Cold archive offer on the specific region.

Here are some supplementary details :

Start time : 07/11/2025 10:00 UTC
Impacted Service(s) : Archiving tasks are temporarily stuck in "Archiving" state.
Customers Impact : Customers are temporarily unable to archive their data.
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.

Nov 20, 2025 - 10:48 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : We continue to work with our provider 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.

Jan 07, 2026 - 19:22 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted.
Actions in progress :
Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored.
Key guidance for customers :
No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored.
Root Cause : This incident is caused by our provider.
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

Dec 26, 2025 - 12:58 UTC
Monitoring - Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible.
The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

Dec 19, 2025 - 08:32 UTC
Update - We are continuing to work on a fix for this issue.
Dec 15, 2025 - 14:36 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

Nov 03, 2025 - 14:50 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC
Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y").
Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y.
Root Cause : This incident is caused by our provider.
Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

Oct 31, 2025 - 12:18 UTC
Investigating - We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC
Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y").
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.

Oct 30, 2025 - 16:15 UTC

About This Site

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

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 || AP-SOUTH-MUM 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-1 Operational
BHS5 Operational
DE1 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
SBG5 Operational
SGP1 Operational
SYD1 Operational
WAW1 Operational
UK1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
Containers & Orchestration || Managed Kubernetes Service Operational
BHS5 Operational
DE1 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
SBG5 Operational
SGP1 Operational
SYD1 Operational
WAW1 Operational
UK1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
Containers & Orchestration || Managed Private Registry Operational
GRA Operational
DE Operational
BHS 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-1 Operational
US-WEST-OR-1 Operational
AP-SOUTH-MUM-1 Operational
Databases || Cassandra Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
SGP Operational
UK Operational
WAW Operational
Databases || MongoDB Operational
BHS Operational
DE Operational
GRA Operational
PAR Operational
SBG Operational
SGP Operational
UK Operational
WAW Operational
Databases || MySQL Operational
BHS Operational
DE Operational
GRA Operational
PAR Operational
SBG Operational
SGP Operational
UK Operational
WAW Operational
Databases || PostgreSQL Operational
BHS Operational
DE Operational
GRA Operational
PAR Operational
SBG Operational
SGP Operational
SYD Operational
UK Operational
WAW Operational
Databases || Valkey Operational
BHS Operational
DE Operational
GRA Operational
PAR Operational
SBG Operational
SGP Operational
UK Operational
WAW Operational
Data & Analytics || Data Platform Operational
Data & Analytics || Dashboards Operational
BHS Operational
DE Operational
GRA Operational
PAR Operational
SBG Operational
SGP Operational
UK Operational
WAW Operational
Data & Analytics || Kafka Degraded Performance
BHS Degraded Performance
DE Degraded Performance
GRA Degraded Performance
PAR Degraded Performance
SBG Degraded Performance
SGP Degraded Performance
UK Degraded Performance
WAW Degraded Performance
Data & Analytics || Kafka Connect Degraded Performance
BHS Degraded Performance
DE Degraded Performance
GRA Degraded Performance
PAR Degraded Performance
SBG Degraded Performance
SGP Degraded Performance
UK Degraded Performance
WAW Degraded Performance
Data & Analytics || Kafka MirrorMaker Degraded Performance
BHS Degraded Performance
DE Degraded Performance
GRA Degraded Performance
PAR Degraded Performance
SBG Degraded Performance
SGP Degraded Performance
UK Degraded Performance
WAW Degraded Performance
Data & Analytics || OpenSearch Operational
BHS Operational
DE Operational
GRA Operational
PAR Operational
SBG Operational
SGP Operational
UK Operational
WAW Operational
Identity, Security & Operations || Authentication Operational
Identity, Security & Operations || Barbican Operational
AP-SOUTH-MUM-1 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-1 Operational
US-EAST-VA-1 Operational
WAW1 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-NORTH Operational
AF-NORTH-LZ-RBA 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
Management || Horizon 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 Degraded Performance
RBX-ARCHIVE Degraded Performance
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
LocalZones || AP-SOUTH-MUM Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

[Global][Data & Analytics ] - Data Platform maintenance notification Feb 9, 2026 13:00-16: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 : 09/02/2026 13:00 UTC
End time : 09/02/2026 16: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 Jan 29, 2026 - 13:29 UTC

[BHS1][Network] - Load Balancer maintenance notification Feb 9, 2026 14:00-17:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our Public Cloud Load Balancer on BHS1 region.

Here are the details of the maintenance:
Start time : 09/02/2026 14:00 UTC
End time : 09/02/2026 17:00 UTC
Service impact : The API will be temporarily unavailable for 1 minute during the maintenance.
Service improvement : As part of our continuous improvement policy, we will be performing a maintenance on the Load Balancer service infrastructure. This maintenance is necessary to ensure the continued reliability and performance of our platform.
If you have any questions or concerns, please don't hesitate to reach out to our support team.

Thank you for your understanding.

Posted on Jan 29, 2026 - 16:08 UTC

[BHS3][Network] - Load Balancer maintenance notification Feb 10, 2026 13:00-16:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our Public Cloud Load Balancer on BHS3 region.

Here are the details of the maintenance:
Start time : 10/02/2026 13:00 UTC
End time : 10/02/2026 16:00 UTC
Service impact : The API will be temporarily unavailable for 1 minute during the maintenance.
Service improvement : As part of our continuous improvement policy, we will be performing a maintenance on the Load Balancer service infrastructure. This maintenance is necessary to ensure the continued reliability and performance of our platform.
If you have any questions or concerns, please don't hesitate to reach out to our support team.

Thank you for your understanding.

Posted on Jan 29, 2026 - 16:14 UTC

[GRA3][Network] - Load Balancer maintenance notification Feb 11, 2026 13:00-16:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our Public Cloud Load Balancer on GRA3 region.

Here are the details of the maintenance:
Start time : 11/02/2026 13:00 UTC
End time : 11/02/2026 16:00 UTC
Service impact : The API will be temporarily unavailable for 1 minute during the maintenance.
Service improvement : As part of our continuous improvement policy, we will be performing a maintenance on the Load Balancer service infrastructure. This maintenance is necessary to ensure the continued reliability and performance of our platform.
If you have any questions or concerns, please don't hesitate to reach out to our support team.

Thank you for your understanding.

Posted on Jan 29, 2026 - 16:17 UTC

[GRA1][Network] - Load Balancer maintenance notification Feb 12, 2026 13:00-16:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our Public Cloud Load Balancer on GRA1 region.

Here are the details of the maintenance:
Start time : 12/02/2026 13:00 UTC
End time : 12/02/2026 16:00 UTC
Service impact : The API will be temporarily unavailable for 1 minute during the maintenance.
Service improvement : As part of our continuous improvement policy, we will be performing a maintenance on the Load Balancer service infrastructure. This maintenance is necessary to ensure the continued reliability and performance of our platform.
If you have any questions or concerns, please don't hesitate to reach out to our support team.

Thank you for your understanding.

Posted on Jan 29, 2026 - 16:21 UTC

[AP-SOUTH-MUM-1][Network] - Load Balancer maintenance notification Feb 16, 2026 14:00-17:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our Public Cloud Load Balancer on AP-SOUTH-MUM-1 region.

Here are the details of the maintenance:
Start time : 16/02/2026 14:00 UTC
End time : 16/02/2026 17:00 UTC
Service impact : The API will be temporarily unavailable for 1 minute during the maintenance.
Service improvement : As part of our continuous improvement policy, we will be performing a maintenance on the Load Balancer service infrastructure. This maintenance is necessary to ensure the continued reliability and performance of our platform.
If you have any questions or concerns, please don't hesitate to reach out to our support team.

Thank you for your understanding.

Posted on Jan 29, 2026 - 16:32 UTC

[RBX/SBG][Containers & Orchestration] - Managed Rancher Service maintenance notification Feb 17, 2026 08:30-17:00 UTC

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

This may temporarily affect availability.

Start time : 17/02/2026 08:30 UTC
End time : 17/02/2026 17:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we need to upgrade Ranchers in version 2.10 to version 2.11. 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.28 and 1.29 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 Jan 06, 2026 - 15:42 UTC

[SBG7][Network] - Load Balancer maintenance notification Feb 17, 2026 14:00-17:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our Public Cloud Load Balancer on SBG7 region.

Here are the details of the maintenance:
Start time : 17/02/2026 14:00 UTC
End time : 17/02/2026 17:00 UTC
Service impact : The API will be temporarily unavailable for 1 minute during the maintenance.
Service improvement : As part of our continuous improvement policy, we will be performing a maintenance on the Load Balancer service infrastructure. This maintenance is necessary to ensure the continued reliability and performance of our platform.
If you have any questions or concerns, please don't hesitate to reach out to our support team.

Thank you for your understanding.

Posted on Jan 29, 2026 - 16:35 UTC

[SYD1][Network] - Load Balancer maintenance notification Feb 18, 2026 14:00-17:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our Public Cloud Load Balancer on SYD1 region.

Here are the details of the maintenance:
Start time : 18/02/2026 14:00 UTC
End time : 18/02/2026 17:00 UTC
Service impact : The API will be temporarily unavailable for 1 minute during the maintenance.
Service improvement : As part of our continuous improvement policy, we will be performing a maintenance on the Load Balancer service infrastructure. This maintenance is necessary to ensure the continued reliability and performance of our platform.
If you have any questions or concerns, please don't hesitate to reach out to our support team.

Thank you for your understanding.

Posted on Jan 29, 2026 - 16:37 UTC

[UK1][Network] - Load Balancer maintenance notification Feb 19, 2026 12:00-15:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our Public Cloud Load Balancer on UK1 region.

Here are the details of the maintenance:
Start time : 19/02/2026 12:00 UTC
End time : 19/02/2026 15:00 UTC
Service impact : The API will be temporarily unavailable for 1 minute during the maintenance.
Service improvement : As part of our continuous improvement policy, we will be performing a maintenance on the Load Balancer service infrastructure. This maintenance is necessary to ensure the continued reliability and performance of our platform.
If you have any questions or concerns, please don't hesitate to reach out to our support team.

Thank you for your understanding.

Posted on Jan 29, 2026 - 16:39 UTC
Feb 4, 2026

No incidents reported today.

Feb 3, 2026
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offer on the specific SBG5/SBG7 regions has been resolved.

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

We apologize for any inconvenience caused and appreciate your understanding.

Feb 3, 14:15 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 SBG5/SBG7 regions.

Here are some supplementary details :

Start time : 03/02/2026 10:05 UTC
Impacted Service(s) : Some instances in the SBG5/SBG7 regions are unreachable.
Customers Impact : Some customers are temporarily unable to access their instances.
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.

Feb 3, 10:29 UTC
Completed - The scheduled maintenance has been completed.
Feb 3, 10:13 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 3, 08: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 : 03/02/2026 08:00 UTC
End time : 03/02/2026 10: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.

Feb 2, 21:17 UTC
Feb 2, 2026
Completed - The scheduled maintenance has been completed.
Feb 2, 14:17 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 2, 12:00 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our Public Cloud Load Balancer on AP-SOUTHEAST-SYD-2 region.

Here are the details of the maintenance:
Start time : 02/02/2026 12:00 UTC
End time : 02/02/2026 15:00 UTC
Service impact : The API will be temporarily unavailable for 1 minute during the maintenance.
Service improvement : As part of our continuous improvement policy, we will be performing a maintenance on the Load Balancer service infrastructure. This maintenance is necessary to ensure the continued reliability and performance of our platform.
If you have any questions or concerns, please don't hesitate to reach out to our support team.

Thank you for your understanding.

Jan 20, 20:29 UTC
Completed - We are sorry to inform you that this maintenance is postponed to another date. We will keep you updated as soon as the date is fixed.
Feb 2, 09:49 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 2, 08: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 : 02/02/2026 08:00 UTC
End time : 02/02/2026 17:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we will deploy a new open-source REST catalog service to prepare for future integrations within our Data Platform offer.

Thank you for your understanding.

Jan 9, 17:42 UTC
Feb 1, 2026

No incidents reported.

Jan 31, 2026
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance has been resolved.

Start time : 31/01/2026 06:50 UTC
End time : 31/01/2026 06:58 UTC
Root Cause : A service disruption occurred due to an unexpected infrastructure failure

We apologize for any inconvenience caused and appreciate your understanding.

Jan 31, 07:04 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 GRA3 region.

Here are some supplementary details :

Start time : 31/01/2026 06:50 UTC
Impacted Service(s) : Some instances in the GRA3 regions are unreachable.
Customers Impact : Some customers are temporarily unable to access their compute instances.
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.

Jan 31, 06:57 UTC
Jan 30, 2026

No incidents reported.

Jan 29, 2026
Resolved - We would like to inform you that the incident on our Object Storage offering has now been resolved.

Here is detail for this incident :
Start time : 29/01/2026 04:30 UTC
End time : 29/01/2026 05:37 UTC
Root Cause : This incident was caused by this incident : https://public-cloud.status-ovhcloud.com/incidents/35fw13hg9xfk

We thank you for your understanding and patience throughout this incident.

Jan 29, 16:25 UTC
Monitoring - Service has been fully restored since 29/01/2026 05:37 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 29/01/2026 04:30 UTC
Impacted Service(s) : Object Storage was temporarily unavailable.
Customers Impact : Customers were temporarily getting 503 errors.
Root Cause : This incident is caused by this incident : https://public-cloud.status-ovhcloud.com/incidents/35fw13hg9xfk

We apologize for any inconvenience caused and appreciate your understanding.

Jan 29, 06:02 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Object Storage offer on the specific region SGP1.

Here are some supplementary details :

Start time : 29/01/2026 04:30 UTC
Impacted Service(s) : Object Storage is temporarily unavailable.
Customers Impact : Customers are temporarily getting 503 errors.
Root Cause : This incident is caused by this incident : https://public-cloud.status-ovhcloud.com/incidents/35fw13hg9xfk
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.

Jan 29, 05:13 UTC
Investigating - We are currently experiencing an event affecting our Object Storage offer.

Start time : 29/01/2026 04:30 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.

Jan 29, 05:06 UTC
Resolved - We would like to inform you that the incident on our Identity, Security & Operations offering has now been resolved.

Here is detail for this incident :
Start time : 29/01/2026 04:30 UTC
End time : 29/01/2026 05:37 UTC
Root Cause : This incident was caused by a software issue.

We thank you for your understanding and patience throughout this incident.

Jan 29, 16:24 UTC
Monitoring - Service has been fully restored since 29/01/2026 05:37 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 29/01/2026 04:30 UTC
Impacted Service(s) : The Identity, Security & Operations service was temporarily unavailable.
Customers Impact : Customers were temporarily unable to use the Identity, Security & Operations service in the SGP1, SGP2, and MUM regions.
Root Cause : This incident was caused by a software issue.

We apologize for any inconvenience caused and appreciate your understanding.

Jan 29, 06:07 UTC
Update - We are currently investigating an incident affecting our Identity, Security & Operations offering, which is causing temporary availability issue in the SGP1/SGP2/MUM regions.

Here are some supplementary details :

Start time : 29/01/2026 04:30 UTC
Impacted Service(s) : The Identity, Security & Operations service is temporarily unavailable.
Customers Impact : Customers are temporarily unable to use the Identity, Security & Operations service in the SGP1, SGP2, and MUM regions.
Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

Jan 29, 05:11 UTC
Investigating - We are currently experiencing an event affecting our Identity, Security & Operations offer.

Start time : 29/01/2026 04:30 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.

Jan 29, 04:47 UTC
Resolved - We would like to inform you that the incident on our Data Platform offer has now been resolved.

Here is detail for this incident :
Start time : 28/01/2026 12:16 UTC
End time : 28/01/2026 16:40 UTC
Root Cause : This incident was caused by this maintenance : https://public-cloud.status-ovhcloud.com//incidents/20z9wycm45ls

We thank you for your understanding and patience throughout this incident.

Jan 29, 13:13 UTC
Monitoring - Service has been fully restored since 28/01/2026 16:40 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 28/01/2026 12:16 UTC
Impacted Service(s) : Data Platform projects were temporarily unavailable.
Customers Impact : Customers were temporarily unable to create and use Data Platform projects

We apologize for any inconvenience caused and appreciate your understanding.

Jan 28, 17:08 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data Platform offer.

Here are some supplementary details :

Start time : 28/01/2026 12:16 UTC
Impacted Service(s) : Data Platform projects are temporarily unavailable.
Customers Impact : Customers are temporarily unable to create and use Data Platform projects
Root Cause : This incident is caused by this maintenance : https://public-cloud.status-ovhcloud.com//incidents/20z9wycm45ls
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.

Jan 28, 13:54 UTC
Investigating - We are currently experiencing an event affecting our Data Platform offer.

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.

Jan 28, 13:45 UTC
Completed - The maintenance has been postponed and will be re-scheduled.
Jan 29, 12:54 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 : 02/02/2026 13:00 UTC
End time : 02/02/2026 16: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.

Jan 27, 22:51 UTC
Jan 28, 2026
Completed - The scheduled maintenance has been completed.
Jan 28, 16:42 UTC
Update - This maintenance caused an incident on Data Platform projects: https://public-cloud.status-ovhcloud.com/incidents/1d6rybkgm95z.

We apologize for any inconvenience caused.

Jan 28, 13:56 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 28, 09:00 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our public cloud infrastructure.

Start time : 28/01/2026 09:00 UTC
End time : 28/01/2026 18:00 UTC
Service impact : Kubernetes will progressively roll out the change across approximately 50 nodes, with an estimated duration of 3 minutes per node.
Pods will be automatically rolled out to ensure minimal service downtime.

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.

Jan 15, 20:47 UTC
Resolved - We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/01/2026 09:00 UTC
End time : 28/01/2026 09:28 UTC
Root Cause : This incident was caused by a software issue.

We apologize for any inconvenience caused and appreciate your understanding.

Jan 28, 09:56 UTC
Investigating - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offering.

Here are some supplementary details :

Start time : 28/01/2026 09:00 UTC
Impacted Service(s) : The data platform is in degraded mode. Customer projects are temporarily unavailable.
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.

Jan 28, 09:21 UTC
Jan 27, 2026

Unresolved incident: [RBX-ARCHIVE][Storage] - Cold Archive incident notification.

Jan 26, 2026
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance has been resolved.

Start time : 26/01/2026 10:08 UTC
End time : 26/01/2026 18:10 UTC
Root Cause : A service disruption occurred due to an unexpected infrastructure failure.

We apologize for any inconvenience caused and appreciate your understanding.

Jan 26, 18:12 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 GRA11 region.

Here are some supplementary details :

Start time : 26/01/2026 10:08 UTC
Impacted Service(s) : Some instances in the GRA11 regions are unreachable.
Customers Impact : Some customers are temporarily unable to access their compute instances.
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.

Jan 26, 15:02 UTC
Update - We are continuing to investigate this issue.
Jan 26, 11:22 UTC
Investigating - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific GRA11 regions.

Here are some supplementary details :

Start time : 26/01/2026 10:08 UTC
Impacted Service(s) : Some instances in the GRA11 regions are unreachable.
Customers Impact : Some customers are temporarily unable to access their compute instances.
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.

Jan 26, 11:12 UTC
Completed - The scheduled maintenance has been completed.
Jan 26, 13:29 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 26, 13:00 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our public cloud infrastructure.

Start time : 26/01/2026 13:00 UTC
End time : 26/01/2026 16: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.

Jan 15, 20:18 UTC
Resolved - We would like to inform you that the incident on our Storage offering has now been resolved.

Here is detail for this incident :
Start time : 26/01/2026 12:45 UTC
End time : 26/01/2026 13:00 UTC
Root Cause : A service disruption occurred due to an unexpected infrastructure failure.

We thank you for your understanding and patience throughout this incident.

Jan 26, 13:21 UTC
Investigating - We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the GRA3 Region.

Here are some supplementary details :
Start time : 26/01/2026 12:45 UTC
Impacted Service(s) : Some Volume Snapshot (Ceph) database is temporarily unavailable.
Customers Impact : Customers are temporarily unable to access their data located in the specified region.
Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

Jan 26, 12:57 UTC
Jan 25, 2026

No incidents reported.

Jan 24, 2026

No incidents reported.

Jan 23, 2026
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance has been resolved.

Start time : 23/01/2026 16:38 UTC
End time : 23/01/2026 17:25 UTC
Root Cause : This incident was caused by a network equipment issue.

We apologize for any inconvenience caused and appreciate your understanding.

Jan 23, 17:45 UTC
Identified - We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue on some instances in the BHS1 region.

Here are some supplementary details :

Start time : 23/01/2026 16:38 UTC
Impacted Service(s) : Some instances in BHS1 region were temporarily unavailable.
Customers Impact : Some customers were temporarily unable to access and use their instances in the specified region.
Root Cause : This incident is caused by a network equipment issue.
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.

Jan 23, 16:49 UTC
Jan 22, 2026

No incidents reported.

Jan 21, 2026
Completed - We would like to inform you that the maintenance on our cooling infrastructure is now completed.
All services are operational.

Thank you for your patience throughout this maintenance.

Jan 21, 11:03 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 21, 10: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 : 21/01/2026 10:00 UTC
End time : 21/01/2026 12: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.

Jan 20, 19:05 UTC
Resolved - We would like to inform you that the incident on our Storage offering has now been resolved.

Here is detail for this incident :
Start time : 20/01/2026 20:45 UTC
End time : 20/01/2026 20:53 UTC
Root Cause : This incident was caused by another incident: https://network.status-ovhcloud.com/incidents/h5f1d9s2kl46

We thank you for your understanding and patience throughout this incident.

Jan 21, 02:59 UTC
Monitoring - Service has been fully restored since 20/01/2026 20:53 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 20/01/2026 20:45 UTC
Impacted Service(s) : Object Storage S3.
Customers Impact : Customers have experienced connection problems while trying to access Object Storage S3 in WAW.
Root Cause : This incident is caused by another incident: https://network.status-ovhcloud.com/incidents/h5f1d9s2kl46

We apologize for any inconvenience caused and appreciate your understanding.

Jan 20, 21:15 UTC
Investigating - We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the region WAW.

Here are some supplementary details :

Start time : 20/01/2026 20:45 UTC
Impacted Service(s) : Object Storage S3.
Customers Impact : Customers may experience connection problems while trying to access Object Storage S3 in WAW.
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.

Jan 20, 20:59 UTC