# GitLab: Failures when GitLab Runners pull container image

- Impact (vendor’s label): major
- Status: resolved
- Started: 2026-04-14 05:23 UTC · Resolved: 2026-04-14 08:05 UTC · Duration: 2.7 h
- Updates: 4 · Affected components: CI/CD
- [Vendor status page: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/69ddcf3f75cad505fa6eed55](https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/69ddcf3f75cad505fa6eed55)
- [Company: GitLab](https://rewindex.com/company/gitlab.md)

## Timeline of updates

- **investigating** 2026-04-14 05:23 UTC: We are investigating the failure of GitLab runners to pull container images. We will provide updates as more information becomes available.
- **identified** 2026-04-14 06:09 UTC: We have identified an MR that causes this issue. We are working on reverting this change.
- **monitoring** 2026-04-14 07:01 UTC: The rollback is finished and our internal testing indicates that GitLab-maintained images are once again pulling as expected. We will monitor the situation before marking this incident as resolved. More details https://gitlab.com/gitlab-com/gl-infra/production/-/work\_items/21778
- **resolved** 2026-04-14 08:05 UTC: We continued to monitor following the rollback and have confirmed that image pulls are functioning normally for GitLab Runners. This incident is now resolved. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work\_items/21778

## Rewindex changes for this incident

- 2026-04-14 05:23 UTC: [Major incident: Failures when GitLab Runners pull container image](https://rewindex.com/change/i1471de88f7a840.md)


---
Canonical: https://rewindex.com/company/gitlab/incidents/69ddcf3f75cad505fa6eed55 · Markdown: https://rewindex.com/company/gitlab/incidents/69ddcf3f75cad505fa6eed55.md · JSON: https://rewindex.com/api/v1/companies/gitlab/incidents/69ddcf3f75cad505fa6eed55 · Generated 2026-10-18T11:26:03.471Z