Is GitLab down?

Live status of GitLab: we monitor 3 of its services (GitLab API, Git over HTTPS and Container registry) every minute by Hyperping from Virginia, Frankfurt and Singapore, with response times and 90 days of history.

Checking GitLab…

Loading our latest checks.

What we monitor 3 GitLab services, every minute

Uptime24 h avg

GitLab APIgitlab.comThe API behind the web app, the CLI and integrations……
Git over HTTPSgitlab.comgit clone, fetch and pull over HTTPS……
Container registryregistry.gitlab.comPulling and pushing container images……
gitlab.com sign-inNot checked: Cloudflare blocks automated checks.

Uptime, 90 days: …
Services up: …
GitLab API, 24 h avg: …

Response times fill in over the first hours of checks.

Uptime, last 90 days

When GitLab fails

GitLab.com hosts Git repositories, merge requests, CI/CD pipelines and container registries. Incidents often hit CI runners, the registry or Git over SSH while the web interface loads.

gitlab.com sends visitors who are not signed in to its marketing site, so we check GitLab.com itself: its API, Git over HTTPS and the container registry. CI runners and GitLab Pages are not checked here.

If GitLab is not working for you

Find what fails for you among the services we monitor above. If that service is green, the problem is likely on your side: try the next steps.
Open gitlab.com on another network, such as mobile data. If it works there, the problem is your connection, your DNS or your VPN.
Update or restart the app, then sign out and back in.
Look for an incident on one feature on status.gitlab.com.

Is another service down?

Questions about GitLab outages.

Is GitLab down right now?

The status at the top of this page comes from Hyperping checks of GitLab, run every minute and refreshed on the page every 60 seconds. Green means the latest checks succeeded; red means they are failing, confirmed from several regions.

How do you check GitLab?

We monitor 3 GitLab services every minute, in turn from Virginia, Frankfurt and Singapore: GitLab API (gitlab.com, up on a successful response), Git over HTTPS (gitlab.com, up on a successful response) and Container registry (registry.gitlab.com, up on a 401 response). When a check fails, other regions check again before that service counts as down. GitLab counts as down when all of them are, and as partly down when only some are. gitlab.com sends visitors who are not signed in to its marketing site, so we check GitLab.com itself: its API, Git over HTTPS and the container registry. CI runners and GitLab Pages are not checked here.

GitLab is up here but not working for me. Why?

An outage can be partial: one feature, one app, one country or one internet provider, and our checks see GitLab from data centers. Try another network such as mobile data, update or restart the app, and check the official status page for an incident on one feature.

Does GitLab have an official status page?

Yes, status.gitlab.com. GitLab's team updates it by hand, so it can lag behind the start of an outage; our checks run every minute whatever it says.

Can I get alerted when GitLab goes down?

Yes. Create a free Hyperping account and add gitlab.com as a monitor: you are alerted by email, Slack or your other channels within a minute of a failure. The free plan includes 20 monitors, enough for your own site and the services it depends on.

Know before your users do.

How uptime checks work