Is GitLab Down?

Developer ToolsLive status, outages, and incident history

Degraded. GitLab is up but having problems.

GitLab is reporting degraded performance as of October 13, 2026. Expect slower responses or more errors. The affected components are listed below.

DegradedChecked just nowLive · 60s while moving

Don't find out like this next time

You searched to find out GitLab was down. Next time we tell you, usually before your customers do, and always before you think to check.

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

2 of 25 GitLab components are impaired. Worst problems listed first.

2degraded23operational

CI/CD - Hosted runners on Linux [Google Compute Engine]

Degraded

CI/CD [Google Compute Engine]

Degraded

API [Google Compute Engine]

Operational

22 more components tracked

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

Also tracking Background Processing [Google Compute Engine], Canary [Google Compute Engine], CI/CD, CI/CD - Hosted runners for GitLab community contributions [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], 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.

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

We are investigating increased queue times for CI/CD jobs using GitLab.com small Linux x86-64 hosted runners. Affected jobs may remain pending longer than usual before starting. We have identified errors and delays when provisioning runner capacity and are working to restore normal job start times. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23176 --- [2026-10-13T15:46:13.023Z] (300) We have identified an ongoing Google Cloud Compute Engine issue affecting runner-capacity provisioning in us-east1. Some GitLab.com CI/CD jobs using small Linux x86-64 hosted runners may remain pending longer than usual before starting. Our engineering teams are working with Google Cloud to restore normal job start times. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23176

Increase of HTTP 50X errors on GitLab.comResolved Oct 13, 2026 · 9h 11mResolved

We are currently investigating reports of an increase of HTTP 50X errors on GitLab.com --- [2026-10-13T07:30:35.395Z] (100) We are seeing an improvement in errors rates in our monitoring, starting from 07:14 UTC. We are still identifying the root cause. --- [2026-10-13T07:48:47.633Z] (400) General GitLab.com service continues to improve. We're now focused on restoring Duo services. --- [2026-10-13T07:59:09.594Z] (100) We are seeing improvements across all services on GitLab.com. We are resuming our investigation on identifying the root cause.

GitLab Duo Workflow IssuesResolved Oct 12, 2026 · 28h 51mResolved

We’re investigating an issue affecting some GitLab Duo Workflow operations. Duo Code Review results may be incomplete or lower quality than expected. Our engineering teams are working on mitigation and will provide further updates. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23158 --- [2026-10-12T13:37:04.404Z] (300) We've identified the cause of the issue affecting GitLab Duo Workflow operations. Duo Code Review remains available, but reviews may contain less context than expected. Our engineering teams are expediting a fix and will continue monitoring until service is fully restored. For more details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23158 --- [2026-10-13T00:28:49.681Z] (300) Errors affecting Code Review tools have decreased, and the tools appear to be operating normally. We’re monitoring error rates and investigating the improvement. A fix is merged but not yet in production, so recovery is still being validated. --- [2026-10-13T00:29:30.864Z] (100) Errors affecting Code Review tools have decreased, and the tools appear to be operating normally. We’re monitoring error rates and investigating the improvement. A fix is merged but not yet in production, so recovery is still being validated. --- [2026-10-13T02:11:37.769Z] (300) Monitoring shows failures are still occurring in a tool used by Duo Code Review. The service remains available, but reviews may contain less context than expected. A fix is merged and awaiting deployment; we’ll update once recovery is confirmed.

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 1599.82% average · 34 days with incidentsOct 13

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.

Are you seeing GitLab problems too?

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.34%. 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.34%. 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