Live / Providers / OVHcloud
OVHcloud
ovhcloud.comNo open incidents
Cloud & hosting · SquidGrid tracks OVHcloud’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.
Public — what OVHcloud is reporting
Current & recent incidents
Resolved[CHI/BHS][Backbone] - Backbone incident notification
None impact · 2026-11-11 07:54 UTC · source
Resolved[US/SYD][Infrastructure] - Backbone incident notification
None impact · 2026-11-04 14:34 UTC · source
Track record
SquidGrid has archived 66 incidents from OVHcloud’s own status page since 2026-01-03: 16 in the last 90 days, against 17 in the 90 days before.
- 3 rated major or critical in the last 90 days
- Median time from first post to resolved: 3.5 h (last 180 days)
- Longest in the last 90 days: 7 days
- Most recent incident: 4 days ago
- Status page last checked 2026-11-16 01:44 UTC
Recent incidents in the archive
With SquidGrid — where the route changes
Independent path health
A status page tells you what OVHcloud has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.
SquidGrid’s own measurement fleet is watching 9,758 internet paths that cross OVHcloud’s network, observed from 27 countries. At last check (01:45 UTC), every measured path within its usual range. Signed-in customers see which paths, the carrier on each side, and the added latency.
🔒 Sign in to see
Which of these paths are off baseline right now
The carrier on each side of the handoff where conditions change
How much slower than normal, by country, and the 24-hour trend
Included with any paid plan.
See the full report →