OVHcloud Status · History · Incident #5481
RESOLVED[BHS1/BHS5][Compute - Instance] - Some Instances Incident Notification
Major · Started Jul 13, 2026 · 5:22 PM
$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 #5481
RESOLVEDMajor · Started Jul 13, 2026 · 5:22 PM
Duration
7h 59m
Severity
Major
Detection lead
—
User reports
—
Summary
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. <b>Start time :</b> 13/07/2026 16:55 UTC <b>End time :</b> 13/07/2026 22:55 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.
Started
Jul 13, 2026 · 5:22 PM
Resolved
Jul 14, 2026 · 1:21 AM
Duration
7h 59m
Severity
Major
Event timeline
Identified
Jul 13 · 5:22 PM OVHcloudWe 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 : <b>Start time :</b> 13/07/2026 16:55 UTC <b>Impacted Service(s) :</b> Some instances in the BHS1/BHS5 regions are unreachable. <b>Customers Impact :</b> Some customers are temporarily unable to access instances located on the specified regions. <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.
Identified
Jul 13 · 5:33 PM OVHcloudWe 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 : <b>Start time :</b> 13/07/2026 16:55 UTC <b>Impacted Service(s) :</b> Some instances in the BHS1/BHS5 regions are unreachable. <b>Customers Impact :</b> Some customers are temporarily unable to access instances located on the specified regions. <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.
Resolved
Jul 14 · 1:21 AM OVHcloudWe are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. <b>Start time :</b> 13/07/2026 16:55 UTC <b>End time :</b> 13/07/2026 22:55 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.
Pattern
[GRA5/7/9/11][Compute - Instance] - Some instances incident notification
Jul 20, 2026 · 32m
View incident →[GLOBAL][Databases] - Database incident notification
Jul 20, 2026
View incident →[GRA11][Compute - Instance] - Instance creation incident notification
Jul 19, 2026 · 1h 26m
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