OVHcloud Public Cloud Status

Current status
Legend
  • Operational
  • Degraded performance
  • Partial Outage
  • Major Outage
  • Under maintenance
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : As you know, a aws SDKs upgrade added a new cheksum enforcement.
This upgrade leads in return of "InvalidArgument" on different Object operations.
Since then, our development team has been working hard on support for this new checksum.
This takes time because these developments affect data integrity checks.
We are therefore taking every possible precaution by adding numerous Q&A tests to ensure that the fix's deployment is carried out without any impact.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

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

Apr 25, 2025 - 13:42 UTC
Update - We are continuing to work on a fix for this issue.
Apr 17, 2025 - 06:51 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : We have completed our development and the fix is ​​currently being tested in our Q&A process.
Testing process is especially long to prevent any regression while fixing 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.

Apr 10, 2025 - 08:46 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 still working on fix.

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

Mar 03, 2025 - 12:37 UTC
Update - We are continuing to work on a fix for this issue.
Feb 06, 2025 - 19:10 UTC
Identified - We have determined the origin of the incident affecting our Object Storage S3 offer.

Here are some supplementary details :
Start time : 01/01/2025 00:00 UTC
Impacted Service(s) : Object Storage S3
Customers Impact : Requests to our Object Storage endpoint could return the error "InvalidArgument", on different Object operations.
Root Cause : Following a recent AWS SDK upgrade, this issue is due to a new checksum enforcement in those SDKs.
Unsupported headers are:
- x-amz-content-sha256 with value STREAMING-UNSIGNED-PAYLOAD-TRAILER
- x-amz-sdk-checksum-algorithm with value CRC32
Workaround A workaround is to downgrade the version, until the feature is implemented on our side.
Max supported versions:
- boto3 1.35.99
- legacy aws cli 1.36.40
- aws cli 2.22.35
- aws-sdk-go 1.72.3
- aws-sdk-java 2.29.52
- aws-sdk-js-v3 3.726.1
- aws-sdk-net 3.7.962.0
- aws-sdk-php 3.336.15
- aws-sdk-ruby 1.177.0
Ongoing Actions : The incident has been identified and our teams are mobilized 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 23, 2025 - 15:11 UTC
Investigating - We are currently experiencing an event affecting our Object Storage S3 offer.
Start time : 01/01/2025 00:00 UTC

Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

Jan 23, 2025 - 14:51 UTC
Identified - We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details :
Start time : 25/03/2025 09:00 UTC
Impacted Service(s) : Object storage offer
Customers Impact :Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted.
Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted.
Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been.
In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates.
Root Cause : This incident is caused by a software issue.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

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

Apr 25, 2025 - 08:47 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : Our technical team is still proceeding with the final fix. This still does not have any impact on customers.
Ongoing Actions : Our teams are currently monitoring the situation.

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

Apr 23, 2025 - 04:38 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : Our technical team will proceed with the final fix on 22/04/2025 21:00 UTC. This will have no impact on customers.
Ongoing Actions : Our teams are currently monitoring the situation.

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

Apr 22, 2025 - 14:06 UTC
Monitoring - We have determined the origin of the incident affecting one of storage backend in the specific region.

Here are some supplementary details :
Start time : 22/04/2025 12:17 UTC
Impacted Service(s) : Block Storage
Customers Impact : No more impact observed since 22/04/2025 12:41 UTC.
During the period of impact, some customers were temporarily unable to access and use their volumes.
Therefore, customers that had access to their volumes were facing slowness on accessing them.
Root Cause : This incident was caused by a software issue.
Ongoing Actions : Our teams are currently monitoring the situation.

We apologize for any inconvenience caused and appreciate your understanding.

Apr 22, 2025 - 12:51 UTC
Investigating - We are currently experiencing an event affecting our Block Storage offer in GRA3.
Start time : 22/04/2025 12:17 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.

Apr 22, 2025 - 12:20 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 22, 2025 - 08:00 UTC
Scheduled - As part of our continuous improvement plan, maintenance is scheduled on network services globally.

Start time : 22/04/2025 08:00 UTC
End time : 25/04/2025 18:00 UTC
Service impact : Debian 10 and Debian 11 IPv6 will be broken on newly created instances.
Service improvement : As part of our continuous improvement plan, a maintenance is scheduled on OpenStack public network services globally.

We are going to update the IPv6 network metadata information given to instances.
The previous metadata was containing wrong data (subnet mask), leading to wrong cloud-init IPv6 network auto configuration.
The new metadata result will contains all necessary data to give proper IPv6 configuration through cloud-init.

