Changes / GitLab / GitLab.com Pipelines Cannot be Run
GitLab: Critical incident: GitLab.com Pipelines Cannot be Run
Summary
Summary pending. The diff below shows exactly what changed.
Major incidentLabel: outage (model (Jev), 100%)Changed Detected Source: status.gitlab.com (opens in new tab)
Incident page: full timeline of updates →
What changed
Before: not present
After: GitLab.com Pipelines Cannot be Run
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-01-28 20:35 UTC
Before: not present
After: 2026-01-28 20:55 UTC
Before: not present
After: 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
Before: not present
After: We are currently seeing issues with starting pipelines on GitLab.com and are investigating the issue.
Before: not present
After: 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
Before: not present
After: 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
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: GitLab.com Pipelines Cannot be Run (this change) | Major incident |