# GitLab: Pipelines failing with 502 error

- Impact (vendor’s label): major
- Status: resolved
- Started: 2026-01-16 10:24 UTC · Resolved: 2026-01-16 20:23 UTC · Duration: 10.0 h
- Updates: 16 · Affected components: CI/CD
- [Vendor status page: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/696a11fab4db2704d6ca3eb7](https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/696a11fab4db2704d6ca3eb7)
- [Company: GitLab](https://rewindex.com/company/gitlab.md)

## Timeline of updates

- **investigating** 2026-01-16 10:24 UTC: 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** 2026-01-16 10:48 UTC: 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** 2026-01-16 11:14 UTC: 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** 2026-01-16 11:41 UTC: 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** 2026-01-16 12:16 UTC: 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** 2026-01-16 12:50 UTC: 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** 2026-01-16 13:32 UTC: 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** 2026-01-16 14:16 UTC: 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** 2026-01-16 15:04 UTC: 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** 2026-01-16 15:59 UTC: 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** 2026-01-16 16:52 UTC: 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** 2026-01-16 17:42 UTC: 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** 2026-01-16 18:39 UTC: 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** 2026-01-16 19:38 UTC: 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** 2026-01-16 20:15 UTC: 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** 2026-01-16 20:23 UTC: 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

- 2026-01-16 10:24 UTC: [Major incident: Pipelines failing with 502 error](https://rewindex.com/change/i46435f59ef0cc5.md)


---
Canonical: https://rewindex.com/company/gitlab/incidents/696a11fab4db2704d6ca3eb7 · Markdown: https://rewindex.com/company/gitlab/incidents/696a11fab4db2704d6ca3eb7.md · JSON: https://rewindex.com/api/v1/companies/gitlab/incidents/696a11fab4db2704d6ca3eb7 · Generated 2026-10-18T10:24:49.408Z