OVHcloud Status · History · Incident #5928
RESOLVED[GRA11][Network] - Load Balancer incident notification
Major · Started Jul 27, 2026 · 12:52 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 #5928
RESOLVEDMajor · Started Jul 27, 2026 · 12:52 PM
Duration
1d 2h 22m
Severity
Major
Detection lead
—
User reports
—
Summary
We are pleased to inform you that the incident affecting our Load Balancer offering has been resolved. <b>Start time :</b> 27/07/2026 07:41 UTC <b>End time :</b> 28/07/2026 14:45 UTC <b>Root Cause :</b> This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Started
Jul 27, 2026 · 12:52 PM
Resolved
Jul 28, 2026 · 3:15 PM
Duration
1d 2h 22m
Severity
Major
Event timeline
Identified
Jul 27 · 12:52 PM OVHcloudWe are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Load Balancer offer in the specific GRA11 region. Here are some supplementary details : <b>Start time :</b> 27/07/2026 07:41 UTC <b>Impacted Service(s) :</b> Creation of Public Cloud instances on GRA11 LoadBalancer is temporarily unavailable. <b>Customers Impact :</b> Customers are temporarily unable to create new Public Cloud instances on LoadBalancer. <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 28 · 11:25 AM OVHcloudWe have new information regarding the incident that affected your service(s). Please find below an update on the situation: <b>Update : </b> Our teams are currently working on a fix to resolve the 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 28 · 12:13 PM OVHcloudWe have new information regarding the incident that affected your service(s). Please find below an update on the situation: <b>Update : </b> The majority of customers are no longer impacted by the incident. <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 28 · 3:15 PM OVHcloudWe are pleased to inform you that the incident affecting our Load Balancer offering has been resolved. <b>Start time :</b> 27/07/2026 07:41 UTC <b>End time :</b> 28/07/2026 14:45 UTC <b>Root Cause :</b> This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
Pattern
[WAW1][Compute - Instance] - Some instances incident notification
Jul 28, 2026 · 8m
View incident →[UK1][Compute - Instance] - Some instances incident notification
Jul 27, 2026 · 2h 5m
View incident →[EU-WEST-PAR][Storage] - Object storage S3 Standard Incident Notification
Jul 23, 2026 · 17h 43m
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. Pulsetic® is a registered trademark.