GitLab favicon

GitLab outage on 2026-11-03

gitlab.com
November 2026 3 Minor incident

GitLab.com had two separate CI/CD problems on 3 November 2026, one lasting 4h 44m and a second lasting 1h 27m. Both were GitLab-side infrastructure issues, not anything in your own pipeline configuration.

Started

05:10 UTC

Duration

Lasted 4h 44m

Source

IsDown

Next time

GitLab is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

What happened?

The first incident started at 05:10 UTC, when GitLab reported elevated latency affecting CI/CD on GitLab.com. Early updates said no user impact had been observed, then within 20 minutes GitLab revised that, noting some users saw intermittent slowness with job updates and artifact uploads. By 06:01 GitLab said it had identified a contributing factor but was still chasing the root cause. A mitigation went out at 07:10 and performance returned to normal, with GitLab then monitoring for recurrence. The incident closed after 4h 44m, and GitLab's own work item link is the only further detail offered, there is no separate post-mortem on this page. A second, unrelated incident started at 17:24 UTC, described as customers being unable to run pipelines without encountering Gitaly-related errors. GitLab gave one update at 17:52 saying it had nothing new to share, then reported recovery at 18:20, closing that incident at 1h 27m. Across both incidents GitLab filed eight updates in total and listed no specific components as affected. No user reports were filed during either window on this page, so what you see here comes entirely from GitLab's own status updates.

Learning

Both incidents here were Gitaly and CI/CD backend problems, the layer that runs jobs and talks to storage behind the scenes, not the layer a simple ping or page-load check from your side would ever touch. That is why an external check watching GitLab.com's homepage or API uptime could have stayed green through this entire day while your pipelines were genuinely stuck or slow. GitLab's first update even said "no user impact observed" before walking that back twenty minutes later, which shows how slowly provider-side awareness can catch up to what's actually happening to jobs in flight. The pattern here, slow job updates and failed artifact uploads in the first incident, Gitaly errors blocking pipeline runs in the second, is the shape to watch for: things submit but don't complete, or complete and then error out partway. GitLab's 90 day history shows 38 incidents with a median duration of 3 hours 24 minutes, so this kind of disruption isn't rare for CI/CD on GitLab.com. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.