Public Cloud Outage History

Public Cloud is up right now

Public Cloud had 123 outages in the last 2 years totaling 334h 43m of downtime — averaging 5.1 incidents per month.

There were 123 Public Cloud outages since October 30, 2025 totaling 334h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://public-cloud.status-ovhcloud.com

Major August 3, 2026

[GLOBAL][Data & Analytics] - Data Platform Incident Notification

Detected by Pingoru
Aug 03, 2026, 02:14 PM UTC
Resolved
Aug 03, 2026, 03:33 PM UTC
Duration
1h 18m
Affected: Data & Analytics || Data Platform
Timeline · 3 updates
  1. investigating Aug 03, 2026, 02:14 PM UTC

    We are currently experiencing an event affecting our Data & Analytics offer. Start time : 03/08/2026 13:47 UTC Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible. We apologize for any inconvenience caused and appreciate your understanding.

  2. identified Aug 03, 2026, 02:50 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on the specific GLOBAL region. Here are some supplementary details : Start time : 03/08/2026 13:47 UTC Impacted Service(s) : DPE jobs and query execution are experiencing degraded performance, resulting in delays and possible failures. Customers Impact : Customers may experience delays and intermittent failures when running DPE jobs and processing queries. Root Cause : This incident is caused by a software issue. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Aug 03, 2026, 03:33 PM UTC

    We are pleased to inform you that the incident affecting our Data & Analytics offering has been resolved. Start time : 03/08/2026 13:47 UTC End time : 03/08/2026 14:00 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 July 29, 2026

[GRA][Storage] - Object Storage incident notification

Detected by Pingoru
Jul 29, 2026, 01:06 PM UTC
Resolved
Jul 29, 2026, 01:06 PM UTC
Duration
Affected: GRA
Timeline · 1 update
  1. resolved Jul 29, 2026, 01:06 PM UTC

    We had an incident on our Object Storage offer in GRA region which has now been resolved. Here are some supplementary details : Start time : 29/07/2026 06:00 UTC End time : 29/07/2026 11:00 UTC Impacted Service(s) : Slowness and 504 error were observed for object storage located in GRA. Customers Impact : Customers were temporarily facing slowness and 504 error when trying to access and use their objects 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 →

Major July 28, 2026

[WAW1][Compute - Instance] - Some instances incident notification

Detected by Pingoru
Jul 28, 2026, 05:12 PM UTC
Resolved
Jul 28, 2026, 05:21 PM UTC
Duration
8m
Affected: WAW1
Timeline · 2 updates
  1. identified Jul 28, 2026, 05:12 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific WAW1 region. Here are some supplementary details : Start time : 28/07/2026 17:06 UTC Impacted Service(s) : Some instances in the WAW1 region are unreachable. Customers Impact : Some customers are temporarily unable to access instances located in the specified 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. resolved Jul 28, 2026, 05:21 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 28/07/2026 17:06 UTC End time : 28/07/2026 17:12 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 July 27, 2026

[GRA11][Network] - Load Balancer incident notification

Detected by Pingoru
Jul 27, 2026, 12:52 PM UTC
Resolved
Jul 28, 2026, 03:15 PM UTC
Duration
1d 2h
Affected: GRA11GRA11
Timeline · 4 updates
  1. identified Jul 27, 2026, 12:52 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer in the specific GRA11 region. Here are some supplementary details : Start time : 27/07/2026 07:41 UTC Impacted Service(s) : Creation of Public Cloud instances on GRA11 LoadBalancer is temporarily unavailable. Customers Impact : Customers are temporarily unable to create new Public Cloud instances on LoadBalancer. 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 Jul 28, 2026, 11:25 AM UTC

    We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Our teams are currently working on a fix to resolve the issue. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  3. identified Jul 28, 2026, 12:13 PM UTC

    We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The majority of customers are no longer impacted by the incident. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  4. resolved Jul 28, 2026, 03:15 PM UTC

    We are pleased to inform you that the incident affecting our Load Balancer offering has been resolved. Start time : 27/07/2026 07:41 UTC End time : 28/07/2026 14: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 July 27, 2026

[UK1][Compute - Instance] - Some instances incident notification

