# GitLab: Delays in background processing

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-02-24 17:11 UTC · Resolved: 2026-02-25 18:58 UTC · Duration: 26 h
- Updates: 7 · Affected components: Background Processing, CI/CD, Website
- [Vendor status page: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/699ddbb845393d060bc68849](https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/699ddbb845393d060bc68849)
- [Company: GitLab](https://rewindex.com/company/gitlab.md)

## Timeline of updates

- **investigating** 2026-02-24 17:11 UTC: We’re investigating increased background processing delays on GitLab.com that are affecting pipeline execution and merge trains. Our engineering team is actively working to identify the cause and restore normal performance. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work\_items/21361
- **investigating** 2026-02-24 17:28 UTC: We do not have a material update to share at this time. Our engineering team continues to actively investigate and will provide further updates as soon as more information becomes available. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work\_items/21361
- **investigating** 2026-02-24 17:47 UTC: We continue to see delays in background job processing on GitLab.com. Our engineers continue to investigate the root cause and work to restore normal performance. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/21361
- **identified** 2026-02-24 18:19 UTC: Background processing on GitLab.com has largely recovered, and user experience has noticeably improved over the past 15 minutes. We’re continuing to investigate the root cause and will share additional updates if we see any recurrence. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work\_items/21361
- **identified** 2026-02-24 18:54 UTC: Background processing on GitLab.com continues to improve, but some users may still experience delays in pipeline execution and merge trains while the backlog is processed. Our engineers continue to investigate the root cause. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work\_items/21361
- **monitoring** 2026-02-24 19:36 UTC: Background processing on GitLab.com has stabilized. We will continue monitoring for the next 24 hours. If the issue does not recur, this incident will be resolved. Otherwise, we’ll provide updates and take additional action as needed. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work\_items/21361
- **resolved** 2026-02-25 18:58 UTC: After continued monitoring, performance has remained stable and within normal levels. As systems are operating as expected, this incident is now marked as resolved. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work\_items/21361


---
Canonical: https://rewindex.com/company/gitlab/incidents/699ddbb845393d060bc68849 · Markdown: https://rewindex.com/company/gitlab/incidents/699ddbb845393d060bc68849.md · JSON: https://rewindex.com/api/v1/companies/gitlab/incidents/699ddbb845393d060bc68849 · Generated 2026-10-18T11:26:02.566Z