OVH.com logo
OVHcloud Public Cloud Status

Current status
Legend
  • Operational
  • Degraded performance
  • Partial Outage
  • Major Outage
  • Under maintenance
[DE][Public Cloud] - Object storage S3 incident notification
Identified - We would like to inform you that we are having an ongoing incident.
Our teams are working tirelessly to resolve this incident once and for all.

Start time : 11/09/2024 08:25 UTC
Service impact : Due to this incident some customers may encounter accessibility problems with some of their objects.
Ongoing actions : Our technical teams will conduct a series of checks to guarantee the functionality of all the hardware.
During the intervention, customers may experience difficulties in accessing some of their services.
Further information will be provided in the near future.

As soon as the situation evolves or the incident is resolved, we will keep you informed.
Sep 18, 2024 - 17:12 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 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 || GRA Operational
GRA1 Operational
GRA2 Operational
GRA3 Operational
GRA4 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 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
SYD3 Operational
Compute - Instance || USA Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
Compute - Instance || WAW Operational
WAW1 Operational
Containers & Orchestration || Load Balancer Operational
BHS5 Operational
DE1 Operational
GRA5 Operational
GRA7 Operational
GRA9 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
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
GRA Operational
Databases || Grafana Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
UK Operational
WAW Operational
Databases || Kafka Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
UK Operational
WAW Operational
Databases || Kafka Connect Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
UK Operational
WAW Operational
Databases || Kafka MirrorMaker 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 || OpenSearch Operational
BHS Operational
DE Operational
GRA Operational
SBG Operational
UK Operational
WAW Operational
Databases || PostgreSQL Operational
BHS Operational
DE Operational
GRA Operational
SBG 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 || Logs Data Platform Operational
BHS Operational
GRA Operational
Identity, Security & Operations || Key Management Service Operational
RBX Operational
SBG Operational
LocalZones || Global Services Operational
AMS Operational
BRU Operational
CHI Operational
DAL Operational
MAD Operational
MIL Operational
MRS Operational
NYC Operational
PRG Operational
ZRH Operational
Management || Horizon Operational
Network || FailoverIP 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
Network || Load Balancer 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
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
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
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
Storage || Object storage Partial Outage
BHS Operational
GRA Operational
DE Partial Outage
RBX Operational
SBG Operational
SGP Operational
SYD Operational
UK Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
WAW Operational
YYZ 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
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
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
[SGP2][Public Cloud] - Network maintenance notification Oct 17, 2024 13:00-19:00 UTC
As part of our continuous improvement plan, maintenance is scheduled on our Public Cloud network.

Start time : 17/10/2024 13:00 UTC
End time : 17/10/2024 19:00 UTC
Service impact : None
Service improvement : Following our continuous improvement policy, we will be doing a maintenance on multiple network equipment.

Thank you for your understanding.
Posted on Oct 10, 2024 - 18:58 UTC
Past Incidents
Oct 15, 2024

No incidents reported today.

Oct 14, 2024

No incidents reported.

Oct 13, 2024

No incidents reported.

Oct 12, 2024
[GRA11][Public Cloud] - Limited availability of B3 resources
Resolved - Start time : 11/10/2024 08:00 UTC
End time : 11/10/2024 20:20 UTC
Root cause : This incident was due to storage equipment issue.
We would like to inform you that the incident have been resolved and the situation is back to normal.

We thank you for your understanding and patience throughout this incident
Oct 12, 06:58 UTC
Update - We are continuing to work on a fix for this issue.
Oct 12, 05:16 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
Oct 11, 20:35 UTC
Update - The gradual return to an operational state is underway.
Oct 11, 16:44 UTC
Update - We are continuing to work on a fix for this issue.
Oct 11, 16:33 UTC
Update - Customers may face difficulties to order new B3 on MKS.
Oct 11, 13:29 UTC
Identified - The issue has been identified and a fix is being implemented.
Oct 11, 13:11 UTC
Investigating - An incident is in progress on our Compute-intance offer.

Please be aware that this is currently affecting the Availability

Here is detail for this incident :

Start time : 11/10/2024 08:00 UTC
Service impact : Customers may encounter difficulties to create new B3 compute instances. Instances already running are not impacted.
Ongoing actions : Investigating

Our teams are fully mobilized and we will keep you informed of developments and the resolution of the incident.

We apologize for the inconvenience and thank you for your understanding.
Oct 11, 13:07 UTC
Oct 11, 2024
[All US region/SYD/SGP][Storage] - Object Storage S3 Standard/High Perf/Swift.
Resolved - Start time : 10/10/2024 05:12 UTC
End time : 10/10/2024 05:58 UTC
Root cause : This incident was related to https://network.status-ovhcloud.com/incidents/6m6tlznkx9bb
We would like to inform you that the incident have been resolved and the situation is back to normal.

