CI/CD Job Delays on GitLab.com

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-10-15 19:50 UTC and 2026-10-15 19:50 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.

Updates from GitLab 1

1. resolvedOct 15, 2026, 7:50 PM UTC

   October 15, 2026 16:19 UTC Investigating - We are investigating an issue affecting GitLab.com CI/CD. Some pipelines may remain in the created state for an extended period or fail to start, causing CI/CD workflows to stall. More Details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234 October 15, 2026 17:23 UTC Identified - We have identified the cause of the issue causing CI/CD delays on GitLab.com and are working to take corrective actions. The issue may persists intermittently as we do so. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234 October 15, 2026 19:50 UTC Resolved - We have taken steps to mitigate the delays on CI/CD jobs on GitLab.com and services have returned to normal. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234

   provider

Corrections

None so far.

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