Is GitLab CI down right now?

As of the latest health check from 4 global regions, GitLab CI is operational. The status badge at the top of this page reflects the most recent check — Probecast probes GitLab CI every 5 minutes, independently of GitLab CI's own status page.

How often is GitLab CI down?

This month, GitLab CI has had 11 incidents. Across the recent incidents listed on this page, the average duration is 18 minutes.

What is the average uptime of GitLab CI in 2026?

The 30-day uptime for GitLab CI is 99.96%. This is measured by Probecast's independent monitoring from 4 global regions.

How do I get alerted when GitLab CI has an incident?

Create a free Probecast account, add GitLab CI to your monitoring stack and configure alerts via email, Slack or custom webhooks.

Which region has the fastest GitLab CI response times?

Currently, US East has the fastest response times for GitLab CI at 130ms.

What endpoint does Probecast monitor for GitLab CI?

Probecast monitors GET https://gitlab.com/api/v4/user for GitLab CI. Health checks run every 5 minutes from 4 global regions.

GitLab CI

OperationalLast checked: —

CI/CD & Deployment·GitLab CI

Docs

Stack Health Score

Score = 30-day uptime − penalties
Latency >500ms: −2 | >1000ms: −5
Outages this month: −2 each
Degradations this month: −1 each

88.0/100

Uptime · Latency · Incidents

Get an email when GitLab CI's status changes.

Free — a minute to set up, checked from 4 regions around the clock.

Watch GitLab CI →

For the projects you ship

How many of your clients depend on GitLab CI?

When GitLab CI slows down, every project that depends on it feels it at once — and the first call goes to whoever shipped it. Probecast watches the sites you ship and the providers underneath them, shows which clients an outage touches and turns each month into a report your client can trust.

One provider breaks. See every client it touches.

Ordered by how many clients it hits, so you message the right people first.

Each client's site and store, checked from four regions.

US West & East, Europe and Asia — a regional outage never hides.

A monthly report under your brand, reviewed by your team before it goes out.

Uptime, incidents, traffic, revenue and support — signed off by a person.

Your team scoped per client. Every change on the record.

Freelancers see only their clients; every change lands in an append-only audit log.

Start free Book 15 minutes →

Alerts land on email, Slack, push or webhooks — with the client's name on them.

99.96%

UptimePercentage of time the API was available.
Only DOWN status impacts this metric.

182ms

Avg Latency

1,000+

APIs monitored

Outages

Degradations

This Month

About GitLab CI's GitLab CI

GitLab CI's GitLab CI provides integrated CI/CD pipelines within GitLab's DevSecOps platform. GitLab CI launched in 2012 as part of GitLab's all-in-one DevOps platform.. The GitLab CI is used by developers worldwide for pipeline management, build automation, test execution, deployment jobs, DevSecOps.

Probecast monitors the GitLab CI from 4 global regions (US West, US East, Europe, Asia Pacific) every 5 minutes, tracking uptime, latency and regional availability. Our real-time monitoring helps developers and teams understand the current health of GitLab CI's GitLab CI and get alerted the moment service degrades.

Why monitor GitLab CI?

If your product depends on GitLab CI for critical features, an outage on GitLab CI's side is an outage on your product. Probecast detects GitLab CI incidents as they start, giving you time to communicate with customers, fall back to alternative services or pause background jobs gracefully.

Current status

As of the latest check, GitLab CI is operational. The 30-day uptime is 99.96%, with 11 incidents recorded this month. Average response latency across all regions is 182ms.