Skip to content

Outage tracker / GitLab

Is GitLab down?

I'm having a problem

Vendor reports no incidentWhat GitLab reports

GitLab reports no incident on its status page.

As of the last successful poll, 2026-11-07 17:14 UTC.

GitLab's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 2 minutes ago

Our checks of GitLab pass from all 10 regions we check.

As of Nov 7, 2026, 5:36 PM UTC, RealUptime's checks of GitLab passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 7, 2026, 5:36 PM UTC
US-East1007 msChecks passing
US-West1058 msChecks passing
Europe820 msChecks passing
Asia-Pacific1525 msChecks passing
US-Central610 msChecks passing
Canada1095 msChecks passing
UK912 msChecks passing
Southeast Asia1984 msChecks passing
Australia1204 msChecks passing
South America1240 msChecks passing
their status pagetheir claim, not our reading

GitLab publishes no status feed we can read, so the only reading here is our check reading on the left.

GitLab response time, by region

US-East
1.1sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 590ms2026-10-10 UTC: p95 465ms2026-10-11 UTC: p95 452ms2026-10-12 UTC: p95 471ms2026-10-13 UTC: p95 567ms2026-10-14 UTC: p95 541ms2026-10-15 UTC: p95 468ms2026-10-16 UTC: p95 585ms2026-10-17 UTC: p95 953ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.5s2026-11-06 UTC: p95 1.2s2026-11-07 UTC: p95 1.1s
Oct 9Oct 23Nov 7
US-West
1.9sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 559ms2026-10-10 UTC: p95 616ms2026-10-11 UTC: p95 503ms2026-10-12 UTC: p95 591ms2026-10-13 UTC: p95 731ms2026-10-14 UTC: p95 602ms2026-10-15 UTC: p95 726ms2026-10-16 UTC: p95 680ms2026-10-17 UTC: p95 858ms2026-10-18 UTC: p95 949ms2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 392ms2026-10-25 UTC: p95 418ms2026-10-26 UTC: p95 500ms2026-10-27 UTC: p95 689ms2026-10-28 UTC: p95 921ms2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.8s2026-11-06 UTC: p95 1.4s2026-11-07 UTC: p95 1.9s
Oct 9Oct 23Nov 7
Europe
921msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 659ms2026-10-10 UTC: p95 512ms2026-10-11 UTC: p95 457ms2026-10-12 UTC: p95 470ms2026-10-13 UTC: p95 652ms2026-10-14 UTC: p95 569ms2026-10-15 UTC: p95 712ms2026-10-16 UTC: p95 559ms2026-10-17 UTC: p95 666ms2026-10-18 UTC: p95 912ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 538ms2026-10-22 UTC: p95 1.0s2026-10-23 UTC: p95 979ms2026-10-24 UTC: p95 767ms2026-10-25 UTC: p95 422ms2026-10-26 UTC: p95 478ms2026-10-27 UTC: p95 924ms2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 914ms2026-10-31 UTC: p95 943ms2026-11-01 UTC: p95 925ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.2s2026-11-06 UTC: p95 1.1s2026-11-07 UTC: p95 921ms
Oct 9Oct 23Nov 7
Asia-Pacific
1.9sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 991ms2026-10-11 UTC: p95 939ms2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 683ms2026-10-15 UTC: p95 885ms2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 2.1s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 830ms2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 3.4s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 2.7s2026-11-06 UTC: p95 2.0s2026-11-07 UTC: p95 1.9s
Oct 9Oct 23Nov 7
US-Central
1.1sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 673ms2026-10-10 UTC: p95 511ms2026-10-11 UTC: p95 526ms2026-10-12 UTC: p95 485ms2026-10-13 UTC: p95 553ms2026-10-14 UTC: p95 721ms2026-10-15 UTC: p95 545ms2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 822ms2026-10-22 UTC: p95 878ms2026-10-23 UTC: p95 954ms2026-10-24 UTC: p95 430ms2026-10-25 UTC: p95 426ms2026-10-26 UTC: p95 634ms2026-10-27 UTC: p95 640ms2026-10-28 UTC: p95 752ms2026-10-29 UTC: p95 463ms2026-10-30 UTC: p95 457ms2026-10-31 UTC: p95 478ms2026-11-01 UTC: p95 480ms2026-11-02 UTC: p95 637ms2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 1.0s2026-11-05 UTC: p95 678ms2026-11-06 UTC: p95 1.0s2026-11-07 UTC: p95 1.1s
Oct 9Oct 23Nov 7
Canada
1.6sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 673ms2026-10-10 UTC: p95 596ms2026-10-11 UTC: p95 627ms2026-10-12 UTC: p95 770ms2026-10-13 UTC: p95 733ms2026-10-14 UTC: p95 530ms2026-10-15 UTC: p95 571ms2026-10-16 UTC: p95 551ms2026-10-17 UTC: p95 668ms2026-10-18 UTC: p95 869ms2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 987ms2026-10-23 UTC: p95 899ms2026-10-24 UTC: p95 672ms2026-10-25 UTC: p95 802ms2026-10-26 UTC: p95 970ms2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 658ms2026-10-29 UTC: p95 648ms2026-10-30 UTC: p95 963ms2026-10-31 UTC: p95 945ms2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.7s2026-11-06 UTC: p95 1.5s2026-11-07 UTC: p95 1.6s
Oct 9Oct 23Nov 7
UK
1.0sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 693ms2026-10-10 UTC: p95 452ms2026-10-11 UTC: p95 461ms2026-10-12 UTC: p95 539ms2026-10-13 UTC: p95 494ms2026-10-14 UTC: p95 595ms2026-10-15 UTC: p95 504ms2026-10-16 UTC: p95 434ms2026-10-17 UTC: p95 905ms2026-10-18 UTC: p95 970ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 624ms2026-10-22 UTC: p95 800ms2026-10-23 UTC: p95 910ms2026-10-24 UTC: p95 636ms2026-10-25 UTC: p95 571ms2026-10-26 UTC: p95 536ms2026-10-27 UTC: p95 697ms2026-10-28 UTC: p95 670ms2026-10-29 UTC: p95 937ms2026-10-30 UTC: p95 831ms2026-10-31 UTC: p95 886ms2026-11-01 UTC: p95 764ms2026-11-02 UTC: p95 872ms2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.0s2026-11-05 UTC: p95 1.1s2026-11-06 UTC: p95 1.0s2026-11-07 UTC: p95 1.0s
Oct 9Oct 23Nov 7
Southeast Asia
2.4sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 2.3s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.6s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 2.9s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.3s2026-11-06 UTC: p95 2.4s2026-11-07 UTC: p95 2.4s
Oct 9Oct 23Nov 7
Australia
1.6sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 834ms2026-10-11 UTC: p95 923ms2026-10-12 UTC: p95 846ms2026-10-13 UTC: p95 837ms2026-10-14 UTC: p95 759ms2026-10-15 UTC: p95 942ms2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 1.6s2026-10-24 UTC: p95 947ms2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 2.2s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 2.0s2026-11-06 UTC: p95 1.6s2026-11-07 UTC: p95 1.6s
Oct 9Oct 23Nov 7
South America
1.9sp95 · latest
20s10s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 20s. Days with no samples are not plotted, not shown as zero.2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 887ms2026-10-15 UTC: p95 776ms2026-10-16 UTC: p95 806ms2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 10.3s2026-10-24 UTC: p95 2.6s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 2.3s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 2.9s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.3s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.4s2026-11-06 UTC: p95 1.3s2026-11-07 UTC: p95 1.9s
Oct 9Oct 23Nov 7

