Companies / GitLab / incidents

GitLab: Jobs not being picked up/stuck pending

Affected components: CI/CDCI/CD - Hosted runners for GitLab community contributionsCI/CD - Hosted runners on LinuxCI/CD - Hosted runners on macOSCI/CD - Hosted runners on Windows

Timeline of updates

1. identified2026-05-18 11:03 UTC

   We've identified the root cause of some jobs not getting picked up due to runner pool exhaustion. We're working on getting more runners added to the pool. More details about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22145

2. monitoring2026-05-18 11:35 UTC

   We're seeing improvements in job queueing after additional runner allocations to the runner resource pool. We will continue to monitor until the the jobs are getting picked up at normal rates. More details about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22145

3. resolved2026-05-18 12:41 UTC

   We've continued to monitor the job queues following the additional provisioning of runners to the resource pool and we observe that the queueing is back to normal. This incident is moved to resolved. More details about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22145

Rewindex changes for this incident

• Major incident: Jobs not being picked up/stuck pending 2026-05-18 11:03 UTC

Impact, status and times are the vendor’s own, as last archived. View on status.gitlab.com (opens in new tab). GitLab profile · Recent GitLab incidents · Markdown · JSON