However, both Debian 10 and Debian 11 images won't be able to configure IPv6 correctly, so you may have to configure IPv6 manually for these following this documentation:
EN: https://help.ovhcloud.com/csm/en-ie-public-cloud-network-ipv6-configuration?id=kb_article_view&sysparm_article=KB0050178
FR: https://help.ovhcloud.com/csm/fr-public-cloud-network-ipv6-configuration?id=kb_article_view&sysparm_article=KB0050183

Apr 22, 2025 08:00 - Apr 25, 2025 18:00 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 Under Maintenance
BHS1 Operational
BHS3 Operational
BHS5 Under Maintenance
Compute - Instance || ERI Under Maintenance
UK1 Under Maintenance
Compute - Instance || EU-WEST-PAR Under Maintenance
EU-WEST-PAR-A Under Maintenance
EU-WEST-PAR-B Under Maintenance
EU-WEST-PAR-C Under Maintenance
Compute - Instance || GRA Under Maintenance
GRA1 Under Maintenance
GRA3 Under Maintenance
GRA5 Under Maintenance
GRA7 Under Maintenance
GRA9 Under Maintenance
GRA11 Under Maintenance
Compute - Instance || India Under Maintenance
AP-SOUTH-MUM-1 Under Maintenance
Compute - Instance || LIM Under Maintenance
DE1 Under Maintenance
Compute - Instance || RBX Under Maintenance
RBX-A Under Maintenance
Compute - Instance || SGP Under Maintenance
SGP1 Under Maintenance
SGP2 Under Maintenance
Compute - Instance || SBG Under Maintenance
SBG5 Under Maintenance
SBG7 Under Maintenance
Compute - Instance || SYD Under Maintenance
SYD1 Under Maintenance
AP-SOUTHEAST-SYD-2 Under Maintenance
Compute - Instance || USA Under Maintenance
US-EAST-VA-1 Under Maintenance
US-WEST-OR-1 Under Maintenance
Compute - Instance || WAW Under Maintenance
WAW1 Under Maintenance
Containers & Orchestration || Load Balancer 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
SBG5 Operational
SBG7 Operational
SGP1 Operational
SGP2 Operational
SYD1 Operational
SYD2 Operational
SYD3 Operational
UK1 Operational
WAW1 Operational
WAW2 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
Databases || Cassandra Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
UK Operational
WAW Operational
Databases || M3 Aggregator Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
UK Operational
WAW Operational
Databases || M3DB Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
UK Operational
WAW Operational
Databases || MongoDB Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
UK Operational
WAW Operational
Databases || MySQL Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
UK Operational
WAW Operational
Databases || PostgreSQL Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
SGP Operational
SYD Operational
UK Operational
WAW Operational
Databases || Caching Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
UK Operational
WAW Operational
Data & Analytics || Data Processing Operational
GRA Operational
Data & Analytics || Dataplatform Operational
Data & Analytics || Grafana Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
UK Operational
WAW Operational
Data & Analytics || Kafka Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
UK Operational
WAW Operational
Data & Analytics || Kafka Connect Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
UK Operational
WAW Operational
Data & Analytics || Kafka MirrorMaker Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
UK Operational
WAW Operational
Data & Analytics || Logs Data Platform Operational
BHS Operational
GRA Operational
Data & Analytics || OpenSearch Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
UK Operational
WAW Operational
Identity, Security & Operations || Key Management Service Operational
BHS Operational
RBX Operational
SBG Operational
YYZ Operational
LocalZones || AF-NORTH Operational
AF-NORTH-LZ-RBA Operational
LocalZones || EU-CENTRAL Operational
EU-CENTRAL-LZ-PRG Operational
LocalZones || EU-NORTH Operational
EU-NORTH-LZ-OSL Operational
EU-NORTH-LZ-STO Operational
LocalZones || EU-SOUTH 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-MRS Operational
EU-WEST-LZ-VIE Operational
EU-WEST-LZ-ZRH 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-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
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
SYD3 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
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
SYD3 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
AP-SOUTH-MUM-1 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
SYD3 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
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
SYD3 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
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
SYD3 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
Storage || Block storage Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA6 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
SYD3 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
Storage || Cloud Archive Operational
DE Operational
GRA Operational
UK Operational
WAW Operational
BHS Operational
SYD Operational
SGP Operational
US-EAST-VA Operational
US-WEST-OR Operational
Storage || Cold Archive Operational
RBX-ARCHIVE Operational
Storage || Instance Backup Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
SYD3 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
Storage || Object storage Partial Outage
BHS Partial Outage
GRA Partial Outage
DE Partial Outage
RBX Partial Outage
SBG Partial Outage
SGP Partial Outage
SYD Partial Outage
UK Partial Outage
US-EAST-VA-1 Partial Outage
US-WEST-OR-1 Partial Outage
WAW Partial Outage
YYZ Partial Outage
LIM Partial Outage
AP-SOUTH-MUM-1 Degraded Performance
EU-WEST-PAR-A Degraded Performance
EU-WEST-PAR-B Degraded Performance
EU-WEST-PAR-C Degraded Performance
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
SYD2 Operational
SYD3 Operational
UK1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
WAW1 Operational
Storage || Volume Snapshot (Ceph) Operational
DE1 Operational
GRA1 Operational
GRA2 Operational
GRA3 Operational
GRA5 Operational
GRA6 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
SYD3 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
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

