OVHcloud Status · History · Incident #5691
ACTIVE INCIDENT[GLOBAL][Databases] - Database incident notification
Major · Started Jul 20, 2026 · 7:48 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
OVHcloud Status · History · Incident #5691
ACTIVE INCIDENTMajor · Started Jul 20, 2026 · 7:48 AM
Duration
Ongoing
Severity
Major
Detection lead
—
User reports
—
Summary
<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.
Started
Jul 20, 2026 · 7:48 AM
Status
Monitoring
Duration
Ongoing
Severity
Major
Event timeline
Identified
Jul 20 · 7:48 AM OVHcloudWe 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> This incident is caused by a hardware issue. <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.
Identified
Jul 20 · 4:33 PM OVHcloudWe 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.
Identified
Jul 20 · 8:35 PM OVHcloudPlease 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.
Monitoring
Jul 20 · 10:15 PM OVHcloud<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.
Pattern
[GRA5/7/9/11][Compute - Instance] - Some instances incident notification
Jul 20, 2026 · 32m
View incident →[GRA11][Compute - Instance] - Instance creation incident notification
Jul 19, 2026 · 1h 26m
View incident →[GRA][AI & Machine Learning] - AI Deploy/Training/Notebooks incident notification
Jul 19, 2026 · 4m
View incident →Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026