GitLab: CI pipelines stuck in pending state
Affected components: CI/CD
Timeline of updates
- investigating
We are currently investigating the cause of CI pipelines being stuck in pending state. More details can be found here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22433 (opens in new tab)
- investigating
We are continuing to investigate and look into CI pipelines being stuck in pending state.
- resolved
Incident has now been mitigated. CI pipelines are now resuming. Engineers will continue to monitor this recovery.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
36c59a76b0980c5a…
Impact, status and times are the vendor’s own, as last archived. View on status.gitlab.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by GitLab, started 2026-07-01 13:14 UTC, resolved after 50 min, 3 update(s).
- Title
- CI pipelines stuck in pending state
- Vendor
- GitLab
- Date
- URL
- https://rewindex.com/company/gitlab/incidents/6a4512c18614df05b0373725
GitLab profileRecent GitLab incidentsAll outages on July 1, 2026GitLab in July 2026MarkdownJSON