Detected by Pingoru
Jul 27, 2026, 06:33 AM UTC
Resolved
Jul 27, 2026, 08:39 AM UTC
Duration
2h 5m
Affected: UK1
Timeline · 2 updates
  1. identified Jul 27, 2026, 06:33 AM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific UK1 region. Here are some supplementary details : Start time : 27/07/2026 06:19 UTC Impacted Service(s) : Some instances in the UK1 region are unreachable. Customers Impact : Some customers are temporarily unable to access instances located in the specified 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. resolved Jul 27, 2026, 08:39 AM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering in UK1 region has been resolved. Start time : 27/07/2026 06:19 UTC End time : 27/07/2026 07:40 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 July 23, 2026

[EU-WEST-PAR][Storage] - Object storage S3 Standard Incident Notification

Detected by Pingoru
Jul 23, 2026, 07:14 PM UTC
Resolved
Jul 24, 2026, 12:58 PM UTC
Duration
17h 43m
Affected: EU-WEST-PAR-AEU-WEST-PAR-BEU-WEST-PAR-C
Timeline · 3 updates
  1. investigating Jul 23, 2026, 07:14 PM UTC

    We are currently investigating an incident affecting our Storage offering, which is causing temporary issue in the EU-WEST-PAR region. Here are some supplementary details : Start time : 23/07/2026 18:00 UTC Impacted Service(s) : Intermittent HTTP 503 errors may affect object upload and download operations. Customers Impact : Customers may experience issues downloading or uploading their objects due to 503 errors. 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 Jul 23, 2026, 11:30 PM UTC

    We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The services s are operational again since 23/07/2026 23:15 UTC. Ongoing Actions : Our team will monitor the situation. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Jul 24, 2026, 12:58 PM UTC

    We are pleased to inform you that the incident affecting our Storage offering has been resolved. Start time : 23/07/2026 18:00 UTC End time : 23/07/2026 23:15 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 July 23, 2026

[GRA1/3/9/11][Compute - Instance] - Some Instances Incident Notification

Detected by Pingoru
Jul 23, 2026, 06:05 PM UTC
Resolved
Jul 23, 2026, 06:34 PM UTC
Duration
29m
Affected: GRA1GRA3GRA9GRA11
Timeline · 2 updates
  1. identified Jul 23, 2026, 06:05 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific GRA1/3/9/11 regions. Here are some supplementary details : Start time : 23/07/2026 17:52 UTC Impacted Service(s) : Some instances in the GRA1/3/9/11 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. 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. resolved Jul 23, 2026, 06:34 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 23/07/2026 17:52 UTC End time : 23/07/2026 17:58 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 July 20, 2026

[GRA5/7/9/11][Compute - Instance] - Some instances incident notification

Detected by Pingoru
Jul 20, 2026, 03:24 PM UTC
Resolved
Jul 20, 2026, 03:57 PM UTC
Duration
32m
Affected: GRA5GRA7GRA9GRA11
Timeline · 2 updates
  1. monitoring Jul 20, 2026, 03:24 PM UTC

    Service has been fully restored since 20/07/2026 15:10 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 20/07/2026 15:02 UTC Impacted Service(s) : Some instances in the GRA5, GRA7, GRA9 and GRA11 regions were unreachable. Customers Impact : Some customers were temporarily unable to access instances located on the specified regions. We apologize for any inconvenience caused and appreciate your understanding.

  2. resolved Jul 20, 2026, 03:57 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 20/07/2026 15:02 UTC End time : 20/07/2026 15:10 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 July 20, 2026

[GLOBAL][Databases] - Database incident notification

