Public Cloud Outage History

Public Cloud is up right now

Public Cloud had 177 outages in the last 2 years totaling 406h 35m of downtime, averaging 7.3 incidents per month.

There were 177 Public Cloud outages since October 30, 2025 totaling 406h 35m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: public-cloud.status-ovhcloud.com

Minor October 21, 2026

[GRA1][Storage] - Block Storage incident notification

Detected by Pingoru
Oct 21, 2026, 10:37 AM UTC
Resolved
Oct 21, 2026, 01:26 PM UTC
Duration
2h 49m
Affected: GRA1
Timeline · 3 updates
  1. identified Oct 21, 2026, 10:37 AM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Storage offer on the specific GRA1 region. Here are some supplementary details : Start time : 21/10/2026 09:30 UTC Impacted Service(s) : The Block Storage service in the GRA1 region is temporarily experiencing degraded performance. Customers Impact : Customers may temporarily experience degraded performance on their Block Storage services. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  2. identified Oct 21, 2026, 12:16 PM UTC

    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 working to resolve the incident, which should be resolved shortly. 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.

  3. resolved Oct 21, 2026, 01:26 PM UTC

    We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 21/10/2026 09:30 UTC End time : 21/10/2026 13:25 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Minor October 21, 2026

[GLOBAL][AI & Machine Learning] - AI Endpoint Incident Notification

Detected by Pingoru
Oct 21, 2026, 07:27 AM UTC
Resolved
Oct 21, 2026, 12:07 PM UTC
Duration
4h 39m
Affected: AI & Machine Learning || AI Endpoint
Timeline · 3 updates
  1. investigating Oct 21, 2026, 07:27 AM UTC

    We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary availability issue on AI Endpoint . Here are some supplementary details : Start time : 21/10/2026 07:00 UTC Impacted Service(s) : AI Endpoints may have some performance issue. Customers Impact : Customers may temporarily experience slowness when using the AI endpoints. 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.

  2. monitoring Oct 21, 2026, 08:07 AM UTC

    Service has been fully restored since 21/10/2026 08:04 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 21/10/2026 07:00 UTC Impacted Service(s) : AI Endpoints may have had some performance issues. Customers Impact : Customers may have temporarily experienced slowness when using the AI endpoints. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Oct 21, 2026, 12:07 PM UTC

    We are pleased to inform you that the incident affecting our AI & Machine Learning offering has been resolved. Start time : 21/10/2026 07:00 UTC End time : 21/10/2026 08:04 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Minor October 20, 2026

[RBX-A][Public Cloud] Block Storage incident notification

Detected by Pingoru
Oct 20, 2026, 09:20 AM UTC
Resolved
Oct 20, 2026, 11:05 AM UTC
Duration
1h 44m
Affected: RBX-A
Timeline · 2 updates
  1. identified Oct 20, 2026, 09:20 AM UTC

    We are currently experiencing an incident affecting our Public Cloud offering in the RBX-A region. Please find the details of this incident below : Start time : 20/10/2026 08:48 UTC Impacted Service(s) : Block Storage volumes hosted on the RBX-A were unavailable between 08:48 and 09:00 UTC and are currently experiencing reduced performance. Customers Impact : Customers were temporarily unable to access their Block Storage volumes between 08:48 and 09:00 UTC. Since 09:00 UTC, customers may experience degraded performance on their volumes while the cluster is recovering. Root Cause : This incident is caused by a hardware issue. Ongoing Actions : Our teams are actively working to restore full performance as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  2. resolved Oct 20, 2026, 11:05 AM UTC

    We would like to inform you that the incident affecting our Public Cloud offering has now been resolved. Please find the details of this incident below : Start time : 20/10/2026 08:48 UTC End time : 20/10/2026 10:26 UTC Impacted Service(s) : Block Storage volumes hosted on the PCI-RBX-A-volumes_2 cluster in the RBX-A region were unavailable between 08:48 and 09:00 UTC, followed by reduced performance until 10:26 UTC. Customers Impact : Customers were temporarily unable to access their Block Storage volumes between 08:48 and 09:00 UTC, and may have experienced degraded performance on their volumes until 10:26 UTC while the cluster was recovering. Root Cause : This incident was caused by a hardware issue. We thank you for your understanding and patience throughout this incident.

Read the full incident report →

Minor October 17, 2026

[GLOBAL][Cloud Databases] - MYSQL Database incident notification

