Public Cloud Status
Real-time updates of Public Cloud issues and outages
Public Cloud status is Operational
GRA1
GRA3
GRA5
GRA7
GRA9
GRA11
GRA4
Lior Grossman
Maker of StatusSight
I built StatusSight. Here's what I'm building next with AI.
In Lior Builds, my free newsletter, I share one story from a product I built with AI, plus short notes on the tools and models worth using: what worked, what did not, and the numbers behind it. Every week or two.
Active Incidents
We are currently investigating an incident affecting our Object Storage S3 offering, which is causing temporary latency issue in the EU-WEST-PAR region.
Here are some supplementary details :
Start time : 08/10/2026 00:00 UTC Impacted Service(s) : Latency observed for Object Storage S3 in the specified region. Customers Impact : Customers are temporarily facing latency when trying to access and use their objects located in EU-WEST-PAR 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.
Recently Resolved Incidents
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in GRA regions.
Here are some supplementary details :
Start time : 09/10/2026 10:23 UTC Impacted Service(s) : Some instances in the GRA regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified 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.
We had an incident on our Compute - Instance offering which has now been resolved.
Here are some supplementary details :
Start time : 09/10/2026 08:30 UTC End time : 09/10/2026 08:36 UTC Impacted Service(s) : Some instances in the WAW1 region were unreachable. Customers Impact : Some customers were temporarily unable to access instances located in the specified region. Root Cause : A service disruption occurred due to an unexpected infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
We had an incident on Storage offer which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC End time : 07/10/2026 13:20 UTC Impacted Service(s) : For these regions, you might had issues to access your Cold Archive services. Customers Impact : Customers were temporarily facing 503/500 errors when trying to access their Cold Archive. Root Cause : This is related to this incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t
We thank you for your understanding and patience throughout this incident.
We had an incident on Object Storage S3 offer in EU-WEST-PAR region which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 09:24 UTC End time : 07/10/2026 09:56 UTC Impacted Service(s) : 503/500 errors on Object Storage S3 in EU-WEST-PAR region. Customers Impact : Customers were temporarily facing 503/500 errors and latency when trying to access their S3 buckets and objects. Root Cause : This incident was caused by another incident : https://bare-metal-servers.status-ovhcloud.com/incidents/b3y29nl3y8pl
We thank you for your understanding and patience throughout this incident.
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific regions.
Here are some supplementary details :
Start time : 07/10/2026 13:00 UTC Impacted Service(s) : Managed Kubernetes Service and Managed Private Registry. Customers Impact : Customers are temporarily unable to create or update Managed Kubernetes Service Clusters, and/or add nodes on their Managed Kubernetes Service Clusters. Existing clusters and their workloads are not impacted. Also, customers are temporarily unable to push and pull their Managed Private registry images located in GRA7, GRA9, BHS5 and EU-WEST-PAR regions. Root Cause : This incident is caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t 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.
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
We had an incident on LocalZones offer for AF-NORTH-LZ-RBA, EU-WEST-LZ-DL, EU-NORTH-LZ-OSL and EU-WEST-LZ-MNC regions which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 08:00 UTC End time : 07/10/2026 12:00 UTC Impacted Service(s) : IPv6 was temporarily unavailable for the specified LocalZones. Customers Impact : Customers were temporarily unable to use IPv6 in AF-NORTH-LZ-RBA, EU-WEST-LZ-DL, EU-NORTH-LZ-OSL and EU-WEST-LZ-MNC LocalZones. Root Cause : This incident was caused by a network equipment issue.
We thank you for your understanding and patience throughout this incident.
We had an incident on Compute - Instance offer which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 05:07 UTC End time : 07/10/2026 05:15 UTC Impacted Service(s) : Some instances in the GRA regions were unreachable via public and vRack network. Customers Impact : Some customers were temporarily unable to access instances located on the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure.
We thank you for your understanding and patience throughout this incident.
We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary issue in the region.
Here are some supplementary details :
Start time : 26/08/2026 15:00 UTC Impacted Service(s) : Slowdowns or interruptions in the transmission of artifacts. Customers Impact : Customers may experience slowdowns or interruptions when sending artifacts. 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.
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Object Storage S3 offer on the specific region.
Here are some supplementary details :
Start time : 03/10/2026 02:00 UTC Impacted Service(s) : Object Storage S3 (standard and highperf) service is disrupted in the GRA region. Customers Impact : Customers may experience issues downloading or uploading their objects due to 500/503 errors. These errors mainly affect deletion requests. 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.
Public Cloud Outage Survival Guide
You're checking on Public Cloud - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Public Cloud Components
Public Cloud AI & Machine Learning || AI Dashboard
Public Cloud AI & Machine Learning || AI Deploy
BHS
GRA
Public Cloud AI & Machine Learning || AI Endpoint
Public Cloud AI & Machine Learning || AI Notebooks
BHS
GRA
Public Cloud AI & Machine Learning || AI Training
BHS
GRA
Public Cloud Compute - Instance || BHS
BHS1
BHS3
BHS5
BHS7
Public Cloud Compute - Instance || ERI
UK1
Public Cloud Compute - Instance || EU-SOUTH-MIL
GRA2
EU-SOUTH-MIL-A
EU-SOUTH-MIL-B
GRA4
EU-SOUTH-MIL-C
Public Cloud Compute - Instance || EU-WEST-PAR
EU-WEST-PAR-A
EU-WEST-PAR-B
EU-WEST-PAR-C
Public Cloud Compute - Instance || GRA
Public Cloud Compute-Instance || AP-SOUTH-MUM
GRA1
We had an incident on Compute - Instance offer which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 05:07 UTC End time : 07/10/2026 05:15 UTC Impacted Service(s) : Some instances in the GRA regions were unreachable via public and vRack network. Customers Impact : Some customers were temporarily unable to access instances located on the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure.
We thank you for your understanding and patience throughout this incident.
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in GRA regions.
Here are some supplementary details :
Start time : 09/10/2026 10:23 UTC Impacted Service(s) : Some instances in the GRA regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified 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.
GRA3
We had an incident on Compute - Instance offer which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 05:07 UTC End time : 07/10/2026 05:15 UTC Impacted Service(s) : Some instances in the GRA regions were unreachable via public and vRack network. Customers Impact : Some customers were temporarily unable to access instances located on the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure.
We thank you for your understanding and patience throughout this incident.
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in GRA regions.
Here are some supplementary details :
Start time : 09/10/2026 10:23 UTC Impacted Service(s) : Some instances in the GRA regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified 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.
GRA5
We had an incident on Compute - Instance offer which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 05:07 UTC End time : 07/10/2026 05:15 UTC Impacted Service(s) : Some instances in the GRA regions were unreachable via public and vRack network. Customers Impact : Some customers were temporarily unable to access instances located on the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure.
We thank you for your understanding and patience throughout this incident.
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in GRA regions.
Here are some supplementary details :
Start time : 09/10/2026 10:23 UTC Impacted Service(s) : Some instances in the GRA regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified 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.
GRA7
We had an incident on Compute - Instance offer which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 05:07 UTC End time : 07/10/2026 05:15 UTC Impacted Service(s) : Some instances in the GRA regions were unreachable via public and vRack network. Customers Impact : Some customers were temporarily unable to access instances located on the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure.
We thank you for your understanding and patience throughout this incident.
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in GRA regions.
Here are some supplementary details :
Start time : 09/10/2026 10:23 UTC Impacted Service(s) : Some instances in the GRA regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified 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.
GRA9
We had an incident on Compute - Instance offer which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 05:07 UTC End time : 07/10/2026 05:15 UTC Impacted Service(s) : Some instances in the GRA regions were unreachable via public and vRack network. Customers Impact : Some customers were temporarily unable to access instances located on the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure.
We thank you for your understanding and patience throughout this incident.
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in GRA regions.
Here are some supplementary details :
Start time : 09/10/2026 10:23 UTC Impacted Service(s) : Some instances in the GRA regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified 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.
GRA11
We had an incident on Compute - Instance offer which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 05:07 UTC End time : 07/10/2026 05:15 UTC Impacted Service(s) : Some instances in the GRA regions were unreachable via public and vRack network. Customers Impact : Some customers were temporarily unable to access instances located on the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure.
We thank you for your understanding and patience throughout this incident.
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in GRA regions.
Here are some supplementary details :
Start time : 09/10/2026 10:23 UTC Impacted Service(s) : Some instances in the GRA regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified 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.
GRA4
We had an incident on Compute - Instance offer which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 05:07 UTC End time : 07/10/2026 05:15 UTC Impacted Service(s) : Some instances in the GRA regions were unreachable via public and vRack network. Customers Impact : Some customers were temporarily unable to access instances located on the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure.
We thank you for your understanding and patience throughout this incident.
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in GRA regions.
Here are some supplementary details :
Start time : 09/10/2026 10:23 UTC Impacted Service(s) : Some instances in the GRA regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified 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.
Public Cloud Compute - Instance || India
AP-SOUTH-MUM-1
Public Cloud Compute - Instance || LIM
DE1
Public Cloud Compute - Instance || RBX
RBX-A
Public Cloud Compute - Instance || SGP
SGP1
SGP2
Public Cloud Compute - Instance || SBG
SBG5
SBG7
SBG3
Public Cloud Compute - Instance || SYD
SYD1
AP-SOUTHEAST-SYD-2
Public Cloud Compute - Instance || USA
US-EAST-VA-1
US-WEST-OR-1
Public Cloud Compute - Instance || WAW
WAW1
We had an incident on our Compute - Instance offering which has now been resolved.
Here are some supplementary details :
Start time : 09/10/2026 08:30 UTC End time : 09/10/2026 08:36 UTC Impacted Service(s) : Some instances in the WAW1 region were unreachable. Customers Impact : Some customers were temporarily unable to access instances located in the specified region. Root Cause : A service disruption occurred due to an unexpected infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
Public Cloud Containers & Orchestration || Load Balancer
BHS5
AP-SOUTH-MUM
DE1
EU-WEST-PAR
GRA5
GRA7
GRA9
GRA11
RBX-A
SBG5
SGP1
SYD1
WAW1
UK1
US-EAST-VA
US-WEST-OR
Public Cloud Containers & Orchestration || Managed Kubernetes Service
AP-SOUTH-MUM
BHS5
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific regions.
Here are some supplementary details :
Start time : 07/10/2026 13:00 UTC Impacted Service(s) : Managed Kubernetes Service and Managed Private Registry. Customers Impact : Customers are temporarily unable to create or update Managed Kubernetes Service Clusters, and/or add nodes on their Managed Kubernetes Service Clusters. Existing clusters and their workloads are not impacted. Also, customers are temporarily unable to push and pull their Managed Private registry images located in GRA7, GRA9, BHS5 and EU-WEST-PAR regions. Root Cause : This incident is caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t 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.
EU-WEST-LIM
EU-SOUTH-MIL
EU-WEST-PAR
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific regions.
Here are some supplementary details :
Start time : 07/10/2026 13:00 UTC Impacted Service(s) : Managed Kubernetes Service and Managed Private Registry. Customers Impact : Customers are temporarily unable to create or update Managed Kubernetes Service Clusters, and/or add nodes on their Managed Kubernetes Service Clusters. Existing clusters and their workloads are not impacted. Also, customers are temporarily unable to push and pull their Managed Private registry images located in GRA7, GRA9, BHS5 and EU-WEST-PAR regions. Root Cause : This incident is caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t 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.
RBX
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific regions.
Here are some supplementary details :
Start time : 07/10/2026 13:00 UTC Impacted Service(s) : Managed Kubernetes Service and Managed Private Registry. Customers Impact : Customers are temporarily unable to create or update Managed Kubernetes Service Clusters, and/or add nodes on their Managed Kubernetes Service Clusters. Existing clusters and their workloads are not impacted. Also, customers are temporarily unable to push and pull their Managed Private registry images located in GRA7, GRA9, BHS5 and EU-WEST-PAR regions. Root Cause : This incident is caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t 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.
GRA5
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific regions.
Here are some supplementary details :
Start time : 07/10/2026 13:00 UTC Impacted Service(s) : Managed Kubernetes Service and Managed Private Registry. Customers Impact : Customers are temporarily unable to create or update Managed Kubernetes Service Clusters, and/or add nodes on their Managed Kubernetes Service Clusters. Existing clusters and their workloads are not impacted. Also, customers are temporarily unable to push and pull their Managed Private registry images located in GRA7, GRA9, BHS5 and EU-WEST-PAR regions. Root Cause : This incident is caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t 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.
GRA7
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific regions.
Here are some supplementary details :
Start time : 07/10/2026 13:00 UTC Impacted Service(s) : Managed Kubernetes Service and Managed Private Registry. Customers Impact : Customers are temporarily unable to create or update Managed Kubernetes Service Clusters, and/or add nodes on their Managed Kubernetes Service Clusters. Existing clusters and their workloads are not impacted. Also, customers are temporarily unable to push and pull their Managed Private registry images located in GRA7, GRA9, BHS5 and EU-WEST-PAR regions. Root Cause : This incident is caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t 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.
GRA9
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific regions.
Here are some supplementary details :
Start time : 07/10/2026 13:00 UTC Impacted Service(s) : Managed Kubernetes Service and Managed Private Registry. Customers Impact : Customers are temporarily unable to create or update Managed Kubernetes Service Clusters, and/or add nodes on their Managed Kubernetes Service Clusters. Existing clusters and their workloads are not impacted. Also, customers are temporarily unable to push and pull their Managed Private registry images located in GRA7, GRA9, BHS5 and EU-WEST-PAR regions. Root Cause : This incident is caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t 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.
GRA11
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific regions.
Here are some supplementary details :
Start time : 07/10/2026 13:00 UTC Impacted Service(s) : Managed Kubernetes Service and Managed Private Registry. Customers Impact : Customers are temporarily unable to create or update Managed Kubernetes Service Clusters, and/or add nodes on their Managed Kubernetes Service Clusters. Existing clusters and their workloads are not impacted. Also, customers are temporarily unable to push and pull their Managed Private registry images located in GRA7, GRA9, BHS5 and EU-WEST-PAR regions. Root Cause : This incident is caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t 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.
SBG5
SGP1
SYD1
WAW1
UK1
US-EAST-VA
US-WEST-OR
DE1
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific regions.
Here are some supplementary details :
Start time : 07/10/2026 13:00 UTC Impacted Service(s) : Managed Kubernetes Service and Managed Private Registry. Customers Impact : Customers are temporarily unable to create or update Managed Kubernetes Service Clusters, and/or add nodes on their Managed Kubernetes Service Clusters. Existing clusters and their workloads are not impacted. Also, customers are temporarily unable to push and pull their Managed Private registry images located in GRA7, GRA9, BHS5 and EU-WEST-PAR regions. Root Cause : This incident is caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t 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.
Public Cloud Containers & Orchestration || Managed Private Registry
AP-SOUTH-MUM
BHS
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific regions.
Here are some supplementary details :
Start time : 07/10/2026 13:00 UTC Impacted Service(s) : Managed Kubernetes Service and Managed Private Registry. Customers Impact : Customers are temporarily unable to create or update Managed Kubernetes Service Clusters, and/or add nodes on their Managed Kubernetes Service Clusters. Existing clusters and their workloads are not impacted. Also, customers are temporarily unable to push and pull their Managed Private registry images located in GRA7, GRA9, BHS5 and EU-WEST-PAR regions. Root Cause : This incident is caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t 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.
DE
EU-SOUTH-MIL
We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary issue in the region.
Here are some supplementary details :
Start time : 26/08/2026 15:00 UTC Impacted Service(s) : Slowdowns or interruptions in the transmission of artifacts. Customers Impact : Customers may experience slowdowns or interruptions when sending artifacts. 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.
EU-WEST-PAR
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific regions.
Here are some supplementary details :
Start time : 07/10/2026 13:00 UTC Impacted Service(s) : Managed Kubernetes Service and Managed Private Registry. Customers Impact : Customers are temporarily unable to create or update Managed Kubernetes Service Clusters, and/or add nodes on their Managed Kubernetes Service Clusters. Existing clusters and their workloads are not impacted. Also, customers are temporarily unable to push and pull their Managed Private registry images located in GRA7, GRA9, BHS5 and EU-WEST-PAR regions. Root Cause : This incident is caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t 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.
GRA
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific regions.
Here are some supplementary details :
Start time : 07/10/2026 13:00 UTC Impacted Service(s) : Managed Kubernetes Service and Managed Private Registry. Customers Impact : Customers are temporarily unable to create or update Managed Kubernetes Service Clusters, and/or add nodes on their Managed Kubernetes Service Clusters. Existing clusters and their workloads are not impacted. Also, customers are temporarily unable to push and pull their Managed Private registry images located in GRA7, GRA9, BHS5 and EU-WEST-PAR regions. Root Cause : This incident is caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t 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.
VA
Public Cloud Containers & Orchestration || Managed Rancher Service
Public Cloud Containers & Orchestration || Workflow Management
BHS1
SYD3
BHS3
BHS5
DE1
GRA1
GRA3
GRA
GRA5
GRA7
GRA9
GRA11
PAR
RBX-A
SBG5
SBG7
SGP1
Public Cloud Databases || M3 Aggregator
SGP2
SYD1
AP-SOUTHEAST-SYD-2
UK1
WAW1
WAW2
Public Cloud Databases || Cassandra
US-EAST-VA
US-WEST-OR
Public Cloud Databases || M3DB
AP-SOUTH-MUM
Public Cloud Databases || MongoDB
BHS
DE
GRA
EU-WEST-PAR
SBG
SGP
UK
WAW
EU-SOUTH-MIL
RBX
AP-SOUTH-MUM
US-EAST-VA
US-WEST-OR
Public Cloud Databases || MySQL
BHS
DE
GRA
EU-SOUTH-MIL
AP-SOUTH-MUM
EU-WEST-PAR
RBX
SBG
SGP
US-EAST-VA
UK
US-WEST-OR
WAW
Public Cloud Databases || PostgreSQL
SYD
BHS
DE
GRA
EU-SOUTH-MIL
AP-SOUTH-MUM
EU-WEST-PAR
RBX
SBG
SGP
UK
US-EAST-VA
US-WEST-OR
Public Cloud Data & Analytics || Data Processing
WAW
Public Cloud Databases || Valkey
GRA
BHS
DE
GRA
EU-SOUTH-MIL
AP-SOUTH-MUM
EU-WEST-PAR
RBX
SBG
SGP
US-EAST-VA
UK
US-WEST-OR
WAW
Public Cloud Data & Analytics || ClickHouse
EU-WEST-PAR
EU-SOUTH-MIL
AP-SOUTH-MUM
Public Cloud Data & Analytics || Data Platform
Public Cloud Data & Analytics || Dashboards
BHS
DE
GRA
EU-WEST-PAR
SBG
SGP
UK
WAW
EU-SOUTH-MIL
AP-SOUTH-MUM
RBX
US-EAST-VA
US-WEST-OR
Public Cloud Data & Analytics || Kafka
BHS
DE
GRA
EU-SOUTH-MIL
AP-SOUTH-MUM
EU-WEST-PAR
RBX
SBG
SGP
AP-SOUTH-MUM-1
UK
US-EAST-VA
MAD
US-WEST-OR
WAW
Public Cloud Data & Analytics || Kafka Connect
Public Cloud Network || FailoverIP
BHS
DE
GRA
EU-WEST-PAR
EU-SOUTH-MIL
AP-SOUTH-MUM
RBX
SBG
SGP
UK
US-EAST-VA
US-WEST-OR
WAW
Public Cloud Data & Analytics || Kafka MirrorMaker
BHS
DE
GRA
EU-SOUTH-MIL
AP-SOUTH-MUM
EU-WEST-PAR
RBX
Public Cloud Network || Load Balancer
SBG
SGP
UK
WAW
US-EAST-VA
US-WEST-OR
Public Cloud Data & Analytics || OpenSearch
BHS
DE
GRA
EU-SOUTH-MIL
AP-SOUTH-MUM
EU-WEST-PAR
RBX
SBG
SGP
US-EAST-VA
UK
US-WEST-OR
WAW
Public Cloud Identity, Security & Operations || Authentication
Public Cloud Identity, Security & Operations || Barbican
AP-SOUTH-MUM
AP-SOUTHEAST-SYD-2
BHS5
DE1
EU-SOUTH-MIL
EU-WEST-PAR
GRA9
RBX-A
SBG7
SGP1
SYD1
UK1
US-WEST-OR
US-EAST-VA
WAW1
Public Cloud Management || Horizon
Public Cloud Identity, Security & Operations || Key Management Service
AP-SOUTHEAST-SGP
AP-SOUTHEAST-SYD
CA-EAST-TOR
CA-EAST-BHS
EU-CENTRAL-WAW
EU-SOUTH-MIL
EU-WEST-ERI
EU-WEST-GRA
EU-WEST-LIM
EU-WEST-PAR
EU-WEST-RBX
EU-WEST-SBG
Public Cloud Identity, Security & Operations || Logs Data Platform
BHS
GRA
Public Cloud LocalZones || AF-CENTRAL
AF-CENTRAL-LZ-ABJ
Public Cloud LocalZones || AF-NORTH
AF-NORTH-LZ-RBA
We had an incident on LocalZones offer for AF-NORTH-LZ-RBA, EU-WEST-LZ-DL, EU-NORTH-LZ-OSL and EU-WEST-LZ-MNC regions which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 08:00 UTC End time : 07/10/2026 12:00 UTC Impacted Service(s) : IPv6 was temporarily unavailable for the specified LocalZones. Customers Impact : Customers were temporarily unable to use IPv6 in AF-NORTH-LZ-RBA, EU-WEST-LZ-DL, EU-NORTH-LZ-OSL and EU-WEST-LZ-MNC LocalZones. Root Cause : This incident was caused by a network equipment issue.
We thank you for your understanding and patience throughout this incident.
Public Cloud LocalZones || AP-SOUTH
AP-SOUTH-LZ-AKL
AP-SOUTH-MUM
Public Cloud LocalZones || EU-CENTRAL
AP-SOUTH-MUM-1
EU-CENTRAL-LZ-BUH
EU-CENTRAL-LZ-PRG
EU-CENTRAL-LZ-SOF
Public Cloud LocalZones || EU-NORTH
EU-NORTH-LZ-CPH
EU-NORTH-LZ-HEL
EU-NORTH-LZ-OSL
We had an incident on LocalZones offer for AF-NORTH-LZ-RBA, EU-WEST-LZ-DL, EU-NORTH-LZ-OSL and EU-WEST-LZ-MNC regions which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 08:00 UTC End time : 07/10/2026 12:00 UTC Impacted Service(s) : IPv6 was temporarily unavailable for the specified LocalZones. Customers Impact : Customers were temporarily unable to use IPv6 in AF-NORTH-LZ-RBA, EU-WEST-LZ-DL, EU-NORTH-LZ-OSL and EU-WEST-LZ-MNC LocalZones. Root Cause : This incident was caused by a network equipment issue.
We thank you for your understanding and patience throughout this incident.
EU-NORTH-LZ-STO
Public Cloud LocalZones || EU-SOUTH
EU-SOUTH-LZ-LIS
EU-SOUTH-LZ-MAD
EU-SOUTH-LZ-MIL
Public Cloud LocalZones || EU-WEST
EU-WEST-LZ-AMS
EU-WEST-LZ-BRU
EU-WEST-LZ-DLN
We had an incident on LocalZones offer for AF-NORTH-LZ-RBA, EU-WEST-LZ-DL, EU-NORTH-LZ-OSL and EU-WEST-LZ-MNC regions which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 08:00 UTC End time : 07/10/2026 12:00 UTC Impacted Service(s) : IPv6 was temporarily unavailable for the specified LocalZones. Customers Impact : Customers were temporarily unable to use IPv6 in AF-NORTH-LZ-RBA, EU-WEST-LZ-DL, EU-NORTH-LZ-OSL and EU-WEST-LZ-MNC LocalZones. Root Cause : This incident was caused by a network equipment issue.
We thank you for your understanding and patience throughout this incident.
EU-WEST-LZ-LUX
EU-WEST-LZ-MNC
We had an incident on LocalZones offer for AF-NORTH-LZ-RBA, EU-WEST-LZ-DL, EU-NORTH-LZ-OSL and EU-WEST-LZ-MNC regions which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 08:00 UTC End time : 07/10/2026 12:00 UTC Impacted Service(s) : IPv6 was temporarily unavailable for the specified LocalZones. Customers Impact : Customers were temporarily unable to use IPv6 in AF-NORTH-LZ-RBA, EU-WEST-LZ-DL, EU-NORTH-LZ-OSL and EU-WEST-LZ-MNC LocalZones. Root Cause : This incident was caused by a network equipment issue.
We thank you for your understanding and patience throughout this incident.
EU-WEST-LZ-MRS
EU-WEST-LZ-VIE
EU-WEST-LZ-ZRH
Public Cloud LocalZones || US-CENTRAL
US-CENTRAL-LZ-SLC
US-CENTRAL-LZ-STL
Public Cloud LocalZones || US-EAST
US-EAST-LZ-ATL
US-EAST-LZ-BOS
US-EAST-LZ-CHI
US-EAST-LZ-DAL
US-EAST-LZ-MIA
US-EAST-LZ-NYC
Public Cloud LocalZones || US-WEST
US-WEST-LZ-DEN
US-WEST-LZ-LAX
US-WEST-LZ-PAO
US-WEST-LZ-PHX
US-WEST-LZ-SEA
Public Cloud LocalZones || SA-WEST
SA-WEST-LZ-SCL
Public Cloud Network || Floating IP
BHS1
BHS3
BHS5
DE1
GRA1
GRA3
GRA5
GRA7
GRA9
GRA11
AP-SOUTH-MUM-1
RBX-A
SBG5
SBG7
SGP1
SYD1
AP-SOUTHEAST-SYD-2
UK1
WAW1
US-EAST-VA-1
US-WEST-OR-1
EU-WEST-PAR-A
EU-WEST-PAR-B
EU-WEST-PAR-C
EU-SOUTH-MIL-A
EU-SOUTH-MIL-B
EU-SOUTH-MIL-C
Public Cloud Network || Gateway
BHS1
BHS3
BHS5
DE1
GRA1
GRA3
GRA5
GRA7
GRA9
GRA11
SBG5
SBG7
Public Cloud UK
SGP1
SYD1
AP-SOUTHEAST-SYD-2
UK1
WAW1
US-EAST-VA-1
US-WEST-OR-1
AP-SOUTH-MUM-1
EU-WEST-PAR-A
EU-WEST-PAR-B
EU-WEST-PAR-C
RBX-A
EU-SOUTH-MIL-A
EU-SOUTH-MIL-B
EU-SOUTH-MIL-C
Public Cloud Network || Load Balancer
BHS1
BHS3
BHS5
DE1
GRA1
GRA3
GRA5
GRA7
GRA9
GRA11
SBG5
SBG7
SGP1
SYD1
AP-SOUTHEAST-SYD-2
UK1
WAW1
US-EAST-VA-1
US-WEST-OR-1
EU-WEST-PAR-A
EU-WEST-PAR-B
EU-WEST-PAR-C
AP-SOUTH-MUM-1
RBX-A
EU-SOUTH-MIL-A
EU-SOUTH-MIL-B
EU-SOUTH-MIL-C
Public Cloud Network || Private network (vRack)
BHS1
BHS3
BHS5
DE1
GRA1
GRA3
GRA5
GRA7
GRA9
GRA11
RBX-A
Public Cloud Compute - Instance || 3AZ
PAR
SBG5
SBG7
SGP1
SGP2
SYD1
RBX-A
AP-SOUTHEAST-SYD-2
UK1
WAW1
US-EAST-VA-1
US-WEST-OR-1
EU-WEST-PAR-A
EU-WEST-PAR-B
EU-WEST-PAR-C
AP-SOUTH-MUM-1
RBX-A
EU-SOUTH-MIL-A
EU-SOUTH-MIL-B
EU-SOUTH-MIL-C
Public Cloud Network || Public network
BHS1
BHS3
BHS5
DE1
GRA1
GRA3
GRA5
GRA7
GRA9
GRA11
RBX-A
SBG1
SBG3
SBG5
SBG7
SGP1
SGP2
SYD1
AP-SOUTHEAST-SYD-2
UK1
WAW1
US-EAST-VA-1
US-WEST-OR-1
EU-WEST-PAR-A
EU-WEST-PAR-B
EU-WEST-PAR-C
AP-SOUTH-MUM-1
RBX-A
EU-SOUTH-MIL-A
EU-SOUTH-MIL-B
EU-SOUTH-MIL-C
Public Cloud Quantum || Emulators
BHS
GRA
Public Cloud Quantum || QPUs
BHS
SYD2
GRA
Public Cloud Storage || Block storage
AP-SOUTHEAST-SYD-2
AP-SOUTH-MUM-1
BHS1
BHS3
BHS5
DE1
EU-SOUTH-MIL-A
EU-SOUTH-MIL-B
EU-SOUTH-MIL-C
EU-WEST-PAR-A
EU-WEST-PAR-B
EU-WEST-PAR-C
GRA1
GRA3
GRA5
GRA6
GRA7
GRA9
GRA11
RBX-A
SBG5
SBG7
SGP1
SYD1
UK1
US-EAST-VA-1
US-WEST-OR-1
WAW1
YNM1
Public Cloud Storage || Cloud Archive
DE
GRA
UK
WAW
Public Cloud BHS
BHS
Public Cloud DE
SYD
Public Cloud GRA
Public Cloud PAR
SGP
US-EAST-VA
Public Cloud SBG
Public Cloud UK
US-WEST-OR
Public Cloud Storage || Cold Archive
Public Cloud WAW
RBX-ARCHIVE
We had an incident on Storage offer which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC End time : 07/10/2026 13:20 UTC Impacted Service(s) : For these regions, you might had issues to access your Cold Archive services. Customers Impact : Customers were temporarily facing 503/500 errors when trying to access their Cold Archive. Root Cause : This is related to this incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t
We thank you for your understanding and patience throughout this incident.
Public Cloud BHS
Public Cloud Storage || File storage
Public Cloud DE
Public Cloud GRA
AP-SOUTH-MUM-1
BHS3
Public Cloud PAR
Public Cloud SBG
BHS5
Public Cloud UK
DE1
EU-SOUTH-MIL
Public Cloud WAW
EU-WEST-PAR
GRA1
GRA3
GRA5
GRA7
GRA9
GRA11
RBX-A
SBG5
SBG7
SGP1
SYD1
UK1
US-EAST-VA-1
US-WEST-OR-1
WAW1
Public Cloud Storage || Instance Backup
BHS1
BHS3
BHS5
DE1
GRA1
GRA3
GRA5
GRA7
GRA9
GRA11
SBG5
SBG7
SGP1
SYD1
AP-SOUTHEAST-SYD-2
UK1
US-EAST-VA-1
US-WEST-OR-1
WAW1
AP-SOUTH-MUM-1
EU-WEST-PAR-A
EU-WEST-PAR-B
EU-WEST-PAR-C
RBX-A
Public Cloud Storage || Object storage
BHS
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
GRA
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Object Storage S3 offer on the specific region.
Here are some supplementary details :
Start time : 03/10/2026 02:00 UTC Impacted Service(s) : Object Storage S3 (standard and highperf) service is disrupted in the GRA region. Customers Impact : Customers may experience issues downloading or uploading their objects due to 500/503 errors. These errors mainly affect deletion requests. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution.
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
DE
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
RBX
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
SBG
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
SGP
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
SYD
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
UK
US-EAST-VA-1
US-WEST-OR-1
WAW
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
YYZ
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
LIM
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
AP-SOUTH-MUM-1
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
EU-WEST-PAR-A
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
We had an incident on Object Storage S3 offer in EU-WEST-PAR region which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 09:24 UTC End time : 07/10/2026 09:56 UTC Impacted Service(s) : 503/500 errors on Object Storage S3 in EU-WEST-PAR region. Customers Impact : Customers were temporarily facing 503/500 errors and latency when trying to access their S3 buckets and objects. Root Cause : This incident was caused by another incident : https://bare-metal-servers.status-ovhcloud.com/incidents/b3y29nl3y8pl
We thank you for your understanding and patience throughout this incident.
We are currently investigating an incident affecting our Object Storage S3 offering, which is causing temporary latency issue in the EU-WEST-PAR region.
Here are some supplementary details :
Start time : 08/10/2026 00:00 UTC Impacted Service(s) : Latency observed for Object Storage S3 in the specified region. Customers Impact : Customers are temporarily facing latency when trying to access and use their objects located in EU-WEST-PAR 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.
EU-WEST-PAR-B
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
We had an incident on Object Storage S3 offer in EU-WEST-PAR region which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 09:24 UTC End time : 07/10/2026 09:56 UTC Impacted Service(s) : 503/500 errors on Object Storage S3 in EU-WEST-PAR region. Customers Impact : Customers were temporarily facing 503/500 errors and latency when trying to access their S3 buckets and objects. Root Cause : This incident was caused by another incident : https://bare-metal-servers.status-ovhcloud.com/incidents/b3y29nl3y8pl
We thank you for your understanding and patience throughout this incident.
We are currently investigating an incident affecting our Object Storage S3 offering, which is causing temporary latency issue in the EU-WEST-PAR region.
Here are some supplementary details :
Start time : 08/10/2026 00:00 UTC Impacted Service(s) : Latency observed for Object Storage S3 in the specified region. Customers Impact : Customers are temporarily facing latency when trying to access and use their objects located in EU-WEST-PAR 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.
EU-WEST-PAR-C
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
We had an incident on Object Storage S3 offer in EU-WEST-PAR region which has now been resolved.
Here are some supplementary details :
Start time : 07/10/2026 09:24 UTC End time : 07/10/2026 09:56 UTC Impacted Service(s) : 503/500 errors on Object Storage S3 in EU-WEST-PAR region. Customers Impact : Customers were temporarily facing 503/500 errors and latency when trying to access their S3 buckets and objects. Root Cause : This incident was caused by another incident : https://bare-metal-servers.status-ovhcloud.com/incidents/b3y29nl3y8pl
We thank you for your understanding and patience throughout this incident.
We are currently investigating an incident affecting our Object Storage S3 offering, which is causing temporary latency issue in the EU-WEST-PAR region.
Here are some supplementary details :
Start time : 08/10/2026 00:00 UTC Impacted Service(s) : Latency observed for Object Storage S3 in the specified region. Customers Impact : Customers are temporarily facing latency when trying to access and use their objects located in EU-WEST-PAR 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.
YNM1
EU-SOUTH-MIL-B
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
EU-SOUTH-MIL-A
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.
EU-SOUTH-MIL-C
We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the EU and CA regions.
Here are some supplementary details :
Start time : 07/10/2026 12:36 UTC Impacted Service(s) : For these regions, you might have issues to access your S3 buckets and objects. Your compute and volume services already running are not impacted. Customers Impact : Customers are temporarily facing 503/500 errors when trying to access their S3 buckets and objects. 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.