Companies / GitLab / incidents

GitLab: GitLab.com Pipelines Cannot be Run

Affected components: CI/CDCI/CD - Hosted runners for GitLab community contributionsCI/CD - Hosted runners on LinuxCI/CD - Hosted runners on macOSCI/CD - Hosted runners on WindowsCI/CD - Self-managed runners

Timeline of updates

1. investigating2026-01-28 20:35 UTC

   We are currently seeing issues with starting pipelines on GitLab.com and are investigating the issue.

2. identified2026-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

3. resolved2026-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

• Critical incident: GitLab.com Pipelines Cannot be Run 2026-01-28 20:35 UTC

Impact, status and times are the vendor’s own, as last archived. View on status.gitlab.com (opens in new tab). GitLab profile · Recent GitLab incidents · Markdown · JSON