Is GitLab down right now?
GitLab looks up
- HTTP status code 200
- Response time 279 ms
- SSL certificate valid for 72 more days
Checked from our server in Germany.
Results are cached for up to 5 minutes.
This is an independent reachability check of gitlab.com. A single check can't see partial or API-only outages — always confirm on the official status page below.
What to do if GitLab is down
- 1
Check the official status page for a component-level breakdown: status.gitlab.com
- 2
Rule out your own side — try a different network or device, and clear your DNS cache. If only you can't reach it, it's likely local.
- 3
If your own product depends on GitLab, monitor that dependency directly so you're alerted before your users notice.
GitLab outage FAQ
Is GitLab.com down right now?
We check gitlab.com from our server in Germany, outside GitLab's infrastructure. If it's unreachable here, it's likely a broad outage; if it's reachable but your pipelines are stuck, the CI/CD component may be degraded — see status.gitlab.com.
My self-hosted GitLab is down — does this help?
No. This page only checks GitLab.com (the SaaS). A self-hosted GitLab instance is your own server — you can monitor it directly with UptimeEye.
Get alerted before your users notice
Monitor your own websites, APIs, and the services you depend on — with verified, multi-region alerts. Free on every plan.
Start freeNo credit card required.