Check your own site while you wait on GitLab

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not GitLab. It cannot diagnose GitLab's own systems.

What we measured, function by function

GitLab answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • CI/CDUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Container RegistryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Git operationsUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • WebsiteUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when GitLab reports an incident on its status page, and again when it reports it resolved.

Get an email when GitLab reports an incident

Email me when GitLab reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is GitLab's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1007msstatus code: 200checked: Nov 7, 2026, 5:35 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach GitLab normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1058msstatus code: 200checked: Nov 7, 2026, 5:28 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach GitLab normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 610msstatus code: 200checked: Nov 7, 2026, 5:28 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach GitLab normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1095msstatus code: 200checked: Nov 7, 2026, 5:34 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach GitLab normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1240msstatus code: 200checked: Nov 7, 2026, 5:36 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach GitLab normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 820msstatus code: 200checked: Nov 7, 2026, 5:29 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach GitLab normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 912msstatus code: 200checked: Nov 7, 2026, 5:21 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach GitLab normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1525msstatus code: 200checked: Nov 7, 2026, 5:26 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach GitLab normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1984msstatus code: 200checked: Nov 7, 2026, 5:33 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach GitLab normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1204msstatus code: 200checked: Nov 7, 2026, 5:23 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach GitLab normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using GitLab, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for GitLab yet, which is not evidence that nothing is wrong.

Recent probe events

Issues Running Pipelines, 1h 31mdeclared on their status page2026-11-03
Elevated CI/CD latency on GitLab.com, 4h 45mdeclared on their status page2026-11-03
Upcoming maintenance for the Customers Portal, 17h 52mdeclared on their status page2026-10-30
General slowness on Gitlab.com, 32mdeclared on their status page2026-10-23
404s on customers.gitlab.com, 3h 25mdeclared on their status page2026-10-20
Intermittent 500 on GitLab.com, 2h 47mdeclared on their status page2026-10-20
503s on GitLab.com, 1h 14mdeclared on their status page2026-10-16
GitLab.com CI/CD Incident, 1h 48mdeclared on their status page2026-10-16

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring GitLab since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for GitLab covering any window you pick, with our check readings and GitLab's own claim at the time, side by side.

Full check history for GitLab: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

GitLab uptime by RealUptime's checksLive, from this page's own readings.
[![GitLab uptime by RealUptime's checks](https://realuptime.io/outages/gitlab/badge.svg?days=30)](https://realuptime.io/outages/gitlab)
<a href="https://realuptime.io/outages/gitlab"><img src="https://realuptime.io/outages/gitlab/badge.svg?days=30" alt="GitLab uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is GitLab down?", https://realuptime.io/outages/gitlab. The readings change with every check, so give the date you read them.

What we check

primaryfunctional
https://gitlab.com/api/v4/projects/278964
secondary
https://status.gitlab.com/
secondary
https://gitlab.com/gitlab-org/gitlab-foss.git/info/refs?service=git-upload-pack
secondary
https://registry.gitlab.com/v2/
secondary
https://gitlab.com/api/v4/projects/278964/pipelines
secondary
https://about.gitlab.com/

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: gitlab.com

RealUptime is not affiliated with GitLab; the name identifies what we checked, and nothing here speaks for GitLab's own team. We send a single web request to GitLab from 10 regions on our own schedule and time the response. We do not see inside GitLab's systems, do not use an account or real transaction, and are not the same signal GitLab's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for GitLab is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.