Search

Changes / GitLab / Investigating delayed CI job pickup

GitLab: Major incident: Investigating delayed CI job pickup

Summary

Summary pending. The diff below shows exactly what changed.

Major incidentLabel: major (vendor)Changed Detected Source: status.gitlab.com (opens in new tab)

Incident page: full timeline of updates →

What changed

AddedTitle#1
Before: not present
After: Investigating delayed CI job pickup
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-09-02 11:54 UTC
AddedResolved time#5
Before: not present
After: 2026-09-02 12:43 UTC
AddedAffected components#6
Before: not present
After: CI/CD
AddedUpdateidentified#7
Before: not present
After: We are investigating an incident affecting GitLab.com CI/CD jobs using instance runners. Some jobs may remain pending longer than expected or may not be picked up by a runner, which can delay pipelines and deployments. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22845
AddedUpdateresolved#8
Before: not present
After: The incident affecting GitLab.com CI/CD jobs using instance runners is now resolved. Some jobs were delayed or remained pending while a manually initiated pg_repack database maintenance operation caused contention on the CI database, affecting runner communication and job pickup. The maintenance operation was terminated and runner metrics recovered. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22845

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: Investigating delayed CI job pickup (this change)Major incident

All GitLab changes → · GitLab profile · Markdown · JSON