Detected by Pingoru
Oct 17, 2026, 08:48 AM UTC
Resolved
Oct 17, 2026, 06:54 PM UTC
Duration
10h 5m
Affected: BHSDEGRAEU-SOUTH-MILAP-SOUTH-MUMEU-WEST-PARRBXSBGSGPUS-EAST-VAUKUS-WEST-ORWAW
Timeline · 2 updates
  1. investigating Oct 17, 2026, 08:48 AM UTC

    We are currently investigating an incident affecting our Cloud Databases offering, which is causing temporary latency issue in the Global Region. Here are some supplementary details : Start time : 16/10/2026 22:16 UTC Impacted Service(s) : New MySQL services are taking longer than usual to become available. Existing services are not affected. Customers Impact : Customers are temporarily unable to access the new MySQL services. 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.

  2. resolved Oct 17, 2026, 06:54 PM UTC

    We are pleased to inform you that the incident affecting our Cloud Databases offering has been resolved. Start time : 16/10/2026 22:16 UTC End time : 17/10/2026 11:30 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Minor October 16, 2026

[GRA11][Public Cloud] - Network API incident notification

Detected by Pingoru
Oct 16, 2026, 04:13 PM UTC
Resolved
Oct 17, 2026, 08:06 PM UTC
Duration
1d 3h
Affected: GRA11GRA11GRA11GRA11GRA11
Timeline · 3 updates
  1. investigating Oct 16, 2026, 04:13 PM UTC

    We are currently experiencing an incident affecting our Public Cloud offering, which is causing temporary latency issues in the GRA11 region. Please find the details of this incident below : Start time : 16/10/2026 12:30 UTC Impacted Service(s) : The Public Cloud Network API in the GRA11 region is currently experiencing slowness, affecting operations on Floating IP, Gateway, Load Balancer, Private network (vRack) and Public network. Existing network configurations continue to operate normally. Customers Impact : Customers may experience latency and slowness, or encounter errors, when modifying network configurations or creating new resources. Existing resources and running instances remain unaffected. 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.

  2. monitoring Oct 16, 2026, 04:27 PM UTC

    We would like to inform you that our service has been fully restored as of 16/10/2026 at 15:30 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : Start time : 16/10/2026 12:30 UTC Impacted Service(s) : The Public Cloud Network API in the GRA11 region experienced slowness, affecting operations on Floating IP, Gateway, Load Balancer, Private network (vRack) and Public network. Existing network configurations continued to operate normally. Customers Impact : Customers may have experienced latency and slowness, or encountered errors, when modifying network configurations or creating new resources. Existing resources and running instances remained unaffected. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Oct 17, 2026, 08:06 PM UTC

    We are pleased to inform you that the incident affecting our Public Cloud Network API in the GRA11 region has been resolved. Start time : 16/10/2026 12:30 UTC End time : 16/10/2026 15:30 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major October 15, 2026

[AP-SOUTH-MUM-1][Storage] - S3 Object Storage incident notification

Detected by Pingoru
Oct 15, 2026, 12:24 PM UTC
Resolved
Oct 16, 2026, 08:21 AM UTC
Duration
19h 56m
Affected: AP-SOUTH-MUM-1
Timeline · 3 updates
  1. monitoring Oct 15, 2026, 12:24 PM UTC

    Service has been fully restored since 15/10/2026 11:35 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 15/10/2026 11:30 UTC Impacted Service(s) : Disconnection and 503 errors observed on S3 Object Storage. Customers Impact : Customers were temporarily facing disconnection and 503 errors when trying to access and use their objects located in AP-SOUTH-MUM-1. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/h9zynmg40bbz We apologize for any inconvenience caused and appreciate your understanding.

  2. identified Oct 15, 2026, 03:28 PM UTC

    We are currently experiencing an incident affecting our Object Storage offering in the AP-SOUTH-MUM-1 region. The root cause has been identified. Please find the details of this incident below : Start time : 15/10/2026 11:30 UTC Impacted Service(s) : S3 Object Storage is experiencing disconnections and 503 errors in the AP-SOUTH-MUM-1 region. Customers Impact : Customers may experience disconnections and 503 errors when accessing, uploading or retrieving their objects stored in the specified region. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/h9zynmg40bbz Ongoing Actions : Our teams are actively working 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.

  3. resolved Oct 16, 2026, 08:21 AM UTC

    We are pleased to inform you that the incident affecting our Object Storage offering in AP-SOUTH-MUM-1 region has been resolved. Start time : 15/10/2026 11:30 UTC End time : 15/10/2026 15:05 UTC Root Cause : This incident was caused by another incident : https://network.status-ovhcloud.com/incidents/h9zynmg40bbz We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major October 14, 2026

