Is GitLab down?
Operationalchecked moments ago
We reached GitLab from all 10 regions we check.
As of Oct 5, 2026, 8:15 PM UTC, GitLab answered RealUptime's probes in all 10 regions that returned a reading.
Last outage: 1h 23m on Sep 24, 2026 (web surface, from Europe, South America, US-East, UK, Asia-Pacific, US-Central, Southeast Asia, US-West and Canada).
GitLab publishes no status feed we can read, so the only independent reading here is ours on the left.
GitLab response time, by region
Is it GitLab, or is it you?
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.
Get an email when we see GitLab go down, and when it is back
Get told when we measure this
We will tell you when our probes stop reaching GitLab, and again when they can reach it again. That is our own measurement from ten regions, not GitLab's status page. No account, no card.
What we measured, and what people reported
- North AmericaOperationalUS-East, US-West, US-Central, Canada
- US-EastOperationallatency: 299msstatus code: 200checked: Oct 5, 2026, 8:15 PM 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-WestOperationallatency: 423msstatus code: 200checked: Oct 5, 2026, 8:13 PM 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-CentralOperationallatency: 318msstatus code: 200checked: Oct 5, 2026, 8:07 PM 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.
- CanadaOperationallatency: 596msstatus code: 200checked: Oct 5, 2026, 8:07 PM 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 AmericaOperationallatency: 923msstatus code: 200checked: Oct 5, 2026, 8:12 PM 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.
- EuropeOperationalEurope, UK
- EuropeOperationallatency: 463msstatus code: 200checked: Oct 5, 2026, 8:06 PM 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.
- UKOperationallatency: 365msstatus code: 200checked: Oct 5, 2026, 8:02 PM 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 PacificOperationalAsia-Pacific, Southeast Asia, Australia
- Asia-PacificOperationallatency: 677msstatus code: 200checked: Oct 5, 2026, 8:10 PM 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 AsiaOperationallatency: 1006msstatus code: 200checked: Oct 5, 2026, 8:02 PM 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.
- AustraliaOperationallatency: 806msstatus code: 200checked: Oct 5, 2026, 8:00 PM 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 outages
measured 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 measurements and GitLab's own claim at the time, side by side.
Full availability history for GitLab: 90-day availability by region, month-by-month uptime, and every incident 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 measured by RealUptime"></a>The badge shows the share of our probes that succeeded 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
What GitLab's SLA implies, from our measurement
Below your target
We measured 1h 22m of downtime for GitLab over the last 30 days, which is 99.8090% uptime by our reading. A 99.9% target allows 43 minutes over that period.
That is 39 minutes more than the target allows. The figure above is the pro-rata share of one month's fee for the time we could not reach it. Your contract probably uses a tiered credit schedule instead, and we have not read it, so treat this as one common way to reason about a credit rather than the amount they owe.
This is computed from our own probe measurements, not from GitLab's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.