Is GitLab Down?

Developer ToolsLive status, outages, and incident history

No. GitLab is up right now.

Every monitored GitLab system is operational as of October 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment GitLab breaks

GitLab is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

Official GitLab status page

How we know: the official GitLab status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

GitLab Component Status

The main GitLab systems on this page. All 25 are operational right now.

25operational

API [Google Compute Engine]

Operational

Background Processing [Google Compute Engine]

Operational

Canary [Google Compute Engine]

Operational

22 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking CI/CD, CI/CD - Hosted runners for GitLab community contributions [Google Compute Engine], CI/CD - Hosted runners on Linux [Google Compute Engine], CI/CD - Hosted runners on macOS [AWS], CI/CD - Hosted runners on macOS [Google Compute Engine], CI/CD - Hosted runners on Windows [Google Compute Engine], CI/CD - Self-managed runners [Self-Managed Runner Connectivity], CI/CD [Google Compute Engine], Container Registry [Google Compute Engine], docs.gitlab.com [Google Compute Engine], forum.gitlab.com [Digital Ocean], Git Operations [Google Compute Engine], and 10 more.

See all of them free

Component statuses may change independently during partial outages.

Recent GitLab Outages & Incidents

Incident history from the official GitLab status page, including resolution updates.

Errors and slow performance on merge requests in the specific groups.Resolved Oct 10, 2026 · 20h 28mResolved

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 --- [2026-10-10T06:26:16.678Z] (400) We have applied a mitigation and are seeing sustained recovery in error rates and performance on merge request and pipeline pages for the affected projects. We are continuing to monitor. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150 --- [2026-10-10T06:27:00.480Z] (100) We have applied a mitigation and are seeing sustained recovery in error rates and performance on merge request and pipeline pages for the affected projects. We are continuing to monitor. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150

Delayed job completionResolved Oct 8, 2026 · 2h 34mResolved

We are currently investigating delays in job completion: CI jobs remain running after success, delaying pipeline progression. Details https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133 --- [2026-10-08T16:19:17.159Z] (400) Job completion delays are still being observed and we are actively working to address the issue. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133 --- [2026-10-08T16:35:02.523Z] (400) Our investigation is ongoing and we are actively working to identify the root cause. We will provide further updates as more information becomes available. Details in: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133 --- [2026-10-08T17:11:13.194Z] (400) We are continuing to investigate. In addition to delays, users may experience job timeouts or failures during this time. If affected, please retry the job. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23133 --- [2026-10-08T17:34:01.594Z] (400) We are continuing to investigate the root cause and will provide further updates as they become available. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23131 --- [2026-10-08T17:45:10.991Z] (400) We are beginning to see signs of recovery and are continuing to monitor the situation closely while we investigate the root cause. If you have been affected, please retry any failed or timed out jobs. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23131

Job delays on saas-linux-small-amd64 hosted runnersResolved Oct 7, 2026 · 1h 13mResolved

An incident affecting CI/CD jobs on GitLab.com instance runners has been resolved. Job pickup delays should no longer be occurring and we are continuing to monitor to confirm full recovery. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23117

GitLab Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a GitLab incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed

Jul 1399.84% average · 33 days with incidentsOct 11

Going further back: GitLab uptime by month and every recorded GitLab outage.

Live GitLab Outage Reports

Problems reported by engineers using GitLab. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total

24h agoNothing reportednow

No GitLab problems reported yet.

Something wrong with GitLab on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About GitLab

GitLab is an end-to-end DevSecOps platform providing source code management, CI/CD, security scanning, and container registry in a single application used by 30M+ registered users. GitLab outages interrupt software delivery pipelines. Track GitLab status and outages here.

Over the past 30 days, PulsAPI has measured GitLab uptime at 99.35%. Response times, incident history, and SLA tracking for GitLab are available on the PulsAPI dashboard.

GitLab Status FAQ

Is GitLab down right now?

The verdict at the top of this page comes from the latest poll of the official GitLab status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if GitLab is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until GitLab recovers.

How do I check GitLab uptime history?

PulsAPI tracks GitLab uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.35%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever GitLab changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect GitLab outages?

PulsAPI reads the official GitLab status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual GitLab components?

Yes. PulsAPI monitors 25 individual GitLab components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when GitLab goes down?

Yes. Create a free account and subscribe to GitLab: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with GitLab to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot GitLab problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor GitLab?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so GitLab plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track GitLab with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services