Protego field desk
PROTEGO

LIVE STATUS CHECKER

Is GitLab down right now?

Pipelines stuck, pushes failing or the web UI timing out? We check gitlab.com, sign-in, the API and the Container Registry every minute, read GitLab’s official status for every component, and count reports from other developers.

Website + GitAPIContainer RegistryOfficial status incl. runnersFree, no sign-in
LIVE STATUS: UP

GitLab is up

  • Every check passed and user reports are at normal levels

Checked

Next refresh in 60s

STEP 1: FREE TROUBLESHOOTER

Why isn't GitLab working for you?

Six checks on your own device in about ten seconds: your connection, whether your network blocks GitLab, your DNS, your device clock, cookies and your network. You get the exact fix for what we find.

STEP 2

Report a problem

What is not working for you? One tap, no sign-in. Your report helps everyone else see what is happening.

One report per person, checked for duplicates and abuse. We store the problem type, your country and anonymous codes that change daily. Never your IP address, name or account.

User reports in the last 24 hours

0 reports, 0 in the last 15 minutes from 0 networks

24 hours ago12 hours agoNow

No one has reported a GitLab problem here in the last 24 hours. Having trouble? Be the first to report it above.

What we checked, right now

Live requests from our servers to gitlab.com, sign-in, the API and the Container Registry, refreshed every minute.

GitLab.com endpoints

  • gitlab.com

    Website and Git over HTTPS

    OK: 303 ms

  • Sign-in

    gitlab.com/users/sign_in

    OK: 40 ms

  • API

    gitlab.com/api/v4

    OK: 222 ms

  • Container Registry

    registry.gitlab.com

    OK: 73 ms

  • about.gitlab.com

    Marketing site and docs

    OK: 135 ms

DNS: can the internet find GitLab?

  • Cloudflare DNS (1.1.1.1)

    Can the internet find gitlab.com?

    OK: 12 ms

  • Google DNS (8.8.8.8)

    A second, independent resolver

    OK: 12 ms

  • GitLab's own nameservers

    Answer for gitlab.com even if public DNS fails

    OK: 23 ms

GitLab official status

No known issues on status.gitlab.com for the website, API, Git operations, registries, Pages or CI/CD runners.

Source: status.gitlab.com. This covers GitLab.com only. A self-managed GitLab instance is run by your own organization.

gitlab.com response time, last 24 hours

24 hours agoPeak 1000 msNow
№ 01

Is GitLab down, or is it just you?

  1. 1

    Read the live status above.

    status.gitlab.com lists the website, API, Git operations, registries, Pages and hosted CI/CD runners separately.

  2. 2

    GitLab.com or self-managed?

    If your company runs its own GitLab (a custom domain), this page does not apply: ask your platform team.

  3. 3

    Test Git directly.

    Run git ls-remote https://gitlab.com/gitlab-org/gitlab.git. If it answers, GitLab.com is reachable from your machine.

  4. 4

    Check your credentials.

    Expired personal or project access tokens and SSH keys that are not loaded fail exactly like an outage.

  5. 5

    Check runners, not GitLab.

    Pipelines stuck as "pending" often mean no matching runner is online, especially with self-hosted runners.

№ 02

GitLab error messages and what they mean

ErrorWhat it meansWhat to do
502: Whoops, GitLab is taking too much time to respondGitLab’s web tier timed outRetry; if it repeats, check the official status
503 Service UnavailableGitLab.com is overloaded or in maintenanceWait; check status.gitlab.com for maintenance windows
HTTP Basic: Access deniedWrong password or token over HTTPSNot an outage: use a valid personal access token
Job is stuck / pendingNo online runner matches the job’s tagsCheck runner tags and status; hosted runners appear on the official status
429 Too Many RequestsYou hit GitLab.com rate limitsNot an outage: slow down API calls or authenticate
№ 03

Keeping CI/CD moving during a GitLab outage

  • Commit locally. Git keeps working on your machine; push when GitLab.com recovers.

  • Retry, do not recreate. Retry failed jobs once runners are healthy instead of creating new pipelines that pile up in queues.

  • Self-hosted runners help. They keep running jobs for repositories they can reach, but still need GitLab.com to pick up work.

  • Cache images and dependencies. Pipelines that pull from registry.gitlab.com on every run fail during registry incidents. Cache or mirror critical images.

№ 04

Why does GitLab go down?

Database incidents
The 2017 outage started when an engineer, fighting heavy load and replication lag, removed data from the primary database.
Load and abuse
Spam and abuse traffic have caused load spikes on GitLab.com, which runs many free accounts.
Cloud and CDN dependencies
GitLab.com runs on Google Cloud with a CDN in front, so provider incidents can reach it.
Maintenance
Planned database and infrastructure maintenance is announced on the status page in advance.
№ 05

GitLab outage history

The biggest GitLab incidents and what caused them. Durations are approximate and come from public reporting and official reviews.

  • JAN 31, 2017

    GitLab.com down for many hours; about six hours of database changes lost

    Accidental removal of data from the primary database while handling load from spam, with backups that turned out not to work. Source: GitLab postmortem

№ 06

How this page works

Every minute our servers request GitLab's main endpoints, resolve gitlab.com through Cloudflare, Google and gitLab's own nameservers, and read status.gitlab.com. We combine that with one-tap user reports, filtered for duplicates and abuse: a spike needs at least 12 reports in 15 minutes from 8 or more different networks.

Built to avoid false alarms: a failed request is retried before it counts, a single bad check never says "down" on its own, and a check that fails for reasons on our side is shown as inconclusive rather than as an outage. Limits: we check from one location, so a regional problem may first show up in user reports. Reports store only the problem type, a country code and anonymous codes that change daily; never your IP address. Protego is independent and not affiliated with GitLab. Last reviewed .

№ 07

Frequently asked questions

Is GitLab down right now?

The status box at the top of this page answers that live. We check gitlab.com, sign-in, the API and the Container Registry every minute, read status.gitlab.com and count user reports.

GitLab pipelines are stuck in pending. Is it down?

Check hosted runners on the official status. If they are fine, a job usually waits because no online runner matches its tags.

Does this page check my company’s GitLab?

No. It checks GitLab.com. A self-managed GitLab on your own domain is run by your organization: use our website down checker for its address.

What does "GitLab is taking too much time to respond" mean?

It is GitLab’s 502 timeout page. Reload once; if it repeats across pages, GitLab.com is having problems.

Where does GitLab post outages?

On status.gitlab.com, with separate components for the website, API, Git, registries, Pages and CI/CD runners. We show it live on this page.

What happened in the 2017 GitLab outage?

An engineer accidentally removed data from the primary database. GitLab restored from a six-hour-old copy and published a detailed, very open postmortem.

FOR DEVOPS ENGINEERS

Design pipelines that degrade gracefully

Our free AZ-400 course covers CI/CD design, caching and secure release pipelines.

Start the free AZ-400 course

IS IT DOWN?

Check other services

Is Facebook down?

Website, app, login, Messenger and DNS

Is AWS down?

Amazon Web Services regions and services

Is Microsoft 365 down?

Outlook, Teams and sign-in

Is Azure down?

Azure portal and cloud services

Is Amazon down?

Amazon.com shopping and checkout

Is LinkedIn down?

Website, app, messaging and feed

Is Reddit down?

Website, app and comments

Is GitHub down?

Git, Actions, API and Copilot

Check any website

DNS, connection, SSL and firewall checks for any address

Related free tools