Is GitLab down?
Loading the latest status…
Is GitLab down right now? Live status from GitLab’s status page, our own checks and user reports, updated every minute.
- Official status
- Reachable
- Reports in the last hour
Detailed data for this service is briefly unavailable. The status above comes from our latest check.
GitLab’s status page
- Website
- API
- Git Operations
- Package Registry
- Container Registry
- GitLab Pages
- CI/CD
- CI/CD - Hosted runners on Linux
Show all 23 components
- CI/CD - Hosted runners on Windows
- CI/CD - Hosted runners on macOS
- CI/CD - Hosted runners for GitLab community contributions
- CI/CD - Self-managed runners
- SAML SSO - GitLab SaaS
- Background Processing
- GitLab Customers Portal
- Support Services
- packages.gitlab.com
- version.gitlab.com
- forum.gitlab.com
- docs.gitlab.com
- Canary
- GitLab Duo
- GitLab agent server for Kubernetes
Not working for me
Pick what’s broken. Your report shows up on the chart below within a few minutes.
Last 24 hours
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (gitlab.com)
By region
| Region | GitLab API gitlab.com |
|---|---|
| N. Virginia | |
| Oregon | |
| Frankfurt | |
| Singapore | |
| Tokyo | |
| São Paulo |
Each row shows the latest result from that region. How we check
Last 90 days
We have checked GitLab ourselves since Oct 28, 2026. Earlier days come from its status page.
6 days with problems in the last 90 days.
Recent incidents
Incidents: 7 in the last 30 days and 7 in the last 90, lasting a median of 1 min. 5 problems our checks found never appeared on GitLab’s status page.
- GitLab unreachable from several regionsPartial outage1 minFound by our checks, not on the status page
- GitLab unreachable from several regionsPartial outage1 minFound by our checks, not on the status page
- GitLab unreachable from several regionsPartial outage1 minFound by our checks, not on the status page
- GitLab unreachable from several regionsPartial outage1 minFound by our checks, not on the status page
- GitLab unreachable from several regionsPartial outage1 minFound by our checks, not on the status page
- Issues Running PipelinesDegraded1 h 31 min
- Elevated CI/CD latency on GitLab.comDegraded4 h 46 min
If GitLab isn’t working for you
GitLab is a DevOps platform for Git repositories, merge requests, CI/CD pipelines and security scanning, offered as GitLab.com or self-managed.
Common GitLab errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
502 Whoops, GitLab is taking too much time to respond. | GitLab's web tier did not get a response from the application in time, during an incident, a restart or heavy load. | An outage | Wait a few minutes and reload; on GitLab.com check status.gitlab.com. Source |
HTTP Basic: Access denied | Git over HTTPS authentication failed, often because two-factor authentication requires a personal access token instead of your password. | Your side | Use a personal access token as the password, or switch to SSH. Source |
The remote end hung up unexpectedly | The connection dropped during a push or clone, often with large repositories over HTTPS. | Your side | Increase Git's POST buffer or use SSH for large pushes. Source |
RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2) | An HTTP/2 transfer was interrupted while using Git over HTTP. | Your side | Increase the POST buffer size or use SSH; retry if the network is unstable. Source |
Is it just you?
- Check status.gitlab.com if you use GitLab.com; self-managed instances are run by your own team.
- Compare the web UI with git over SSH and HTTPS to narrow down where it fails.
- If CI jobs sit in pending, check whether any runners are online for your project before assuming an outage.
- Retry large pushes over SSH; HTTP buffer limits cause many push failures.
Alternatives to GitLab
Questions
GitLab.com incidents appear on status.gitlab.com. If your company runs its own GitLab, outages there are handled by your administrators, not GitLab Inc.
GitLab's front end did not get a response from the application in time. On self-managed instances it is normal briefly after a restart; on GitLab.com it usually means an incident or heavy load.
Sources: docs.gitlab.com, forum.gitlab.com, status.gitlab.com
Get alerted when GitLab breaks your app.
If your product depends on GitLab, your users feel its outages too. Point a Site Qwality monitor at the GitLab endpoint you use and at your own site, and we alert you on Slack, email, SMS or a webhook as soon as either one stops answering.