[GRA9/GRA11][Public Cloud] - Network API incident notification

Detected by Pingoru
Oct 14, 2026, 02:46 PM UTC
Resolved
Oct 14, 2026, 03:24 PM UTC
Duration
37m
Affected: GRA9GRA9GRA11GRA11
Timeline · 2 updates
  1. investigating Oct 14, 2026, 02:46 PM UTC

    We are currently experiencing an incident affecting our Public Cloud offering, which is causing temporary latency issues in the GRA9 and GRA11 regions. Please find the details of this incident below : Start time : 14/10/2026 08:00 UTC Impacted Service(s) : The OpenStack Network API in the GRA9 and GRA11 regions is experiencing increased latency. Customers Impact : Customers may experience slowness when performing network operations through the API or Horizon, such as creating or modifying networks, ports, floating IPs or security groups. 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.

  2. resolved Oct 14, 2026, 03:24 PM UTC

    We are pleased to inform you that the incident affecting our Public Cloud offering has been resolved. Start time : 14/10/2026 08:00 UTC End time : 14/10/2026 15:22 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Notice October 14, 2026

[SBG5][Public Cloud] - File Storage incident notification

Detected by Pingoru
Oct 14, 2026, 01:02 AM UTC
Resolved
Oct 14, 2026, 08:39 AM UTC
Duration
7h 37m
Affected: SBG5
Timeline · 1 update
  1. resolved Oct 14, 2026, 09:08 AM UTC

    We would like to inform you that an incident occurred affecting our File Storage offering in the SBG5 region. This incident has now been resolved. Please find the details of this incident below : Start time : 14/10/2026 01:02 UTC End time : 14/10/2026 08:39 UTC Impacted Service(s) : Creation of new File Storage shares was temporarily unavailable in the SBG5 region. Customers Impact : Customers were temporarily unable to provision new File Storage shares, as newly created shares ended up in error status. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.

Read the full incident report →

Major October 13, 2026

[SBG5][Public Cloud] - Managed Kubernetes Service incident notification

Detected by Pingoru
Oct 13, 2026, 03:22 PM UTC
Resolved
Oct 13, 2026, 04:00 PM UTC
Duration
37m
Affected: SBG5
Timeline · 3 updates
  1. identified Oct 13, 2026, 03:22 PM UTC

    We are currently experiencing an incident affecting our Managed Kubernetes Service offering in the SBG5 region. The root cause has been identified. Please find the details of this incident below : Start time : 13/10/2026 15:00 UTC Impacted Service(s) : Access to the Kubernetes API Server is temporarily unstable. Customers Impact : Customers may experience intermittent connectivity issues or errors when accessing the Kubernetes API Server of their clusters located in the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : Our teams are actively working 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.

  2. monitoring Oct 13, 2026, 03:46 PM UTC

    We would like to inform you that our service has been fully restored as of 13/10/2026 at 15:20 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : Start time : 13/10/2026 15:00 UTC Impacted Service(s) : Access to the Kubernetes API Server was temporarily unstable. Customers Impact : Customers may have experienced intermittent connectivity issues or errors when accessing the Kubernetes API Server of their clusters located in the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Oct 13, 2026, 04:00 PM UTC

    We would like to inform you that the incident affecting our Managed Kubernetes Service offering has now been resolved. Please find the details of this incident below : Start time : 13/10/2026 15:00 UTC End time : 13/10/2026 15:20 UTC Impacted Service(s) : Access to the Kubernetes API Server was temporarily unstable. Customers Impact : Customers may have experienced intermittent connectivity issues or errors when accessing the Kubernetes API Server of their clusters located in the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.

Read the full incident report →

Notice October 13, 2026

[GRA4/GRA5/GRA7/GRA9/GRA11][Public Cloud] - Compute Instance incident notification

Detected by Pingoru
Oct 13, 2026, 05:17 AM UTC
Resolved
Oct 13, 2026, 05:26 AM UTC
Duration
9m
Affected: GRA5GRA7GRA9GRA11GRA4
Timeline · 1 update
  1. resolved Oct 13, 2026, 05:29 AM UTC

    We would like to inform you that an incident occurred in the GRA4, GRA5, GRA7, GRA9 and GRA11 regions. This incident has now been resolved. Please find the details of this incident below : Start time : 13/10/2026 05:17 UTC End time : 13/10/2026 05:26 UTC Impacted Service(s) : Some instances in the GRA5, GRA7, GRA9 and GRA11 regions were unavailable. Customers Impact : Customers were temporarily unable to access their instances located in the specified regions. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.

