Is GitLab down?

Check if gitlab.com is down for everyone or just you

Response time & status — last 24h
All checks passed 0 checks
Monitoring data will appear after first check cycle

Common questions

Why is GitLab down right now?

GitLab outages are usually caused by server overloads, failed deployments, CDN or DNS problems, DDoS attacks, or regional internet routing issues. isitdown.io checks GitLab from 4 regions (US East, US West, Europe, Asia) simultaneously. If all 4 fail, GitLab is down for everyone. If only some fail, the outage may be regional. If all pass but you still can't connect, the issue is on your local network, VPN, or DNS.

How can I check if GitLab is down for everyone or just me?

Click "Check GitLab now" above. isitdown.io pings gitlab.com from four global regions in parallel and reports which ones succeeded. If all four pass, the issue is local — try flushing your DNS cache, switching networks, disabling your VPN, or using a different browser. If two or more regions fail, the outage is on GitLab's side.

Is GitLab having issues today?

The live response-time graph above shows the last 24 hours of real checks against gitlab.com. Each data point is an actual HTTP request from our monitoring system — not a third-party feed. Green means up, red means down. Spikes indicate slow responses. Bookmark this page to check back during future outages.