Skip to main content
OUTAGE RESOLVED · UTC

GitLab outage, 24 September 2026

GitLab was down for 20 minutes on 24 September 2026, from 22:58 to 23:19 UTC, as measured by HostTracker's checkpoints.

STARTED
22:58
24 Sep 2026 UTC
ENDED
23:19
24 Sep 2026 UTC
DURATION
20.4m
20 minutes
CHECKPOINTS
1
reported a failure
MOST COMMON ERROR
Http 503
as reported by our checks

What our checkpoints saw

ALL TIMES UTC

The first failed check is the top row, and the recovery is the last one. A row marked "x N" stands for several consecutive checks with the same result from that checkpoint.

Individual checks recorded during the GitLab outage on 24 September 2026, all times UTC
Time (UTC) Location Result Error
24 Sep 23:09 Lagos, Nigeria Failed x 2 Http 503
Response time around the outage
152ms low · 368ms peak
24 Sep 21:08 to 24 Sep 23:08 UTC
368 ms 152 ms 24 Sep 21:08 UTC 24 Sep 23:08 UTC

The shaded band is the outage window. Points are averaged per bucket across the checkpoints that answered, so a gap in the line is a period where nothing answered at all.

Previous outage

No earlier outage on record.

Next outage

This is the most recent outage we recorded.

Your own monitoring

Does your product depend on GitLab?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Independent measurement by HostTracker. Not affiliated with GitLab.