Is GitLab down?
Vendor reports an incidentWhat GitLab reports
GitLab reports an incident on its status page: Increase of HTTP 50X errors on GitLab.com.
Impact: minor. Since 2026-10-13 07:10 UTC.
Latest update, 2026-10-14 02:33 UTC: Monitoring confirms that GitLab.com services have remained stable. We are continuing to monitor for any recurrence of the issues before marking this incident as resolved.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingchecked 1 minute ago
Our checks of GitLab pass from all 10 regions we check.
As of Oct 14, 2026, 4:00 AM UTC, RealUptime's checks of GitLab passed in all 10 regions that returned a reading.
GitLab publishes no status feed we can read, so the only reading here is our check reading on the left.
GitLab response time, by region
Check your own site while you wait on GitLab
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not GitLab. It cannot diagnose GitLab's own systems.
Email me when GitLab reports an incident on its status page, and again when it reports it resolved.
Get an email when GitLab reports an incident
Email me when GitLab reports an incident on its status page, and again when it reports it resolved. No account, no card.
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 253msstatus code: 200checked: Oct 14, 2026, 4:00 AM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach GitLab normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 470msstatus code: 200checked: Oct 14, 2026, 3:55 AM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach GitLab normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralChecks passinglatency: 460msstatus code: 200checked: Oct 14, 2026, 3:53 AM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach GitLab normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaChecks passinglatency: 363msstatus code: 200checked: Oct 14, 2026, 3:53 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach GitLab normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaChecks passinglatency: 634msstatus code: 200checked: Oct 14, 2026, 3:54 AM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach GitLab normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 335msstatus code: 200checked: Oct 14, 2026, 3:56 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach GitLab normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKChecks passinglatency: 338msstatus code: 200checked: Oct 14, 2026, 3:55 AM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach GitLab normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 465msstatus code: 200checked: Oct 14, 2026, 3:55 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach GitLab normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaChecks passinglatency: 455msstatus code: 200checked: Oct 14, 2026, 3:55 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach GitLab normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaChecks passinglatency: 343msstatus code: 200checked: Oct 14, 2026, 3:55 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach GitLab normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using GitLab, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for GitLab yet, which is not evidence that nothing is wrong.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring GitLab since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for GitLab covering any window you pick, with our check readings and GitLab's own claim at the time, side by side.
Full check history for GitLab: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversPut this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/gitlab)<a href="https://realuptime.io/outages/gitlab"><img src="https://realuptime.io/outages/gitlab/badge.svg?days=30" alt="GitLab uptime by RealUptime's checks"></a>The badge shows the share of our checks that passed over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
To cite this page: RealUptime, "Is GitLab down?", https://realuptime.io/outages/gitlab. The readings change with every check, so give the date you read them.
Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.
What we check
What our check can and cannot see
A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.
Host checked: gitlab.com