GitLab experienced in-memory errors causing failures in remote flows, Duo Developer, and other foundational workflows for 2.1 hours. Users encountered "Session failed" errors when requesting code reviews through GitLab Duo and other affected services. The incident was resolved by reverting the changes that caused the root issue.
We've identified failures for remote flows, including Duo Developer, and other foundational workflows. Users are seeing failures such as "Session failed" when requesting code reviews through GitLab Duo. The root cause has been identified and a revert is ongoing. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21429
No material updates at this time, the revert is still in progress. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21429
Still no material updates at this time, the revert is in progress. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21429
Still no material updates at this time, the revert is in progress. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21429
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6020 services available
Integrations with