Read the full incident report →

Major October 9, 2026

[GRA][Compute - Instance] - Compute Instance Incident Notification

Detected by Pingoru
Oct 09, 2026, 10:34 AM UTC
Resolved
Oct 09, 2026, 12:02 PM UTC
Duration
1h 28m
Affected: GRA1GRA3GRA5GRA7GRA9GRA11GRA4
Timeline · 3 updates
  1. investigating Oct 09, 2026, 10:34 AM UTC

    We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in GRA region. Here are some supplementary details : Start time : 09/10/2026 10:23 UTC Impacted Service(s) : Some instances in the GRA region are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified region. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  2. investigating Oct 09, 2026, 10:41 AM UTC

    We are continuing to investigate this issue.

  3. resolved Oct 09, 2026, 12:02 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 09/10/2026 10:23 UTC End time : 09/10/2026 10:37 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Notice October 9, 2026

[WAW1][Compute - Instance] - Compute Instance Incident Notification

Detected by Pingoru
Oct 09, 2026, 08:30 AM UTC
Resolved
Oct 09, 2026, 08:36 AM UTC
Duration
6m
Affected: WAW1
Timeline · 1 update
  1. resolved Oct 09, 2026, 08:47 AM UTC

    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.

Read the full incident report →

Minor October 8, 2026

[EU-WEST-PAR][Storage] - Object Storage S3 incident notification

Detected by Pingoru
Oct 08, 2026, 03:14 PM UTC
Resolved
Oct 15, 2026, 09:37 AM UTC
Duration
6d 18h
Affected: EU-WEST-PAR-AEU-WEST-PAR-BEU-WEST-PAR-C
Timeline · 4 updates
  1. investigating Oct 08, 2026, 03:14 PM UTC

    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.

  2. identified Oct 08, 2026, 04:43 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Object Storage S3 offer on the specific 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 may still experience some latency when accessing and using their objects located in EU-WEST-PAR region, though it has significantly decreased. Root Cause : This incident is caused by a software issue. Ongoing Actions : The incident has been identified and a significant reduction in latency has been observed. Our teams remain mobilised to fully 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.

  3. monitoring Oct 08, 2026, 06:15 PM UTC

    Service has been fully restored since 08/10/2026 18:14 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 08/10/2026 00:00 UTC Impacted Service(s) : Latency was observed for Object Storage S3 in the specified region. Customers Impact : Customers were temporarily facing latency when trying to access and use their objects located in EU-WEST-PAR region. Root Cause : This incident is caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

  4. resolved Oct 15, 2026, 09:37 AM UTC

    We are pleased to inform you that the incident affecting our Object Storage S3 offering has been resolved. Start time : 08/10/2026 00:00 UTC End time : 08/10/2026 18:14 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Notice October 8, 2026

[EU/CA][Storage] - Cold Archive Incident notification

Detected by Pingoru
Oct 08, 2026, 07:41 AM UTC
Resolved
Oct 08, 2026, 01:20 PM UTC
Duration
5h 38m
Affected: RBX-ARCHIVE
Timeline · 1 update
  1. resolved Oct 08, 2026, 07:41 AM UTC

    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 : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.

Read the full incident report →

Major October 7, 2026

[EU/CA][Storage] - Object Storage S3 incident notification

Detected by Pingoru
Oct 07, 2026, 01:11 PM UTC
Resolved
Oct 07, 2026, 02:02 PM UTC
Duration
50m
Affected: BHSGRADERBXSBGSGPSYDWAWYYZLIMAP-SOUTH-MUM-1EU-WEST-PAR-AEU-WEST-PAR-BEU-WEST-PAR-CEU-SOUTH-MIL-BEU-SOUTH-MIL-AEU-SOUTH-MIL-C
Timeline · 3 updates
  1. investigating Oct 07, 2026, 01:11 PM UTC

    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 09:24 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.

  2. monitoring Oct 07, 2026, 01:43 PM UTC

    Service has been fully restored since 07/10/2026 13:41 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 07/10/2026 12:36 UTC Impacted Service(s) : No more issue observed for Object Storage S3. Customers Impact : Customers are no longer facing 503/500 errors when trying to access their S3 buckets and objects We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Oct 07, 2026, 02:02 PM UTC

    We are pleased to inform you that the incident affecting our Object Storage S3 offering has been resolved. Start time : 07/10/2026 12:36 UTC End time : 07/10/2026 13:41 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Notice October 7, 2026

