Service status / GitLab

Is GitLab down?

Up No. GitLab is up.

Our checks are passing. Checked .

GitLab.com is the hosted GitLab service for Git repositories, CI/CD pipelines and issue tracking. This page checks it every minute from three regions.

Free plan: 50 monitors · Alerts by email, Slack, Telegram and the app · No card

Our checks

Up

Checked every minute from the US, Europe and Israel. GitLab is shown as failing only when two regions agree.

Updated .

GitLab’s official status

We don’t show GitLab’s status here yet. Its own page has the latest.

Open GitLab’s status page ↗

Uptime from our checks

99.929% 4 days

Recent outages

No outages recorded since we started checking GitLab.

What we check

A GET request to https://gitlab.com/api/v4/version every 60 seconds from US (New York), Europe (Amsterdam) and Israel (Tel Aviv), expecting HTTP 401 and the text “401 Unauthorized” in the answer.

GitLab.com’s REST API. Without a token it answers with a JSON 401, which shows the API is up.

A region counts as failing after 2 failed checks in a row, and we show GitLab as failing only when 2 regions agree.

Monitor it from your own account →

Is it GitLab, or is it me?

  1. The official status page covers GitLab.com only. A self-managed GitLab instance runs on your own servers and needs its own monitoring.
  2. Separate the parts: the website, Git over SSH, Git over HTTPS, the API, CI/CD runners and the container registry can fail independently. If pushes fail over SSH, try HTTPS, or the other way round.
  3. Pipelines stuck in “pending” can mean the shared runners are short of capacity, even while the rest of GitLab.com works. Your own runners are not affected by that.
  4. A 401 or 403 on your own requests usually means an expired or revoked token, not an outage.

Show GitLab on your own status page

If your product depends on GitLab, your users ask you first when it fails. Monitor it from your account and show it as a component on your 12happy status page, next to your own services. One status page is free.

Add it to a status page →

Questions

Is GitLab down right now?

The top of this page answers that from our latest checks, run every 60 seconds from three regions. It refreshes every minute while the page is open.

Where is GitLab’s official status page?

GitLab publishes its status at status.gitlab.com. This page links to it.

How does 12happy check GitLab?

A GET request to https://gitlab.com/api/v4/version every 60 seconds from US (New York), Europe (Amsterdam) and Israel (Tel Aviv), expecting HTTP 401 and the text “401 Unauthorized” in the answer. A region counts as failing after 2 failed checks in a row, and we only show GitLab as failing when 2 regions agree, so a problem on one network path doesn’t become a false alarm.

How can I get alerted when GitLab goes down?

Sign up for 12happy’s free plan and add a monitor for https://gitlab.com/api/v4/version, the same address this page checks. It runs every 5 minutes on the free plan, and every 30 seconds on Pro. You get an alert by email, Slack, Telegram or the 12happy app when it fails, confirmed from a second location. The free plan includes 50 monitors, so you can watch your own site too.

Does GitLab’s status page cover my self-managed GitLab?

No. status.gitlab.com reports on GitLab.com, the hosted service. A self-managed instance depends on your own servers and network, so monitor it directly.

12happy is not affiliated with or endorsed by GitLab. GitLab is a trademark of its owner and is named here only to identify the service. The status shown comes from 12happy’s independent checks.