Search

Changes / GitLab / GitLab.com CI/CD pipelines delayed or not starting

GitLab: Major incident: GitLab.com CI/CD pipelines delayed or not starting

Summary

GitLab.com reported a major CI/CD incident: merge train, scheduled, and child/downstream pipelines were delayed or failed to start, with delayed mergeability analysis and webhook notifications plus general site errors and slowness. It ran from 2026-10-14 14:33 UTC to 2026-10-14 18:30 UTC (3 h 57 min). GitLab reported remediation and restored stability without specifying the cause or fix.

Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.

Major incidentLabel: degradation (model (Jev), 49%)Changed Detected Source: status.gitlab.com (opens in new tab)

Discussed on Hacker News

Threads are matched automatically by vendor name and timing; points and comments refresh every 30 minutes. Method and limits.

Incident page: full timeline of updates →

What changed

AddedTitle#1
Before: not present
After: GitLab.com CI/CD pipelines delayed or not starting
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-10-14 14:33 UTC
AddedResolved time#5
Before: not present
After: 2026-10-14 18:30 UTC
AddedAffected components#6
Before: not present
After: CI/CD
AddedUpdateinvestigating#7
Before: not present
After: We are investigating an issue affecting GitLab.com merge trains. Some merge train pipelines may remain in the created state for an extended period or fail to start, causing merge trains and related CI/CD workflows to stall. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192
AddedUpdateinvestigating#8
Before: not present
After: We are investigating an issue affecting GitLab.com CI/CD. Merge train, scheduled, and child/downstream pipelines may be delayed, remain in a created or pending state, or fail to start. Mergeability analysis and webhook notifications may also be delayed. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192
AddedUpdateinvestigating#9
Before: not present
After: We are investigating an issue affecting GitLab.com and general site errors and slowness related to the initial issue. We are actively investigating the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192
AddedUpdateidentified#10
Before: not present
After: We identified the issue affecting GitLab.com and general site errors and slowness related to the initial issue. We are actively working to resolve the issue. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192
AddedUpdateresolved#11
Before: not present
After: The source of the issue has been identified and we have taken steps to remediate and resolve the issue. GitLab.com is stable now. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: GitLab.com CI/CD pipelines delayed or not starting (this change)
GitLab.com reported a major CI/CD incident: merge train, scheduled, and child/downstream pipelines were delayed or failed to start, with delayed mergeability analysis and webhook notifications plus general site errors and slowness. It ran from 2026-10-14 14:33 UTC to 2026-10-14 18:30 UTC (3 h 57 min). GitLab reported remediation and restored stability without specifying the cause or fix.
Major incident

All GitLab changes → · GitLab profile · Markdown · JSON