[AF-NORTH/EU-WEST/EU-NORTH][LocalZones] - IPv6 incident notification

Detected by Pingoru
Oct 07, 2026, 08:00 AM UTC
Resolved
Oct 07, 2026, 12:00 PM UTC
Duration
4h
Affected: AF-NORTH-LZ-RBAEU-WEST-LZ-DLNEU-NORTH-LZ-OSLEU-WEST-LZ-MNC
Timeline · 1 update
  1. resolved Oct 07, 2026, 12:27 PM UTC

    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.

Read the full incident report →

Notice October 7, 2026

[GRA][Compute - Instance] - Some Instances incident notification

Detected by Pingoru
Oct 07, 2026, 05:07 AM UTC
Resolved
Oct 07, 2026, 05:15 AM UTC
Duration
8m
Affected: GRA1GRA3GRA5GRA7GRA9GRA11GRA4
Timeline · 1 update
  1. resolved Oct 07, 2026, 05:42 AM UTC

    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.

Read the full incident report →

Notice October 4, 2026

[GRA5/GRA7][Compute - Instance] - Some Instances incident notification

Detected by Pingoru
Oct 04, 2026, 01:36 PM UTC
Resolved
Oct 04, 2026, 01:38 PM UTC
Duration
2m
Affected: GRA5GRA7
Timeline · 1 update
  1. resolved Oct 04, 2026, 01:47 PM UTC

    We had an incident on Compute - Instance offer which has now been resolved. Here are some supplementary details : Start time : 04/10/2026 13:36 UTC End time : 04/10/2026 13:38 UTC Impacted Service(s) : Some instances in the GRA5 and GRA7 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.

Read the full incident report →

Major October 3, 2026

[GRA][Storage] - Object Storage S3 incident notification

Detected by Pingoru
Oct 03, 2026, 03:06 AM UTC
Resolved
Oct 05, 2026, 11:47 AM UTC
Duration
2d 8h
Affected: GRA
Timeline · 3 updates
  1. identified Oct 03, 2026, 03:06 AM UTC

    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) : You may experience issues accessing your Object Storage S3 service. Customers Impact : Customers may experience issues downloading or uploading their objects due to 500/503 errors. 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.

  2. monitoring Oct 03, 2026, 04:47 AM UTC

    We would like to inform you that our service has been fully restored as of 03/10/2026 at 04:27 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : Start time : 03/10/2026 02:00 UTC Impacted Service(s) : Access to the Object Storage S3 service was disrupted in the GRA region. Customers Impact : Customers may have experienced issues downloading or uploading their objects due to 500/503 errors. Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Oct 05, 2026, 11:47 AM UTC

    We are pleased to inform you that the incident affecting our Object Storage S3 offering has been resolved. Start time : 03/10/2026 02:00 UTC End time : 03/10/2026 at 04:27 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major October 1, 2026

[US-EAST-LZ-MIA][Network] - Localzone incident notification

Detected by Pingoru
Oct 01, 2026, 06:09 AM UTC
Resolved
Oct 01, 2026, 08:03 AM UTC
Duration
1h 54m
Affected: US-EAST-LZ-MIA
Timeline · 3 updates
  1. investigating Oct 01, 2026, 06:09 AM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Network offer on the specific US-EAST-LZ-MIA region. Here are some supplementary details : Start time : 01/10/2026 05:41 UTC Impacted Service(s) : The public network may temporarily be slowed down or become unstable. Customers Impact : Customers may temporarily experience latency or disruptions on the public network in this region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  2. monitoring Oct 01, 2026, 07:29 AM UTC

    Service has been fully restored since 01/10/2026 07:26 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 01/10/2026 05:06 UTC Impacted Service(s) : The public network was temporarily slowed down or became unstable. Customers Impact : Customers temporarily experienced latency or disruptions on the public network in this region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Oct 01, 2026, 08:03 AM UTC

    We are pleased to inform you that the incident affecting our LocalZones offering has been resolved. Start time : 01/10/2026 05:06 UTC End time : 01/10/2026 07:26 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major September 30, 2026