Detected by Pingoru
Jul 20, 2026, 07:48 AM UTC
Resolved
Jul 21, 2026, 10:19 AM UTC
Duration
1d 2h
Affected: BHSBHSBHSDEDEDEGRAGRAGRAEU-SOUTH-MILEU-SOUTH-MILEU-SOUTH-MILAP-SOUTH-MUMAP-SOUTH-MUMAP-SOUTH-MUMEU-WEST-PAREU-WEST-PAREU-WEST-PARRBXRBXRBXSBGSBGSBGSGPSGPSGPUS-EAST-VAUS-EAST-VAUKUKUKUS-EAST-VAUS-WEST-ORUS-WEST-ORWAWWAWUS-WEST-ORWAW
Timeline · 5 updates
  1. identified Jul 20, 2026, 07:48 AM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Databases offer on the specific GRA11 Region. Here are some supplementary details : Start time : 19/07/2026 18:00 UTC Impacted Service(s) : Some Database are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their Database located on the specified region. Root Cause : This incident is caused by a hardware issue. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  2. identified Jul 20, 2026, 04:33 PM UTC

    We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Databases are temporarily unavailable in GLOBAL region. 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. identified Jul 20, 2026, 08:35 PM UTC

    Please find an update of this incident below : Update: Database access is being progressively restored in all regions, with the exception of GRA11. Pending orders are now being progressively delivered. As a precaution, new orders remain temporarily suspended. Ongoing Actions : Our teams continue to restore the remaining impacted region and are closely monitoring the situation. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  4. monitoring Jul 20, 2026, 10:15 PM UTC

    Update: Database access has been restored across all regions. Our teams are continuing to work on the remaining impacted databases in GRA11. Pending orders are being delivered, and new orders are no longer suspended. Monitoring remains in place to ensure long-term stability. We apologize for any inconvenience caused and appreciate your understanding and patience.

  5. resolved Jul 21, 2026, 10:19 AM UTC

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

Read the full incident report →

Major July 19, 2026

[GRA11][Compute - Instance] - Instance creation incident notification

Detected by Pingoru
Jul 19, 2026, 05:50 PM UTC
Resolved
Jul 19, 2026, 07:16 PM UTC
Duration
1h 26m
Affected: GRA11
Timeline · 2 updates
  1. identified Jul 19, 2026, 05:50 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific region GRA11. Here are some supplementary details : Start time : 19/07/2026 16:50 UTC Impacted Service(s) : Creation of Public Cloud instances in GRA11 region is temporarily unavailable. Customers Impact : Customers are temporarily unable to create new Public Cloud instances. Instances created during the incident will remain stuck in a "building"/"spawning" state and will not become operational. Once the incident is resolved, customers are advised to delete these instances and create new ones. Root Cause : This incident is caused by our provider. 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 Jul 19, 2026, 07:16 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering in GRA11 has been resolved. Start time : 19/07/2026 16:50 UTC End time : 19/07/2026 19:14 UTC Root Cause : This incident was caused by our provider. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major July 19, 2026

[GRA][AI & Machine Learning] - AI Deploy/Training/Notebooks incident notification

Detected by Pingoru
Jul 19, 2026, 02:27 PM UTC
Resolved
Jul 19, 2026, 02:31 PM UTC
Duration
4m
Affected: GRAGRAAI & Machine Learning || AI Endpoint
Timeline · 2 updates
  1. investigating Jul 19, 2026, 02:27 PM UTC

    We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary issue in the GRA region. Here are some supplementary details : Start time : 19/07/2026 12:40 UTC Impacted Service(s) : AI Deploy, AI Training and AI Notebooks are temporarily unavailable. Customers Impact : Customers are temporarily unable to access and use models in the specified offers. 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 Jul 19, 2026, 02:31 PM UTC

    We are pleased to inform you that the incident affecting our AI & Machine Learning offering on AI Deploy, AI Training and AI Notebooks has been resolved. Start time : 19/07/2026 12:40 UTC End time : 19/07/2026 14:30 UTC Root Cause : This incident was caused by our provider. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major July 16, 2026

[BHS/GRA][Identity, Security & Operations] - Logs Data Platform incident notification

Detected by Pingoru
Jul 16, 2026, 12:03 PM UTC
Resolved
Jul 16, 2026, 01:02 PM UTC
Duration
58m
Affected: BHSGRA
Timeline · 2 updates
  1. investigating Jul 16, 2026, 12:03 PM UTC

    We are currently experiencing an incident affecting our Logs Data Platform service, which is causing temporary availability issues. Please find the details of this incident below : Start time : 15/07/2026 18:00 UTC Impacted Service(s) : The WebSocket connection on Logs Data Platform is temporarily unavailable. Customers Impact : Customers are temporarily unable to use the Logs Data Platform WebSocket connection. 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 Jul 16, 2026, 01:02 PM UTC

    We are pleased to inform you that the incident affecting our Logs Data Platform service has been resolved. Start time : 15/07/2026 18:00 UTC End time : 16/07/2026 13:00 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 July 14, 2026