[BHS5][Public Cloud] - Internal databases update Apr 28, 2025 07:00-15:00 UTC

As part of our continuous improvement plan, maintenance is scheduled for update the Internal databases on BHS5.

Start time : 28/04/2025 07:00 UTC
End time : 28/04/2025 15:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we will be doing a public cloud service maintenance.

Thank you for your understanding.

Posted on Apr 24, 2025 - 14:34 UTC

[GLOBAL][Databases] - Block Storage incident notification Apr 29, 2025 09:30-10:00 UTC

As part of our continuous improvement plan, maintenance is scheduled on our Block Storage offer.

Start time : 29/04/2025 09:30 UTC
End time : 29/04/2025 10:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Block Storage offer.

Thank you for your understanding.

Posted on Apr 16, 2025 - 20:30 UTC

[RBX/SBG][Public Cloud] - Rancher upgrade May 5, 2025 08:00-16:00 UTC

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

Start time : 05/05/2025 08:00 UTC
End time : 05/05/2025 16:00 UTC
Service impact : None
Service improvement : Following our continuous improvement policy, we will be doing an upgrade only for Ranchers version 2.7.15.
Customers about will be contacted by mail.

Thank you for your understanding.

Posted on Apr 10, 2025 - 21:28 UTC

[VA1][Public Cloud] - Registries upgrade May 6, 2025 08:30-16:30 UTC

As part of our continuous improvement plan, maintenance is scheduled on our Managed Private Registry.

Start time : 06/05/2025 08:30 UTC
End time : 06/05/2025 16:30 UTC
Service impact : The upgrade of the Harbor version will set Harbor in read-only mode (only pull will be allowed) for 1 or 2mn.
Service improvement : Following our continuous improvement policy, we are rolling out an upgrade of registries.

Thank you for your understanding.

Posted on Apr 10, 2025 - 20:23 UTC
Apr 25, 2025

Unresolved incidents: [GLOBAL][Storage] - Object storage incident notification, [GLOBAL][Object Storage] - Amazon S3 SDK compatibility inconsistencies with Object Storage Standard/High Performance.

Apr 24, 2025
Completed - The scheduled maintenance has been completed.
Apr 24, 17:15 UTC
Update - The current maintenance is taking more time than expected.
Below you can find the new information regarding the operation.

Start time : 24/04/2025 08:30 UTC
End time : 24/04/2025 17:15 UTC
Service impact : Registries in plan SMALL will have 1 minute of unavailability.
Service improvement : Following our continuous improvement policy, we are upgrading the underlying infrastructure.

Thank you for your understanding.

Apr 24, 16:54 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 24, 08:30 UTC
Scheduled - As part of our continuous improvement plan, maintenance is scheduled on our Managed Private Registry.

Start time : 24/04/2025 08:30 UTC
End time : 24/04/2025 16:30 UTC
Service impact : Registries in plan SMALL will have 1 minute of unavailability.
Service improvement : Following our continuous improvement policy, we are upgrading the underlying infrastructure

Thank you for your understanding.

Apr 10, 20:35 UTC
Apr 23, 2025
Resolved - We would like to inform you that the incident on our AI Deploy application has now been resolved.

Here is detail for this incident :
Start time : 23/04/2025 08:18 UTC
End time : 23/04/2025 08:58 UTC
Impacted Service(s) : AI Deploy application was temporarily unavailable.
Customers Impact : Customers were temporarily unable to access their instances through AI Deploy application.
However, instances were still operational during the incident.
Root Cause : This incident was caused by a network issue.

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