[DE1/DE2][Compute - Instance] - Compute Instance Incident Notification

Detected by Pingoru
Sep 30, 2026, 11:46 AM UTC
Resolved
Sep 30, 2026, 12:45 PM UTC
Duration
58m
Affected: DE1
Timeline · 2 updates
  1. identified Sep 30, 2026, 11:46 AM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offering in the specific LIM3 region. Here are some supplementary details : Start time : 30/09/2026 11:00 UTC Impacted Service(s) : Some instances in the LIM3 region are temporarily unreachable. Customers Impact : Some customers are temporarily unable to access instances located in the specified region. Root Cause : This incident is caused by this maintenance : https://network.status-ovhcloud.com/incidents/psvb5n915gr6 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.

  2. resolved Sep 30, 2026, 12:45 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 30/09/2026 11:00 UTC End time : 30/09/2026 12:37 UTC Root Cause : This incident was caused by this maintenance : https://network.status-ovhcloud.com/incidents/psvb5n915gr6 We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Notice September 29, 2026

[EU-SOUTH-MIL][Identity, Security & Operations] - MKS Cluster incident notification

Detected by Pingoru
Sep 29, 2026, 03:14 PM UTC
Resolved
Sep 29, 2026, 04:03 PM UTC
Duration
48m
Affected: EU-SOUTH-MIL
Timeline · 2 updates
  1. investigating Sep 29, 2026, 03:14 PM UTC

    We are currently investigating an incident affecting our services, which is causing temporary issue in EU-SOUTH-MIL Region. Here are some supplementary details : Start time : 29/09/2026 10:00 UTC Impacted Service(s) : MKS cluster delivery and deletion is may have issue. Customers Impact : Some customers may experience difficulties when creating or deleting new MKS clusters. 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.

  2. resolved Sep 29, 2026, 04:03 PM UTC

    We are pleased to inform you that the incident affecting our services has been resolved. Start time : 29/09/2026 10:00 UTC End time : 29/09/2026 15:45 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major September 25, 2026

[SBG5][Public Cloud] - Compute Instance incident notification

Detected by Pingoru
Sep 25, 2026, 07:18 PM UTC
Resolved
Sep 25, 2026, 08:28 PM UTC
Duration
1h 9m
Affected: SBG5
Timeline · 2 updates
  1. identified Sep 25, 2026, 07:18 PM UTC

    We are currently experiencing an incident affecting our Public Cloud offering in the SBG5 region. The root cause has been identified. Please find the details of this incident below : Start time : 25/09/2026 18:26 UTC Impacted Service(s) : Some instances in the SBG5 region are unavailable. Customers Impact : Customers are temporarily unable to access their instances located in the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : Our teams are actively working 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.

  2. resolved Sep 25, 2026, 08:28 PM UTC

    We would like to inform you that the incident affecting our Compute Instance offering has now been resolved. Please find the details of this incident below : Start time : 25/09/2026 18:26 UTC End time : 25/09/2026 20:24 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.

Read the full incident report →

Major September 25, 2026

[US-EAST-VA][Storage] - Object Storage incident notification

Detected by Pingoru
Sep 25, 2026, 05:00 PM UTC
Resolved
Sep 29, 2026, 02:37 PM UTC
Duration
3d 21h
Affected: US-EAST-VA-1
Timeline · 3 updates
  1. investigating Sep 25, 2026, 05:00 PM UTC

    We are currently experiencing an incident affecting our Object Storage offering, which is causing temporary latency and availability issues in the US-EAST-VA region. Please find the details of this incident below : Start time : 25/09/2026 11:00 UTC Impacted Service(s) : Object Storage High Performance and Standard are temporarily facing perturbations in the US-EAST-VA region. Customers Impact : Customers may experience increased latency and 503 errors when accessing their data located in the specified region. 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.

  2. monitoring Sep 25, 2026, 06:41 PM UTC

    We would like to inform you that our service has been fully restored as of 25/09/2026 at 18:20 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : Start time : 25/09/2026 11:00 UTC Impacted Service(s) : Object Storage High Performance and Standard were temporarily facing perturbations in the US-EAST-VA region. Customers Impact : Customers may have experienced increased latency and 503 errors when accessing their data located in the specified region. Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Sep 29, 2026, 02:37 PM UTC

    We are pleased to inform you that the incident affecting our Storage offering has been resolved. Start time : 25/09/2026 11:00 UTC End time : 29/09/2026 14:22 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →