Issues Running Pipelines

What to do

• Check whether your product depends on GitLab. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-11-03 18:51 UTC and 2026-11-03 18:51 UTC may need a replay.

• Subscribe to GitLab's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=gitlab works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

Our team is working to identify the cause, and we’ll provide another update within an hour.

Updates from GitLab 1

1. resolvedNov 3, 2026, 6:51 PM UTC

   November 3, 2026 17:20 UTC Investigating - We're investigating reports of customers being unable to run pipelines on GitLab.com without encountering Gitaly-related errors. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23401. November 3, 2026 17:52 UTC Investigating - We’re continuing to investigate this issue and don’t have any new information to share at this time. Our team is working to identify the cause, and we’ll provide another update within an hour. November 3, 2026 18:20 UTC Monitoring - We’re seeing recovery, and CI/CD pipelines should be running normally again. We’re continuing to monitor to confirm the issue doesn’t return while we investigate the root cause. November 3, 2026 18:51 UTC Resolved - This incident is now resolved, as we didn’t see the issue return during our monitoring period and CI/CD pipelines are running normally. We’re continuing to investigate the root cause internally with details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23401.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.