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-East50 min
Failing from Sep 24, 2026, 10:57 PM UTC, recovered Sep 24, 2026, 11:47 PM UTC
US-West30 min
Failing from Sep 24, 2026, 11:00 PM UTC, recovered Sep 24, 2026, 11:30 PM UTC
Europe30 min
Failing from Sep 24, 2026, 11:00 PM UTC, recovered Sep 24, 2026, 11:30 PM UTC
Asia-Pacific41 min
Failing from Sep 24, 2026, 11:02 PM UTC, recovered Sep 24, 2026, 11:43 PM UTC
US-Central1h 20m
Failing from Sep 24, 2026, 10:59 PM UTC, recovered Sep 25, 2026, 12:19 AM UTC
Canada20 min
Failing from Sep 24, 2026, 11:15 PM UTC, recovered Sep 24, 2026, 11:35 PM UTC
UK40 min
Failing from Sep 24, 2026, 10:57 PM UTC, recovered Sep 24, 2026, 11:36 PM UTC
Southeast Asia20 min
Failing from Sep 24, 2026, 11:24 PM UTC, recovered Sep 24, 2026, 11:44 PM UTC
South America1h
Failing from Sep 24, 2026, 11:04 PM UTC, recovered Sep 25, 2026, 12:04 AM UTC
How this was measured
This record comes only from RealUptime's own scheduled probes against GitLab's public, unauthenticated endpoints, run from 10 named regions. It is never built from user reports or from GitLab's own status page, and it does not change once this incident closes: this page is the permanent record, not a live view.