Investigating
GitLab.com · degraded service
GitLab.com CI/CD pipelines delayed or not starting
Started today 14:33 UTC; still ongoing when ChangeIntel last read it, just now.
What it affected
As the provider names itWhat the provider posted
Newest first- today 15:22 UTCInvestigatingWe 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
- today 14:33 UTCInvestigatingWe 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/23190
- today 14:33 UTCInvestigatingWe 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
- today 15:24 UTC ChangeIntel noticed a new title; it was "Merge train pipelines delayed or not starting"
Around it
From the sources ChangeIntel reads; a match in time is not a causeElsewhere at the same time
- Cisco Meraki Cloud Communication Interruption
- Cloudflare Cloudflare Workers - Cron Trigger Activation Issues
- Cloudflare Audit Logs v2 ingestion is missing multiple Cloudflare products
- GitLab.com Increase of HTTP 50X errors on GitLab.com
- Cloudflare Elevated Errors in China Network Colos
- Cloudflare Cloudflare One Clients are incorrectly challenged on some sites
Earlier incidents in the 14 days before
- GitLab.com: Job delays on saas-linux-small-amd64 hosted runnersService incident · 13 Oct
- GitLab.com: GitLab Duo Workflow IssuesService incident · 12 Oct
- GitLab.com: Errors and slow performance on merge requests in the specific groups.Service incident · 10 Oct
Changed in the 14 days before
- GitLab Critical Patch Release: 19.4.2, 19.3.5, 19.2.8Revised by Microsoft · 2 times, latest 12 Oct
- GitLab AI Gateway Critical Patch Release: 19.2.4, 19.3.2, and 19.4.1Security advisory · 2 Oct
What changed
First observed 14 Oct 2026- 14 Oct 2026 SummaryWe 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 → 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
- 14 Oct 2026 TitleMerge train pipelines delayed or not starting → GitLab.com CI/CD pipelines delayed or not starting
- 14 Oct 2026 SummaryWe 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/23190 → 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
The most recent 100 field changes are listed. Complete recorded revisions are kept separately.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.
Keep track
- Service status now: every provider ChangeIntel reads, with ongoing incidents first.
- Status RSS feed: new and ended incidents as they happen.
- Everything about GitLab: its changes, known issues and incidents on one timeline.