CheckWebsiteNow

Live status check

Is GitLab down right now?

We check gitlab.com from one measurement point when you open this page. This shows what we saw, not a worldwide verdict.

A fresh check of gitlab.com runs in your browser. If no result appears, run the check on the start page.

Our last check

Not checked yet — a fresh check starts when you open this page.

About GitLab problems

GitLab.com problems can affect git push and pull, CI/CD pipelines, merge requests or sign-in. Check the GitLab status page first, then test whether git works over HTTPS and over SSH, because some networks block one of them. Pipelines that wait for a runner can point to runner availability rather than a GitLab outage.

Official information

GitLab official status page (verified )

Our check and GitLab's own status page can disagree. We test from one location and read only the homepage response. The provider reports what it knows about its own systems, such as sign-in, apps or single regions. A site can answer our check while one feature is broken, and a regional problem can affect one location but not another.

GitLab help pages

How this check works

  • One measurement location (single-self-hosted-probe), not a worldwide test.
  • We read only the response headers of the HTTPS homepage; page content and features are not tested.
  • We follow at most 5 HTTPS redirects and check every new address again.
  • The whole check stops after 10 seconds.
  • Results are reused for 60 seconds; this page refreshes its saved check at most every 10 minutes.

Full method and limits

Typical GitLab problems

An editorial list of typical problems, not based on live user reports.

  • Git push or pull is denied If git over HTTPS returns a 403, the access token or password may lack write permission, so check the token scopes and your role in the project. Guide: 403 Forbidden
  • Git over SSH times out When SSH port 22 is blocked on your network, GitLab.com also accepts SSH on port 443 through altssh.gitlab.com. Guide: ERR_CONNECTION_TIMED_OUT
  • Too many requests GitLab.com answers 429 when a signed-in user or a network address sends too many requests, so slow down scripts and retry after the time given in the Retry-After header. Guide: 429 Too Many Requests
  • Web pages show a bad gateway A 502 page on GitLab.com means a gateway did not get a valid answer from the server behind it, so check the status page and retry shortly. Guide: 502 Bad Gateway
  • Pipelines stay pending A GitLab job stuck in pending can be waiting for an available runner, and GitLab drops a job that finds no matching runner after one hour, so check the project's runner settings and tags.

General fixes: Developer tools

  1. Read the full error response API and git errors include a status code and a message. A 401 or 403 points to credentials or permissions, a 429 to rate limits and a 5xx code to the provider.
  2. Check tokens and scopes Expired tokens and missing scopes can cause sudden failures. Create a fresh token with only the scopes you need.
  3. Try HTTPS and SSH If git fails over one protocol, test the other one. Some networks block SSH while HTTPS still works.
  4. Retry with growing pauses For temporary errors, wait and retry with longer pauses each time instead of retrying in a tight loop, which can trigger rate limits.

Check another website

One measurement point. Results explain what we saw, not a worldwide verdict.