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-East1h
Failing from Sep 3, 2026, 11:01 AM UTC, recovered Sep 3, 2026, 12:01 PM UTC
Europe1h
Failing from Sep 3, 2026, 11:01 AM UTC, recovered Sep 3, 2026, 12:01 PM UTC
Asia-Pacific31 min
Failing from Sep 3, 2026, 11:22 AM UTC, recovered Sep 3, 2026, 11:53 AM UTC
US-Central30 min
Failing from Sep 3, 2026, 11:03 AM UTC, recovered Sep 3, 2026, 11:33 AM UTC
Canada1h
Failing from Sep 3, 2026, 11:03 AM UTC, recovered Sep 3, 2026, 12:03 PM UTC
UK30 min
Failing from Sep 3, 2026, 11:37 AM UTC, recovered Sep 3, 2026, 12:07 PM UTC
Southeast Asia33 min
Failing from Sep 3, 2026, 11:20 AM UTC, recovered Sep 3, 2026, 11:53 AM UTC
Australia34 min
Failing from Sep 3, 2026, 11:12 AM UTC, recovered Sep 3, 2026, 11:47 AM UTC
South America31 min
Failing from Sep 3, 2026, 11:28 AM UTC, recovered Sep 3, 2026, 11:59 AM 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.