[WAW][Object Storage] - Object Storage Swift Incident Notification

Detected by Pingoru
Jul 14, 2026, 08:08 AM UTC
Resolved
Jul 14, 2026, 09:40 AM UTC
Duration
1h 32m
Affected: WAW
Timeline · 3 updates
  1. investigating Jul 14, 2026, 08:08 AM UTC

    We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the region WAW. Here are some supplementary details : Start time : 14/07/2026 07:49 UTC Impacted Service(s) : Object Storage S3. Customers Impact : Customers may experience connection problems while trying to access Object Storage S3 in WAW. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  2. identified Jul 14, 2026, 08:38 AM UTC

    We have determined the origin of the issue affecting our Object Storage Swift offer in WAW. Here are some supplementary details : Start time : 14/07/2026 07:59 UTC Impacted Service(s) : Object Storage Swift is temporarily unavailable. Customers Impact : Customers may experience connection problems while trying to access Object Storage Swift in WAW. 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.

  3. resolved Jul 14, 2026, 09:40 AM UTC

    We are pleased to inform you that the incident affecting our Object Storage Swift offering has been resolved. Start time : 14/07/2026 07:49 UTC End time : 14/07/2026 08:15 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 July 13, 2026

[BHS1/BHS5][Compute - Instance] - Some Instances Incident Notification

Detected by Pingoru
Jul 13, 2026, 05:22 PM UTC
Resolved
Jul 14, 2026, 01:21 AM UTC
Duration
7h 59m
Affected: BHS1BHS5
Timeline · 3 updates
  1. identified Jul 13, 2026, 05:22 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific BHS1/BHS5 regions. Here are some supplementary details : Start time : 13/07/2026 19:34 UTC Impacted Service(s) : Some instances in the BHS1/BHS5 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. 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 Jul 13, 2026, 05:33 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific BHS1/BHS5 regions. Here are some supplementary details : Start time : 13/07/2026 19:34 UTC Impacted Service(s) : Some instances in the BHS1/BHS5 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. 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.

  3. resolved Jul 14, 2026, 01:21 AM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 13/07/2026 16:55 UTC End time : 13/07/2026 22:55 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 July 10, 2026

[EU-WEST-PAR][Containers & Orchestration] - Managed Private Registry incident notification

Detected by Pingoru
Jul 10, 2026, 09:30 PM UTC
Resolved
Jul 11, 2026, 12:18 AM UTC
Duration
2h 47m
Affected: EU-WEST-PAR
Timeline · 2 updates
  1. identified Jul 10, 2026, 09:30 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Managed Private Registry service on the EU-WEST-PAR region. Here are some supplementary details : Start time : 10/07/2026 20:20 UTC Impacted Service(s) : Registries are temporarily unavailable. Customers Impact : Customers are temporarily facing issues when trying to use connect to Harbor UI, pull or push new images. Root Cause : This incident is caused by a hardware issue. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  2. resolved Jul 11, 2026, 12:18 AM UTC

    We are pleased to inform you that the incident affecting our Managed Private Registry service has been resolved. Start time : 10/07/2026 20:20 UTC End time : 11/07/2026 00:10 UTC Root Cause : This incident was caused by this maintenance : https://public-cloud.status-ovhcloud.com/incidents/m5qn00qgl9zh We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major July 9, 2026

[EU-WEST-PAR][Containers & Orchestration] - Loadbalancer/API/Instance provisioning incident notification