Apr 23, 15:23 UTC
Resolved - We would like to inform you that the incident on our AI Deploy application has now been resolved.

Here is detail for this incident :
Start time : 23/04/2025 13:14 UTC
End time : 23/04/2025 13:54 UTC
Impacted Service(s) : AI Deploy application was temporarily unavailable.
Customers Impact : Customers were temporarily unable to access their instances through AI Deploy application.
However, instances were still operational during the incident.
Root Cause : This incident was caused by a network issue.

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

Apr 23, 15:19 UTC
Completed - The scheduled maintenance has been completed.
Apr 23, 15:10 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 23, 14:15 UTC
Scheduled - As part of our continuous improvement plan, maintenance is scheduled on the API of the LocalZone US-EAST-LZ-CHI-A.

This will temporarily affect availability.

Start time : 23/04/2025 14:15 UTC
End time : 23/04/2025 15:15 UTC
Service impact : During the maintenance, the API will be unreachable.
Service improvement : Following our continuous improvement policy of our products and services, we will carry out a maintenance on the API infrastructure.

Thank you for your understanding.

Apr 22, 13:28 UTC
Resolved - We would like to inform you that the incident on our Public cloud offer has now been resolved.

Here is detail for this incident :
Start time : 23/04/2025 08:43 UTC
End time : 23/04/2025 12:37 UTC
Root Cause : A service disruption occured due to an unexpected infrastructure failure.

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

Apr 23, 12:50 UTC
Update - We are currently experiencing an incident affecting our Public cloud offering, which is causing temporary availability issues in the region BHS1&3.

Here is detail for this incident :
Start time : 23/04/2025 08:43 UTC
Impacted Service(s) : Some hosts are temporarily unavailable in region BHS1 & 3.
Customers Impact : Some instances are temporarily unavailable.
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.

Apr 23, 09:07 UTC
Investigating - We are currently experiencing an event affecting our Public cloud offer.
Start time : 23/04/2025 08:43 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.

Apr 23, 08:59 UTC
Apr 22, 2025
Completed - The scheduled maintenance has been completed.
Apr 22, 15:55 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 22, 08:30 UTC
Scheduled - As part of our continuous improvement plan, maintenance is scheduled on our Managed Private Registry.

Start time : 22/04/2025 08:30 UTC
End time : 22/04/2025 16:30 UTC
Service impact : Registries in plan SMALL will have 1 minute of unavailability.
Service improvement : Following our continuous improvement policy, we are upgrading the underlying infrastructure.

Thank you for your understanding.

Apr 10, 20:49 UTC
Resolved - We would like to inform you that the incident on the Block storage offer has now been resolved.

Here is detail for this incident :
Start time : 21/04/2025 23:25 UTC
End time : 22/04/2025 00:30 UTC
Root Cause : A service disruption occured due to an unexpected software malfunction.

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

Apr 22, 00:55 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 22, 00:34 UTC
Update - We are continuing to work on a fix for this issue.
Apr 22, 00:32 UTC
Update - We are continuing to work on a fix for this issue.
Apr 22, 00:30 UTC
Identified - We have determined the origin of the incident affecting our Block Storage offer, in GRA3

Here are some supplementary details :
Start time : 21/04/2025 23:25 UTC
Impacted Service(s) : GRA3 region
Customers Impact : Some Volumes in GRA3 are temporarily unavailable due to a storage malfunction .
Ongoing Actions : The incident has been identified and our teams are mobilized to restore service as quickly as possible.

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

Apr 22, 00:29 UTC
Investigating - We are currently experiencing an event affecting our Block Storage offer in GRA3.
Start time : 21/04/2025 23:25 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.

Apr 22, 00:15 UTC
Apr 21, 2025

No incidents reported.

Apr 20, 2025

No incidents reported.

Apr 19, 2025

No incidents reported.

Apr 18, 2025

No incidents reported.

Apr 17, 2025
Resolved - We would like to inform you that the incident on our Public Cloud offer, have been resolved
Start Time : 17/04/2025 01:35 UTC
End Time : 17/04/2025 04:00 UTC
Root Cause : This incident is caused by https://network.status-ovhcloud.com/incidents/wqq5qxpcsszn.

We thank you for your understanding and patience throughout this incident

