Live  /  OVHcloud  /  Incident

OVHcloud: [WAS/YTO][Infrastructure] - Backbone incident notification

OVHcloud · ovhcloud.comMinor incidentResolved2026-10-29 13:58 UTC
Public — what happened

Summary

OVHcloud said a network link between its Washington and Toronto backbone sites became unreachable, which made services that route between the two locations slower to access. The company gave the start as 21:40 UTC on 28 October and said it had identified the cause, which it attributed to its provider. OVHcloud reported the problem resolved with an end time of 13:51 UTC on 29 October, and posted the resolution notice at 13:58 UTC.

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 271 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 45, 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.