Detected by Pingoru
Jul 09, 2026, 08:07 PM UTC
Resolved
Jul 10, 2026, 01:55 AM UTC
Duration
5h 48m
Affected: EU-WEST-PAR
Timeline · 3 updates
  1. investigating Jul 09, 2026, 08:07 PM UTC

    We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary issue in the EU-WEST-PAR region. Here are some supplementary details : Start time : 09/07/2026 19:20 UTC Impacted Service(s) : Public Cloud API is temporarily facing perturbations. Creation or modification of any LoadBalancer can have issues. Customers Impact : Customers are temporarily facing issues when trying to use the API, create or modify their Loadbalancer. 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 Jul 09, 2026, 08:19 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our DNS offer on the specific region. Here are some supplementary details : Start time : 09/07/2026 19:20 UTC Impacted Service(s) : Public Cloud API is temporarily facing perturbations. Creation or modification of any LoadBalancer can have issues. Customers Impact : Customers are temporarily facing issues when trying to use the API, create or modify their Loadbalancer. Root Cause : This incident is caused by a software issue. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Jul 10, 2026, 01:55 AM UTC

    We are pleased to inform you that the incident affecting our Load Balancer service has been resolved. Start time : 09/07/2026 19:20 UTC End time : 10/07/2026 01:50 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 July 9, 2026

[GRA][Network] - Public network incident notification

Detected by Pingoru
Jul 09, 2026, 01:45 PM UTC
Resolved
Jul 13, 2026, 12:05 PM UTC
Duration
3d 22h
Affected: GRA1GRA3GRA5GRA7GRA9GRA11
Timeline · 2 updates
  1. identified Jul 09, 2026, 01:45 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Network offer on the specific region. Here are some supplementary details : Start time : 09/07/2026 13:40 UTC Impacted Service(s) : Paquet loss is being observed for IPv6. Customers Impact : Customers are temporarily facing packet loss on IPv6 when using services located in GRA region. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/cfjg549ghh2y 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 Jul 13, 2026, 12:05 PM UTC

    We are pleased to inform you that the incident affecting our Network offering has been resolved. Start time : 09/07/2026 13:40 UTC End time : 13/07/2026 11:10 UTC Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/cfjg549ghh2y We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Notice July 9, 2026

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

Detected by Pingoru
Jul 09, 2026, 12:24 PM UTC
Resolved
Jul 09, 2026, 12:24 PM UTC
Duration
Affected: SBG
Timeline · 1 update
  1. resolved Jul 09, 2026, 12:24 PM UTC

    We had an incident on S3 Object Storage offer which has now been resolved. Here are some supplementary details : Start time : 09/07/2026 11:46 UTC End time : 09/07/2026 11:48 UTC Impacted Service(s) : Object storage service in SBG region was temporarily unavailable for some customers. Customers Impact : Some customers were getting 503 error when trying to connect to their object storage 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 →

Major July 7, 2026

[GRA][AI & Machine Learning] - AI payload incident notification

Detected by Pingoru
Jul 07, 2026, 03:10 PM UTC
Resolved
Jul 07, 2026, 03:10 PM UTC
Duration
Affected: AI & Machine Learning || AI Endpoint
Timeline · 2 updates
  1. monitoring Jul 07, 2026, 12:31 PM UTC

    Service has been fully restored since 07/07/2026 11:56 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 07/07/2026 11:45 UTC Impacted Service(s) : Creation of AI payloads was temporarily unavailable in GRA region. Customers Impact : Customers were temporarily unable to create AI payloads. We apologize for any inconvenience caused and appreciate your understanding.

  2. resolved Jul 07, 2026, 03:10 PM UTC

    We are pleased to inform you that the incident affecting our offering has been resolved. Start time : 07/07/2026 11:45 UTC End time : 07/07/2026 11:56 UTC Root Cause : This incident was caused by a network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major July 6, 2026

[GRA5/7/9/11][Containers & Orchestration] - Managed Kubernetes Service Incident Notification

Detected by Pingoru
Jul 06, 2026, 11:30 PM UTC
Resolved
Jul 08, 2026, 09:34 AM UTC
Duration
1d 10h
Affected: GRA5GRA7GRA9GRA11
Timeline · 3 updates
  1. investigating Jul 06, 2026, 11:30 PM UTC

    We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary availability issue in the GRA5/7/9/11 regions. Here are some supplementary details : Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Kubernetes Service is experiencing delays in managed node provisioning. Customers Impact : Customers may experience network disruptions when using the load balancer and delays in managed node delivery. 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 Jul 07, 2026, 01:43 AM UTC

    Service has been fully restored since 07/07/2026 01:25 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Kubernetes Service experienced delays in managed node provisioning. Customers Impact : Customers may have experienced network disruptions when using the load balancer and delays in managed node delivery. 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 Jul 08, 2026, 09:34 AM UTC

    We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved. Start time : 06/07/2026 20:08 UTC End time : 07/07/2026 01: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 →

