GitLab incident

Issue with processing CI jobs

Minor Resolved View vendor source →

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

Started
Jun 05, 2026, 11:58 AM UTC
Resolved
Jun 05, 2026, 01:46 PM UTC
Duration
1h 47m
Detected by Pingoru
Jun 05, 2026, 11:58 AM UTC

Affected components

CI/CDCI/CD - Hosted runners on LinuxGitLab agent server for Kubernetes (Google Compute Engine)

Update timeline

  1. investigating Jun 05, 2026, 11:58 AM UTC

    We are investigating an issue where CI jobs are not processing. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256 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. investigating Jun 05, 2026, 11:58 AM UTC

    We are investigating an issue where CI jobs are not processing. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

  3. identified Jun 05, 2026, 12:08 PM UTC

    We have identified a recent change as a possible root cause and we are working on rolling back the change. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

  4. identified Jun 05, 2026, 12:08 PM UTC

    We have identified a recent change as a possible root cause and we are working on rolling back the change. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

  5. identified Jun 05, 2026, 12:51 PM UTC

    We are still working on rolling back the change that we believe is the root cause. This issue impacts GitLab Hosted Runners and Hosted Runners on Linux. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

  6. identified Jun 05, 2026, 12:51 PM UTC

    We are still working on rolling back the change that we believe is the root cause. This issue impacts GitLab Hosted Runners and Hosted Runners on Linux. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

  7. identified Jun 05, 2026, 12:53 PM UTC

    We are still working on rolling back the change that we believe is the root cause. This issue impacts GitLab Hosted Runners and Hosted Runners on Linux. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

  8. identified Jun 05, 2026, 12:53 PM UTC

    We are still working on rolling back the change that we believe is the root cause. This issue impacts GitLab Hosted Runners and Hosted Runners on Linux. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

  9. identified Jun 05, 2026, 01:04 PM UTC

    The change has been reverted and we are seeing that error rates are recovering. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

  10. identified Jun 05, 2026, 01:04 PM UTC

    The change has been reverted and we are seeing that error rates are recovering. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

  11. monitoring Jun 05, 2026, 01:15 PM UTC

    Error rates have recovered back to normal levels and we started processing jobs again. We expect that the job queue should be processed over the next 30 minutes. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

  12. monitoring Jun 05, 2026, 01:15 PM UTC

    Error rates have recovered back to normal levels and we started processing jobs again. We expect that the job queue should be processed over the next 30 minutes. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256

  13. resolved Jun 05, 2026, 01:46 PM UTC

    The job queue is now cleared and we do not expect any further customer impact. This is considered resolved. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22256