Apr 17, 13:35 UTC
Update - New customers Impact : Customers were unable to connect to workload running on GRA, neither start or stop workloads on all the 3 AI Machine products. Running workloads were still up after incident. It started at 01:39 and ended at 02:09 UTC.
Apr 17, 09:15 UTC
Update - We are continuing to monitor for any further issues.
Apr 17, 09:06 UTC
Monitoring - Please find below an update on the situation:
Update : No more impact observed on Public Cloud since 17/04/2025 04:00 UTC
Ongoing Actions : Our teams are still working and monitoring the problem.
Root Cause : This incident is caused by https://network.status-ovhcloud.com/incidents/wqq5qxpcsszn .

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

Apr 17, 04:42 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : No more impact observed for Block Storage on GRA1/3/5/7/9/11.
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

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

Apr 17, 03:26 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 unable to create workflows.
Instabilities are seen on Public Cloud API.
Ongoing Actions : The incident has been identified and our teams are mobilized to restore service as quickly as possible.

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

Apr 17, 03:09 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : No more impact observed for Block Storage on GRA1/3/5/7/9.
Our teams are currently working all the impacted services and on GRA11 Block Storage.
Ongoing Actions : The incident has been identified and our teams are mobilized to restore service as quickly as possible.

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

Apr 17, 02:54 UTC
Identified - We have determined the origin of the incident affecting our Public Cloud offer on the specific region.

Here are some supplementary details :
Start time : 17/04/2025 01:35 UTC
Impacted Service(s) : Public Cloud offers
Customers Impact : Customers are temporarily unable to access and use their services in GRA.
Root Cause : This incident is caused by a network equipment issue during the maintenance https://network.status-ovhcloud.com/incidents/myfn82jp00k5 .
Ongoing Actions : The incident has been identified and our teams are mobilized to restore service as quickly as possible.

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

Apr 17, 02:14 UTC
Investigating - We are currently experiencing an event affecting our Public Cloud offer.

Start time : 17/04/2025 01:35 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.

Apr 17, 01:52 UTC
Resolved - We would like to inform you that the incident on the mongoDB offer has now been resolved.

Here is detail for this incident :
Start time : 17/04/2025 01:35 UTC
End time :17/04/2025 08:30 UTC
Root Cause : This incident is caused by https://network.status-ovhcloud.com/incidents/wqq5qxpcsszn

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

Apr 17, 12:39 UTC
Update - The incident is still ongoing. We would like to assure you that we are doing our utmost to resolve this situation as quickly as possible.

As soon as the situation evolves or the incident is resolved, we will keep you informed.

Thank you for your understanding

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

Please find below an update on the situation:
Update : Fetching metrics and edition of service are operational again for mongodb services in region GRA
Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

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

Apr 17, 08:11 UTC
Identified - We have determined the origin of the incident affecting our Public Cloud offer on the specific region.

Here are some supplementary details :
Start time : 17/04/2025 01:35 UTC
Impacted Service(s) : Mongo DB offers
Customers Impact : Delay in delivery of new services is observed in region GRA.
Fetching metrics and edition of service are unreachable for mongodb services in region GRA
Related incident : https://public-cloud.status-ovhcloud.com/incidents/wnjcmhtl1ffz .
Ongoing Actions : The incident has been identified and our teams are mobilized to restore service as quickly as possible.

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

Apr 17, 07:11 UTC
Apr 16, 2025
Completed - The scheduled maintenance has been completed.
All services are operational.

Apr 16, 19:42 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 16, 08:30 UTC
Scheduled - As part of our continuous improvement plan, maintenance is scheduled on our public cloud offer.

This may temporarily affect availability.
Start time : 16/04/2025 08:30 UTC
End time : 16/04/2025 22:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we will do a maintenance operation on our network equipment related to Managed Rancher Service products in order to fix a CVE.

Thank you for your understanding.

Apr 9, 00:18 UTC
Completed - The scheduled maintenance has been completed.
All services are operational. There has been no impact since 16/04/2025 17:30 UTC.

Apr 16, 18:36 UTC
Update - The maintenance must have been extended.
End time : 16/04/2025 17:30 UTC

Thank you for your understanding.

Apr 16, 15:41 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 16, 08:00 UTC
Scheduled - As part of our continuous improvement plan, maintenance is scheduled on our Managed Private Registry.

Start time : 16/04/2025 08:00 UTC
End time : 16/04/2025 16:00 UTC
Service impact : The upgrade of the Harbor version will set Harbor in read-only mode (only pull will be allowed) for 1 or 2mn.
Service improvement : Following our continuous improvement policy, we are rolling out an upgrade of registries.

Thank you for your understanding.

