Companies / GitLab / incidents
GitLab: Pipelines failing with 502 error
Affected components: CI/CD
Timeline of updates
- investigating
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
- investigating
We are still investigating "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
- investigating
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
- investigating
We are still investigating "502 Bad Gateway" errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
- investigating
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
- investigating
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
- investigating
We are still investigating the 502 intermittent errors when running pipelines. More details available at gitlab.com/gitlab-com/gl-infra/production/-/issues/21096
- investigating
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
- investigating
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
- investigating
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
- investigating
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
- investigating
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
- investigating
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
- investigating
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
- identified
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.
- resolved
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.
Rewindex changes for this incident
- Major incident: Pipelines failing with 502 error 2026-01-16 10:24 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