All services

Is GitLab down?

GitLab is up.

OperationalChecked 6 minutes ago from N. Virginia · responded in 624 ms

Our last check reached gitlab.com and got a healthy response.

Last 30 days

The numbers

Availability and response time for GitLab over the last 24 hours.

Availability

100%

56 checks, none failed

Avg response

291 ms

Mean of every check

Slowest

648 ms

Worst single check

Incidents

0

Runs of failing checks

Downtime

None

Estimated from samples

Downtime is estimated from 10-minute samples, so figures are accurate to within one check interval.

Over time

Every check we ran, and how long each one took.

Availability

05:00Each bar is 10 minutesnow
  • All checks passed
  • Some checks failed
  • All checks failed

Response time

Where the time goes

"Is it down?" is usually really "it feels broken — what's wrong with it?" This is the answer: every millisecond of a request to gitlab.com, broken into the four phases it actually spends time in.

DNS

Resolving the hostname to an IP address.

12 ms4%
TCP + TLS

Opening the connection and completing the TLS handshake.

8 ms3%
Time to first byte

Waiting for the server to start responding. Usually the server thinking.

271 ms93%
Download

Transferring the response body.

0 ms0%

Averaged over the last 24 hours. The four phases add up to the total response time of 291 ms.

Incidents

Every time a check against gitlab.com failed in the last 30 days, grouped into incidents.

No incidents recorded for GitLab.

Every check we’ve run against GitLab has passed.

This page is a Checkly monitor.

Not a mockup of one. Everything above is produced by the monitor below, running every 10 minutes from N. Virginia and Frankfurt. It lives in a repo, gets code-reviewed, and deploys from CI — the same way you would monitor your own service.

That’s the whole product. Monitoring you can read, diff, and version.

availability-gitlab.check.ts
1import {
2 UrlMonitor,
3 UrlAssertionBuilder,
4 Frequency,
5} from 'checkly/constructs'
6 
7new UrlMonitor('availability-gitlab', {
8 name: 'GitLab (gitlab.com)',
9 activated: true,
10 frequency: Frequency.EVERY_10M,
11 locations: ['us-east-1', 'eu-central-1'],
12 degradedResponseTime: 3000,
13 maxResponseTime: 10000,
14 request: {
15 url: 'https://gitlab.com/api/v4/projects?per_page=1',
16 followRedirects: true,
17 skipSSL: false,
18 assertions: [
19 UrlAssertionBuilder.statusCode().lessThan(400),
20 ],
21 },
22})
Monitor your own serviceHow uptime monitoring works

How we check GitLab

A real request to the endpoint that matters, every 10 minutes — measured, not crowd-sourced.

What we actually do

  • We send a real HTTP GET to https://gitlab.com/api/v4/projects?per_page=1 every 10 minutes.
  • We run it from two datacenters: N. Virginia and Frankfurt.
  • It passes if the endpoint answers with a status below 400 within 10 seconds. Slower than 3 seconds is “degraded”, not down.
  • We probe the GitLab REST API rather than gitlab.com. The API is what your CI runners and git tooling actually depend on, and it can degrade while the website still loads.

What a green check means

  • GitLab answered a real request from both N. Virginia and Frankfurt — an actual measurement, not complaints counted from a crowd.
  • We probe the endpoint that fails when GitLab fails, so a green check tracks the part you depend on, not a marketing page that stays up regardless.
  • Checks run around the clock, every 10 minutes, on the same infrastructure Checkly customers monitor production with.

Frequently asked

No. Our most recent check reached https://gitlab.com/api/v4/projects?per_page=1 and got a healthy response. We check every 10 minutes from N. Virginia and Frankfurt.

We run a real HTTP request against https://gitlab.com/api/v4/projects?per_page=1 every 10 minutes from N. Virginia and Frankfurt, using Checkly's synthetic monitoring. A check passes when the endpoint returns a status below 400 within 10 seconds. We are not counting user reports — we are measuring the actual response.

We probe the GitLab REST API rather than gitlab.com. The API is what your CI runners and git tooling actually depend on, and it can degrade while the website still loads.

We check GitLab from N. Virginia and Frankfurt. If it answers us but not you, the problem is usually specific to your network, ISP, region, or account rather than GitLab itself.

Downdetector counts user reports — how many people are complaining. We run an actual synthetic check against the service and report what the wire says. Reports lag the outage and can be noisy; a probe either gets a response or it doesn't.

See every service we monitor