We thank you for your understanding and patience throughout this incident
Oct 11, 09:17 UTC
Identified - The issue has been identified and our provider is working on it.
Oct 10, 07:17 UTC
Update - Related incident : https://network.status-ovhcloud.com/incidents/6m6tlznkx9bb
Oct 10, 06:05 UTC
Update - An incident is in progress on our Object Storage offer.

Please be aware that this is currently affecting the Latency.

Here is detail for this incident :

Start time : 10/10/2024 05:12 UTC
Service impact : Customers may experience storage connection problems, 503 errors and high response times.
Ongoing actions : Investigating

Our teams are fully mobilized and we will keep you informed of developments and the resolution of the incident.

We apologize for the inconvenience and thank you for your understanding.
Oct 10, 06:01 UTC
Investigating - We have detected an issue on one of our services. We will update informations when we will have more details.
Start time : 10/10/2024 05:12 UTC
Oct 10, 05:43 UTC
Oct 10, 2024
Oct 9, 2024

No incidents reported.

Oct 8, 2024
[CA][Public Cloud] - Instances unreachable
Resolved - Please be advised that the incident has been resolved and the situation has returned to normal.

Start time : 08/10/2024 11:54 UTC
End time : 08/10/2024 16:00 UTC
Root cause : Issue caused by this incident https://bare-metal-servers.status-ovhcloud.com/incidents/0b8phs355pfs

We thank you for your understanding and patience throughout this incident
Oct 8, 18:59 UTC
Identified - An incident is in progress on our compute offer. It has temporarily affected the availability.

Our teams are fully mobilized and we will keep you informed of developments and the resolution of the incident.

Here is detail for this incident :

Start time : 08/10/2024 11:54 UTC
Service impact : Some instances are unavailable.
Root cause : Issue caused by this incident https://bare-metal-servers.status-ovhcloud.com/incidents/0b8phs355pfs

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

We apologize for the inconvenience and thank you for your understanding.
Oct 8, 13:19 UTC
Oct 7, 2024

No incidents reported.

Oct 6, 2024

No incidents reported.

Oct 5, 2024

No incidents reported.

Oct 4, 2024
[DE1][Public Cloud] Octavia Load balancer incident notification
Resolved - Start time : 04/10/2024 14:00 UTC
End time : 04/10/2024 16:00 UTC
Service impact : The customers could no longer manage (update, delete) the Octavia load balancer service.
Root cause : This incident was due to network issue.
We would like to inform you that the incident have been resolved and the situation is back to normal.

We thank you for your understanding and patience throughout this incident
Oct 4, 16:42 UTC
Oct 3, 2024
[GRA6][BlockStorage] - VPS
Resolved - Start time : 01/10/2024 13:05 UTC
End time : 03/10/2024 10:15 UTC
Service impact : Some slowness and latency were observed by customers on their servers.
Root cause : Software issue
We would like to inform you that the incident have been resolved and the situation is back to normal.
We thank you for your understanding and patience throughout this incident
Oct 3, 10:49 UTC
Update - Our teams performed a rollback of the operation which was scheduled for 02/10/2024 at 21:00 UTC.
They are currently monitoring the situation and working on a fix to implement.
In the meantime, customers may experience latency.
Oct 3, 04:04 UTC
Update - An operation will take place on 02/10/2024 at 21:00 UTC for a duration of 6 hours. Performance may be impacted during the operation.
Oct 2, 07:29 UTC
Update - Services have regained operational capacity, however customers may experience latency.
Oct 1, 18:26 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 1, 18:21 UTC
Update - We are continuing to work on a fix for this issue.
Oct 1, 18:19 UTC
Identified - The issue has been identified and a fix is being implemented.
Oct 1, 13:59 UTC
Investigating - An incident is in progress on our Block Storage offer.

Please be aware that this is currently affecting the latency.

Here is detail for this incident :

Start time : 01/10/2024 13:05 UTC
Service impact : Some slowness and latency are observed by customers on their servers.
Ongoing actions : Investigating

Our teams are fully mobilized and we will keep you informed of developments and the resolution of the incident.

We apologize for the inconvenience and thank you for your understanding
Oct 1, 13:36 UTC
[GRA9][Containers & Orchestration] - Managed Kubernetes Service incident notification
Resolved - Start time : 03/10/2024 04:45 UTC
End time : 03/10/2024 08:31 UTC
Service impact : Customers were unable to perform management operations on the Managed Kubernetes Service Clusters in GRA9 (creation/modification/deletion)
Root cause : Software issue
We would like to inform you that the incident have been resolved and the situation is back to normal.

We thank you for your understanding and patience throughout this incident
Oct 3, 08:33 UTC
Identified - Start time : 03/10/2024 04:45 UTC
Service impact : Customers are unable to perform management operations on the Managed Kubernetes Service Clusters in GRA9 (creation/modification/deletion)
Ongoing actions : Our technical teams are currently implementing a fix to solve the incident. Update will be posted as significant progress is made.
Oct 3, 07:54 UTC
Oct 2, 2024
[SGP2][Public Cloud] - Network maintenance notification
Completed - The scheduled maintenance has been completed.
Oct 2, 18:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 2, 14:00 UTC
Scheduled - As part of our continuous improvement plan, maintenance is scheduled on our Public Cloud network.