Major July 6, 2026

[GRA][Containers & Orchestration] - Managed Private Registry Incident Notification

Detected by Pingoru
Jul 06, 2026, 10:24 PM UTC
Resolved
Jul 08, 2026, 09:34 AM UTC
Duration
1d 11h
Affected: GRA
Timeline · 3 updates
  1. investigating Jul 06, 2026, 10:24 PM UTC

    We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary availability issue in the GRA region. Here are some supplementary details : Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Private Registry service may experience intermittent disruptions or temporary unavailability. Customers Impact : Customers may experience issues pushing, pulling, or deploying container images. 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 Jul 07, 2026, 01:39 AM UTC

    Service has been fully restored since 07/07/2026 01:25 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 06/07/2026 20:08 UTC Impacted Service(s) : The Managed Private Registry service experienced intermittent disruptions or temporary unavailability. Customers Impact : Customers may have experienced issues pushing, pulling, or deploying container images. 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 Jul 08, 2026, 09:34 AM UTC

    We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved. Start time : 06/07/2026 20:08 UTC End time : 07/07/2026 01: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 July 6, 2026

[GRA][Object Storage] - Object Storage Swift Incident Notification

Detected by Pingoru
Jul 06, 2026, 02:22 PM UTC
Resolved
Jul 08, 2026, 12:43 PM UTC
Duration
1d 22h
Affected: GRA
Timeline · 3 updates
  1. investigating Jul 06, 2026, 02:22 PM UTC

    We are currently investigating an incident affecting our Storage and Backups offering, which is causing temporary functionality issue in GRA2 region. Here are some supplementary details : Start time : 06/07/2026 14:00 UTC Impacted Service(s) : Slowness and 504 error in response time Customers Impact : Some customers might face slowness or 504 error in response time in 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. monitoring Jul 06, 2026, 03:31 PM UTC

    Service has been fully restored since 06/07/2026 15:25 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 06/07/2026 14:00 UTC Impacted Service(s) : Slowness and 504 error in response time Customers Impact : Some customers might have faced slowness or 504 error in response time in specified region. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Jul 08, 2026, 12:43 PM UTC

    We are pleased to inform you that the incident affecting our Object Storage Swift offering has been resolved. Start time : 06/07/2026 14:00 UTC End time : 06/07/2026 15:25 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 July 3, 2026

[GRA1/3/9][Compute - Instance] - Some Instances Incident Notification

Detected by Pingoru
Jul 03, 2026, 01:39 PM UTC
Resolved
Jul 03, 2026, 06:57 PM UTC
Duration
5h 18m
Affected: GRA1GRA3GRA9
Timeline · 2 updates
  1. identified Jul 03, 2026, 01:39 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific GRA1/3/9 regions. Here are some supplementary details : Start time : 03/07/2026 12:55 UTC Impacted Service(s) : Some instances in the GRA1/3/9 regions are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified regions. 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. resolved Jul 03, 2026, 06:57 PM UTC

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 03/07/2026 12:55 UTC End time : 03/07/2026 18:20 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 July 3, 2026

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

Detected by Pingoru
Jul 03, 2026, 01:05 PM UTC
Resolved
Jul 03, 2026, 01:05 PM UTC
Duration
Affected: AI & Machine Learning || AI Endpoint
Timeline · 1 update
  1. resolved Jul 03, 2026, 01:05 PM UTC

    We had an incident on AI & Machine Learning offer which has now been resolved. Here are some supplementary details : Start time : 02/07/2026 15:00 UTC End time : 03/07/2026 08:15 UTC Impacted Service(s) : All models on AI Endpoints have experienced latency and some 503 errors. Customers Impact : Customers experienced increased latency and intermittent 503 errors across all models on AI Endpoints. 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 →