Region-by-region timeline
When each monitored region started failing and when it recovered, per RealUptime's own probes. A region not listed here never failed during this incident.
US-East9h 31m
Failing from Sep 8, 2026, 7:40 AM UTC, recovered Sep 8, 2026, 5:11 PM UTC
US-West9h 59m
Failing from Sep 8, 2026, 7:13 AM UTC, recovered Sep 8, 2026, 5:12 PM UTC
Europe9h 30m
Failing from Sep 8, 2026, 7:41 AM UTC, recovered Sep 8, 2026, 5:11 PM UTC
Asia-Pacific9h 33m
Failing from Sep 8, 2026, 7:38 AM UTC, recovered Sep 8, 2026, 5:11 PM UTC
US-Central7h
Failing from Sep 8, 2026, 10:07 AM UTC, recovered Sep 8, 2026, 5:07 PM UTC
Canada8h
Failing from Sep 8, 2026, 9:09 AM UTC, recovered Sep 8, 2026, 5:09 PM UTC
UK10h
Failing from Sep 8, 2026, 7:41 AM UTC, recovered Sep 8, 2026, 5:41 PM UTC
Southeast Asia9h 1m
Failing from Sep 8, 2026, 8:01 AM UTC, recovered Sep 8, 2026, 5:02 PM UTC
Australia1h 45m
Failing from Sep 8, 2026, 9:24 AM UTC, recovered Sep 8, 2026, 11:09 AM UTC
South America5h 53m
Failing from Sep 8, 2026, 7:48 AM UTC, recovered Sep 8, 2026, 1:41 PM UTC
How this was measured
This record comes only from RealUptime's own scheduled probes against OVHcloud's public, unauthenticated endpoints, run from 10 named regions. It is never built from user reports or from OVHcloud's own status page, and it does not change once this incident closes: this page is the permanent record, not a live view.
See OVHcloud's full evidence record or read the methodology.