Start time : 02/10/2024 14:00 UTC
End time : 02/10/2024 20:00 UTC
Service impact : None
Service improvement : Following our continuous improvement policy, we will be doing a maintenance on multiple network equipment.

Thank you for your understanding.
Sep 17, 22:26 UTC
[SGP][Storage] - Object Storage S3 Standard/High Perf
Resolved - Start time : 02/10/2024 16:28 UTC
End time : 02/10/2024 16:41 UTC
Service impact : Customers may have faced 503 errors and high response times
Root cause : It was due to a malfunction on a hardware.

We would like to inform you that the incident have been resolved and the situation is back to normal.

We thank you for your understanding and patience throughout this incident
Oct 2, 17:00 UTC
Oct 1, 2024
[Global][Public Cloud] - Databases API instabilities
Resolved - Start time : 02/09/2024 10:30 UTC
End time : 26/09/2024 15:30 UTC
Root cause : This incident was due to change in underlying metrics infrastructure caused latency increase.
We would like to inform you that the incident have been resolved and the situation is back to normal.

We thank you for your understanding and patience throughout this incident
Oct 1, 09:19 UTC
Monitoring - A change in underlying metrics infrastructure on August 21 ended up increasing latency for metrics calls in certain conditions, causing the September 2 event with a period of hours where all such calls ended up erroring. Other parts of the system decided that calls where latency was too high were in error, causing about a 3% error rate on metrics endpoints since then.
Increasing latency toleration in some parts of the system allows us to mitigate the impact and reach an almost 0% error rate. We continue to monitor and work on improvements to go back to nominal behavior. Please be advised that further details will be provided on Monday 30/09/2024.
Sep 27, 13:48 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.
Sep 16, 09:25 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.
Sep 6, 10:08 UTC
Identified - Ongoing actions :Errors are again being observed since the 05/09/2024 08:00 UTC.
Our providers is currently working on a fix for this issue.
Sep 5, 15:29 UTC
Update - Ongoing actions :Errors have been observed again the 04/09/2024 between 01:00 UTC and 2:00 UTC and also between 07:00 UTC and 08:00 UTC.
Our teams are currently monitoring the situation.
Sep 4, 08:46 UTC
Monitoring - Ongoing actions : No more impact is being observed since 02/09/2024 09:30 UTC.
Our teams are currently monitoring the situation.
Sep 3, 13:05 UTC
Investigating - Service impact : Errors are being observed again on API calls to metrics endpoints.
Customer may have error 500 and error 200.
Database service functionality is not impacted and should continue to work as expected.
Ongoing actions : Our technical teams are currently working with our partner to solve the issue.
Update will be posted as significant progress is made.
Sep 3, 07:57 UTC
Monitoring - Ongoing actions : No more impact is being observed since 02/09/2024 20:00 UTC.
Our teams are currently monitoring the situation.
Sep 3, 07:17 UTC
Update - The incident is still ongoing. We would like to assure you that our providers are doing their 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
Sep 2, 17:32 UTC
Update - Our providers continuing to work on a fix for this issue.
Sep 2, 12:54 UTC
Identified - The issue has been identified and a fix is being implemented.
Sep 2, 12:33 UTC
Investigating - Start time : 02/09/2024 10:30 UTC
Service impact : API calls to metrics endpoints are erroring. Database service functionality is not impacted and should continue to work as expected.
Ongoing actions : Investigating
Our providers are working on the issue.
Update will be posted as significant progress is made.
Sep 2, 12:33 UTC
[GRA3/5/7/9/11][Public Cloud] - Network maintenance notification
Completed - The scheduled maintenance has been completed.
Oct 1, 03:51 UTC
Update - Please be advised that during the initial operations in GRA, there was a one-minute interruption. Please be aware that operations are still ongoing.
Sep 30, 23:58 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 30, 20:00 UTC
Scheduled - As part of our continuous improvement plan, maintenance is scheduled on our network infrastructure.

This may temporarily affect Latency.

Start time : 30/09/2024 20:00 UTC
End time : 01/10/2024 04:00 UTC
Service impact : None. Except in rare case latencies may be noted to reach PCI instances running
Service improvement : Following our continuous improvement policy of our products and services, we will carry out a network hardware upgrade in our Graveline Datacenters.

The operation is carried out in several steps:

- Step 1: Preparation of the operation (about 3 hours)
- Step 2: New hardware implementation (about 2 hours)
- Step 3: Test and activation of the new hardware (about 2 hours)

The critical phase of this upgrade is tentatively scheduled between 10:30 PM UTC and 12:00 AM UTC. We are not expecting any impact. However in case of an issue the rollback can be managed in less than 30 minutes.
Sep 17, 21:28 UTC
← Incident History Powered by Atlassian Statuspage