Changes / GitLab / Pipelines failing with 502 error
GitLab: Major incident: Pipelines failing with 502 error
Summary
Summary pending. The diff below shows exactly what changed.
Incident page: full timeline of updates →
What changed
Before: not present
After: Pipelines failing with 502 error
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-01-16 10:24 UTC
Before: not present
After: 2026-01-16 20:23 UTC
Before: not present
After: CI/CD
Before: not present
After: We are currently investigating pipelines failing with "502 Bad Gateway" errors. More details available at https://gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
Before: not present
After: We are still investigating "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
Before: not present
After: We are investigating possible saturation. Users will still experience intermittent "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
Before: not present
After: We are still investigating "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
Before: not present
After: We are investigating a possible root cause, users still experience intermittent "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
Before: not present
After: We are investigating the rate limiting and related configuration changes is ongoing. Users might still experience intermittent 502 errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
Before: not present
After: We are still investigating the 502 intermittent errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
Before: not present
After: We are continuing to investigate possible backend performance bottlenecks and other upstream factors that could be causing the intermittent "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
Before: not present
After: We are continuing to investigate intermittent "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
Before: not present
After: Users still experience intermittent "502 Bad Gateway" errors when running pipelines. We are currently investigating previous Cloudflare configuration change. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
Before: not present
After: No material updates at this time. Users may still experience intermittent "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
Before: not present
After: Our team is currently working with Cloudflare to investigate the ongoing 502 errors. Users may still experience intermittent "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
Before: not present
After: No material updates at this time. Users may still experience intermittent "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
Before: not present
After: No material updates at this time. Users may still experience intermittent "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
Before: not present
After: Our team has identified that the 502 Bad Gateway errors were related to a Cloudflare Worker deployment in the HTTP router. A rollback of the deployment is showing a decline in 502 errors for the artifact endpoints. Our team is continuing to monitor.
Before: not present
After: This incident is now resolved. Our team has confirmed that the rollback fixed the issue and we are no longer seeing 502 Bad Gateway errors.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Pipelines failing with 502 error (this change) | Major incident |