GitLab incident

Jobs not being picked up/stuck pending

Minor Resolved View vendor source →

GitLab experienced a minor incident on May 18, 2026 affecting CI/CD and CI/CD - Hosted runners on Linux and 1 more component, lasting 1h 37m. The incident has been resolved; the full update timeline is below.

Started
May 18, 2026, 11:03 AM UTC
Resolved
May 18, 2026, 12:41 PM UTC
Duration
1h 37m
Detected by Pingoru
May 18, 2026, 11:03 AM UTC

Affected components

CI/CDCI/CD - Hosted runners on LinuxCI/CD - Hosted runners on WindowsCI/CD - Hosted runners on macOSCI/CD - Hosted runners for GitLab community contributionsversion.gitlab.com (AWS)GitLab agent server for Kubernetes (Google Compute Engine)

Update timeline

  1. identified May 18, 2026, 11:03 AM 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 Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

  2. identified May 18, 2026, 11:03 AM 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

  3. monitoring May 18, 2026, 11:35 AM 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

  4. monitoring May 18, 2026, 11:35 AM 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

  5. resolved May 18, 2026, 12:41 PM 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