Live / OVHcloud / Incident
OVHcloud: [US][Infrastructure] - Backbone incident notification
OVHcloud · ovhcloud.comMinor incidentResolved2026-11-10 10:51 UTC
Public — what happened
Summary
OVHcloud said its backbone network in the US region had higher-than-normal delays, which it later said also involved some lost data traffic, so customers may have had slower or less reliable access to their services there. The company said the problem began at 06:22 UTC on 10 November 2026 and that it identified the cause as a network equipment issue. It reported the situation was reduced from 07:07 UTC, gave 08:30 UTC as the end time, and marked the incident resolved at 10:51 UTC.
Affected
Infrastructure || Backbone
Timeline
- Started — 2026-11-10 08:20 UTC
- Identified — 2026-11-10 08:20 UTC
- Resolved — 2026-11-10 10:51 UTC · 2h 31m after it started
What SquidGrid measured
SquidGrid measured 251 internet paths into OVHcloud’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach OVHcloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for OVHcloud: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the OVHcloud report →
More from OVHcloud
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.