Mar 5, 23:21 UTC
Completed - The maintenance is completed, all services are operational.
Apr 16, 08:47 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 16, 08:15 UTC
Scheduled - As part of our continuous improvement plan, maintenance is scheduled on the API of the LocalZone EU-CENTRAL-LZ-PRG-A.

This will temporarily affect availability.
Start time : 16/04/2025 08:15 UTC
End time : 16/04/2025 09:15 UTC
Service impact : The API service will be temporarily unavailable for a few minutes during maintenance.
Service improvement : Following our continuous improvement policy of our products and services, we will carry out a maintenance on the API infrastructure.

Thank you for your understanding.

Apr 14, 20:33 UTC
Resolved - We would like to inform you that the incident on Block Storage High speed Gen2 has now been resolved.

Here is detail for this incident :
Start time : 15/05/2025 23:30 UTC
End time : 15/05/2025 23:50 UTC
Impacted Service(s) : Access to data was temporarily unavailable for some customers.
Customers Impact : Some customers having High speed Gen2 speed for their Block Storage were temporarily unable to access their data.
Root Cause : This incident was caused by a hardware issue on storage node.

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

Apr 16, 00:26 UTC
Investigating - We are currently experiencing an event affecting our Block Storage High speed Gen2 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.

Apr 15, 23:50 UTC
Apr 15, 2025
Apr 14, 2025
Completed - Maintenance will have to be rescheduled.
We apologise for any inconvenience caused.

Apr 14, 14:44 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 14, 14:15 UTC
Scheduled - As part of our continuous improvement plan, maintenance is scheduled on the API of the LocalZone US-EAST-LZ-CHI-A.

This will temporarily affect availability.

Start time : 14/04/2025 14:15 UTC
End time : 14/04/2025 15:15 UTC
Service impact : During the maintenance, the API will be unreachable.
Service improvement : Following our continuous improvement policy of our products and services, we will carry out a maintenance on the API infrastructure.

Thank you for your understanding.

Apr 11, 00:00 UTC
Completed - The scheduled maintenance has been completed.
Apr 14, 14:34 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 14, 08:00 UTC
Scheduled - As part of our continuous improvement plan, we are deploying a new infrastructure for the Managed Kubernetes product.

Start time : 14/04/2025 08:00 UTC
End time : 14/04/2025 15:30 UTC
Service impact : During the intervention, the management API of Managed Kubernetes clusters may return errors.
Service improvement : Due to our continuous improvement process, we are deploying a new infrastructure for the Managed Kubernetes product.
Workloads currently deployed on MKS cluster are not impacted by this intervention.

Thank you for your understanding.

Apr 10, 23:47 UTC
Resolved - We would like to inform you that the incident in GRA9 region has now been resolved.

Here is detail for this incident :
Start time : 14/04/2025 06:39 UTC
End time : 14/04/2025 09:30 UTC
Root Cause : This incident was caused by an infrastructure equipment issue.

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

Apr 14, 10:12 UTC
Update - We are currently experiencing an incident affecting our Data & Analytics offering, which is causing temporary availability issues in the GRA9 region.

Here is detail for this incident :
Start time : 14/04/2025 06:39 UTC
Impacted Service(s) : Two nodes working instead of three, the workload in the region can be high for the jobs.
Customers Impact : You may experience some delays with jobs on our Kubernetes infrastructure.
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.

Apr 14, 08:28 UTC
Investigating - We are currently experiencing an incident affecting our Data & Analytics offer.
Start time : 14/04/2025 06:39 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.

Apr 14, 07:51 UTC
Apr 13, 2025

No incidents reported.

Apr 12, 2025
Resolved - We would like to inform you that the incident on Object Storage offer has now been resolved.

Here is detail for this incident :
Start time : 12/04/2025 05:13 UTC
End time : 12/04/2025 13:30 UTC
Root Cause : This incident was caused by this incident: https://bare-metal-servers.status-ovhcloud.com/incidents/sq1nf48jmls1.

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

Apr 12, 13:53 UTC
Identified - We have determined the origin of the incident affecting our Object Storage offer on the specific region.

Here are some supplementary details :
Start time : 12/04/2025 05:13 UTC
Impacted Service(s) : Object Storage
Customers Impact : Some customers might be getting 503 errors while trying to access their objects.
Root Cause : This incident is caused by this incident: https://bare-metal-servers.status-ovhcloud.com/incidents/sq1nf48jmls1.
Ongoing Actions : The incident has been identified and our teams are mobilized to restore service as quickly as possible.

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

Apr 12, 05:50 UTC
Apr 11, 2025

No incidents reported.