Major impactResolvedCloud

OVHcloud outage: [GLOBAL][Databases] - Database incident notification

OVHcloud reported this major-impact incident on its official status page on Jul 20, 2026, 07:48 UTC. It was resolved after 1d 2h.

Right now OVHcloud is having a partial outage. Live OVHcloud status →

🔔 Get alerted when OVHcloud has issuesFree · email alerts · no credit card
Jul 20, 2026, 07:48 UTC
started
Jul 21, 2026, 10:19 UTC
resolved
1d 2h
duration
Major
impact

Affected components

  • AP-SOUTH-MUM
  • BHS
  • DE
  • EU-SOUTH-MIL
  • EU-WEST-PAR
  • GRA
  • RBX
  • SBG
  • SGP
  • UK
  • US-EAST-VA
  • US-WEST-OR
  • WAW
  1. resolvedJul 21, 2026, 10:19 UTC

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

  2. monitoringJul 20, 2026, 22:15 UTC

    <b>Update:</b> 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.

  3. identifiedJul 20, 2026, 20:35 UTC

    Please find an update of this incident below : <b>Update:</b> 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. <b>Ongoing Actions :</b> 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. identifiedJul 20, 2026, 16:33 UTC

    We have new information regarding the incident that affected your service(s). Please find below an update on the situation: <b>Update : </b> Customers are temporarily unable to access and fork their databases. Please note that no data has been lost, and all data remains intact. <b>Ongoing Actions :</b> 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.

  5. identifiedJul 20, 2026, 07:48 UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Databases offering Here are some supplementary details : <b>Start time :</b> 19/07/2026 18:00 UTC <b>Impacted Service(s) :</b> Some Database are temporarily unavailable. <b>Customers Impact :</b> Customers are temporarily unable to access their Database located on the specified region. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. <b>Ongoing Actions :</b> 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in OVHcloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does OVHcloud have incidents?

OVHcloud reported 39 incidents in the last 90 days, 30 of them major or critical. A typical incident lasted 3h 19m. See OVHcloud's uptime and incident history

OVHcloud outage on Jul 20, 2026: [GLOBAL][Databases] - Database incident notification · APIStatus.watch