Where does this status come from?

From GitLab's own status API at https://status.gitlab.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are GitLab's words.

How can my agent or app check GitLab status?

Fetch https://upbutler.com/status/gitlab/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"gitlab"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or GitLab's?

Add "gitlab" to the dependencies of your UpButler workspace. When one of your monitors fails while GitLab has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is GitLab down?

Right now

Yes. GitLab has a partial outage.

Errors and slow performance on merge requests in the specific groups.

Read from status.gitlab.com 30 s ago · every 120s

For agents

fallback

Use a fallback, next attempt in 60s.

GET upbutler.com/status/gitlab/status.agent.json

MCP: upstream_status {"service":"gitlab"}

GitLab.com: Git, CI/CD runners, registry and Pages.

What GitLab reports

Partial outage· 1 open incident

Taken as is from GitLab's own status API. Incident titles and component names below are theirs.

Open status.gitlab.com

UpButler's independent probe

There is no keyless endpoint of GitLab that says anything useful, so UpButler does not probe it. To check your own GitLab account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Open at GitLab

Errors and slow performance on merge requests in the specific groups.investigating · impact major
Since 2026-10-10 04:49 UTC · Website, API, Git Operations, CI/CD
We are investigating reports of errors and slow performance on merge request and pipeline pages for projects in the specific groups. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150

Text written by GitLab, shown unchanged.

GitLab components

4 of 23 not operational

WebsitePartial outage
APIPartial outage
Git OperationsPartial outage
Package RegistryOperational
Container RegistryOperational
GitLab PagesOperational
CI/CDPartial outage
CI/CD - Hosted runners on LinuxOperational
CI/CD - Hosted runners on WindowsOperational
CI/CD - Hosted runners on macOSOperational
CI/CD - Hosted runners for GitLab community contributionsOperational
CI/CD - Self-managed runnersOperational
SAML SSO - GitLab SaaSOperational
Background ProcessingOperational
GitLab Customers PortalOperational
Support ServicesOperational
packages.gitlab.comOperational
version.gitlab.comOperational
forum.gitlab.comOperational
docs.gitlab.comOperational
CanaryOperational
GitLab DuoOperational
GitLab agent server for KubernetesOperational

GitLab incidents, last 90 days

No finished incidents on record yet since 2026-10-10. UpButler keeps what GitLab publishes for 90 days from the day it starts tracking a service.

Tell your outage from GitLab's

Declare that your project depends on GitLab. When one of your monitors fails while GitLab has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - gitlab

Ask before you retry

curl -s https://upbutler.com/status/gitlab/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "gitlab",
  "verdict": "fallback",
  "status": "partial_outage",
  "reason": "Errors and slow performance on merge requests in the specific groups.",
  "retryAfterSec": 60,
  "incident": {
    "title": "Errors and slow performance on merge requests in the specific groups.",
    "url": "https://status.gitlab.com"
  },
  "probe": null
}

Questions

Is GitLab down right now?: Yes. As of 2026-10-10 05:10 UTC, GitLab has a partial outage, with an open incident: "Errors and slow performance on merge requests in the specific groups.". This page reads the status again every 2 minutes.
Where does this status come from?: From GitLab's own status API at https://status.gitlab.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are GitLab's words.
How can my agent or app check GitLab status?: Fetch https://upbutler.com/status/gitlab/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"gitlab"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or GitLab's?: Add "gitlab" to the dependencies of your UpButler workspace. When one of your monitors fails while GitLab has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in code, packages and workflows

UpButler is not affiliated with GitLab. Status and incident text belong to GitLab and are read from their public status source; the probe result is UpButler's own measurement.