Live  /  OVHcloud  /  Incident

OVHcloud: [LIM][Network & Infrastructure] - Public and vRack network incident notification

OVHcloud · ovhcloud.comMajor incidentResolved2026-10-15 23:37 UTC
Public — what happened

Summary

OVHcloud reported a problem with its backbone network that caused some packet loss and slower connections for certain customers with services in its LIM datacenter, affecting both the public network and vRack private network, particularly traffic over the FRA-LIM and AMS links. The company said the trouble began at 22:10 UTC on 15 October 2026, and its status entry was opened at 22:48 UTC while teams investigated. OVHcloud said service was fully restored at 22:54 UTC, kept monitoring, and marked the incident resolved at 23:37 UTC, stating the cause was a network equipment issue.

Affected

Infrastructure || Backbone

As listed on OVHcloud’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

What SquidGrid measured

SquidGrid measured 215 internet paths into OVHcloud’s network during this incident. None of them ran meaningfully slower than the same paths the day before.

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 see
Customers 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 43, 2026, our weekly internet health report.

The full archive is on the OVHcloud status & history page.

Related: OVHcloud status & history. SquidGrid is not affiliated with OVHcloud.