# GitLab: GitLab.com Pipelines Cannot be Run

- Impact (vendor’s label): critical
- Status: resolved
- Started: 2026-01-28 20:35 UTC · Resolved: 2026-01-28 20:55 UTC · Duration: 20 min
- Updates: 3 · Affected components: CI/CD, CI/CD - Hosted runners for GitLab community contributions, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on macOS, CI/CD - Hosted runners on Windows, CI/CD - Self-managed runners
- [Vendor status page: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/697a73018a49c505b631ccdb](https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/697a73018a49c505b631ccdb)
- [Company: GitLab](https://rewindex.com/company/gitlab.md)

## Timeline of updates

- **investigating** 2026-01-28 20:35 UTC: We are currently seeing issues with starting pipelines on GitLab.com and are investigating the issue.
- **identified** 2026-01-28 20:41 UTC: We identified that a recently enabled feature flag may have contributed to the pipeline failures on GitLab.com. The feature flag was just disabled, and we're now seeing a sharp drop in error rates. Initial checks confirm that pipelines can now be started again. We're monitoring to ensure the issue is resolved for all users. Details can be found in https://gitlab.com/gitlab-com/gl-infra/production/-/work\_items/21160
- **resolved** 2026-01-28 20:55 UTC: We have identified and disabled a feature flag that was the cause. Error rates have returned to normal. Additional information can be found in https://gitlab.com/gitlab-com/gl-infra/production/-/work\_items/21160

## Rewindex changes for this incident

- 2026-01-28 20:35 UTC: [Critical incident: GitLab.com Pipelines Cannot be Run](https://rewindex.com/change/i478204845a4312.md)


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