GitLab is a DevSecOps platform providing Git repository management, CI/CD pipelines, issue tracking, and security scanning in a single application. Current OutageHQ URL check for GitLab: up and running.
Current URL check for GitLab
GitLab is up and running
https://gitlab.com
Not working for you?
Report an outageLast checked: . Current OutageHQ status: operational. There have been 0 user-submitted reports in the past 24 hours. Automated monitoring results are summarized on this page.
Last 24 hours, shown in UTC
Tap or drag for details Arrow keys supported
Reports are anonymous. This history shows only the selected issue type and submission time from the last 30 days.
Newest anonymous GitLab reports from the last 30 days
0 in the last 24 hours
No detailed outage reports in the last 30 days
If GitLab is not working for you, use the report panel above to add an anonymous signal.
Clear steps, real-time checks, and helpful context when GitLab isn't working.
Check this firstDistinguish GitLab.com from a self-managed instance, then compare Git operations with pipeline runners.
GitLab.com outages typically involve database performance issues or CI runner infrastructure problems. Self-managed GitLab instances are unaffected by GitLab.com incidents since they run on separate infrastructure.
Free embed
Help readers check whether GitLab is down from a blog, help center, internal wiki, or incident runbook.
OutageHQ checks the monitored GitLab URL. A reachable URL does not prove that every feature, account, or region works. Compare these observations with GitLab's own updates when available. How OutageHQ checks services.
We could not load live provider updates. Check the GitLab status page directly; it may cover only some GitLab products or regions.
View GitLab status pageOldest to newest; taller bars mean slower URL responses. Select a bar to inspect it. Exact values and statuses also appear below.
Select a bar to inspect its time, status, and response.
Compare GitLab with nearby cloud and developer tools services users often check during the same incident.
GitLab had 96 response-time checks in the last 24 hours, averaging 286 ms, with 3 incident buckets and 0 reports.