Is GitLab Down?

Developer ToolsLive status, outages, and incident history

No. GitLab is up right now.

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

OperationalChecked just nowLive, rechecked every 60s

Start monitoring GitLab Official GitLab status page

How we know: the official GitLab status page, PulsAPI's own check every 60 seconds, 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.

Create a free account

Component statuses may change independently during partial outages.

Recent GitLab Outages & Incidents

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

403 errors across GitLab.comResolved Aug 21, 2026 · 26 minResolved

We're monitoring an incident where 403s were seen across GitLab.com. The fix for this is already in place. More about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22762

500 errors when fetching commits on GitLab.comResolved Aug 18, 2026 · 3h 11mResolved

We are investigating an issue causing a subset of requests to GitLab.com receiving 500 errors. We will provide updates as we learn more from our investigation. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729 --- [2026-08-18T14:16:27.627Z] (500) We are still investigating the root cause for 500 errors while fetching commits on GitLab.com. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729 --- [2026-08-18T14:31:22.637Z] (500) Investigation for the root cause of 500 errors while fetching commits on GitLab.com is still ongoing. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729 --- [2026-08-18T14:49:41.988Z] (500) Our monitoring shows the error rate decreasing towards normal thresholds. We're continuing to monitor the incident. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729 --- [2026-08-18T16:11:39.118Z] (500) The error rate has continued to remain within normal thresholds. We're continuing to monitor the error rate. Further developments can be read here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

Project and Group Deletions DelayedResolved Aug 17, 2026 · 6h 25mResolved

We are currently investigating an issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been scheduled for deletion may remain visible past their expected deletion date. --- [2026-08-17T08:18:28.838Z] (400) We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 --- [2026-08-17T08:56:09.034Z] (400) We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 --- [2026-08-17T09:16:19.094Z] (400) We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 --- [2026-08-17T09:37:47.108Z] (400) We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 --- [2026-08-17T09:58:52.265Z] (400) We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 --- [2026-08-17T10:22:31.087Z] (400) We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 --- [2026-08-17T10:44:00.000Z] (400) We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 --- [2026-08-17T11:02:00.000Z] (400) We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 --- [2026-08-17T11:20:00.000Z] (400) We've identified a fix for the issue affecting project and group deletions on GitLab.com. Due to routine DB maintenance there will be a delay for when the fix will land in production. Given the current state of a known fix and the known delay, we will post status updates every hour for this incident. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 --- [2026-08-17T12:37:04.750Z] (400) The fix is now in production and we're now working on processing the deletion queue via the deletion workers. The last 4 status updates were missing a "4" infrastructure work item link shared; this has been corrected on the status page. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 --- [2026-08-17T13:24:47.871Z] (400) We're continuing to monitor the deletion queue being processed via the deletion workers. Delay of deletions and visibility of scheduled/queued deletions would be experienced until the queue is cleared. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

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

May 2693.99% average · 22 days with incidentsAug 24

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.73%. Response times, incident history, and SLA tracking for GitLab are available on the PulsAPI dashboard.

GitLab Status FAQ

Is GitLab down right now?

PulsAPI checks GitLab every 60 seconds. 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.

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.73%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for GitLab.

How fast does PulsAPI detect GitLab outages?

PulsAPI polls the official GitLab status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

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 PulsAPI account and subscribe to GitLab. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever GitLab status changes.

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. PulsAPI's Starter plan includes up to 25 monitored services with Slack and email alerts, and the 30-day free trial requires no credit card. You can monitor GitLab alongside up to 24 other services at pulsapi.com/signup.

Track GitLab with the rest of your stack

Monitor 2463+ cloud services from one dashboard and get alerts when GitLab status changes.

Start free trial