We have resolved the issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are continuing to monitor the platform. The impact may have included partial degradation to the web UI and Git operations. status.gitlab.com

We identified and resolved an issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are monitoring the platform to ensure the issue remains resolved. More details here: gitlab.com/gitlab-com/gl-inf… status.gitlab.com

The monitoring period has concluded, and the incident has been confirmed resolved. See the issue for more details: gitlab.com/gitlab-com/gl-inf… status.gitlab.com

The Customers Portal is loading normally again, and we are no longer observing the intermittent 404 errors affecting sign-in and page loading. A redeployment has completed successfully, and we are monitoring the service for any recurrence before resolvi... status.gitlab.com

We’re continuing our investigation of 404s on the customers panel. We’ll update you as we learn more. status.gitlab.com

We've investigating 404s on the customers panel. We'll update as we learn more status.gitlab.com

We have not seen any more HTTP 500 errors for GitLab Secrets Manager since the mitigation was applied. This incident is now resolved. Details: gitlab.com/gitlab-com/gl-inf… status.gitlab.com

This issue affects projects and groups using GitLab Secrets Manager. Users saw HTTP 500 errors, not 503 as previously stated. A mitigation has been applied and we're monitoring. Details: gitlab.com/gitlab-com/gl-inf… status.gitlab.com

We're investigating intermittent HTTP 503 errors when opening project pages. At this time, this issue only occurs in specific projects. More details at: gitlab.com/gitlab-com/gl-inf… status.gitlab.com

The issue is fully resolved and operations on GitLab.com and GitLab Duo are operating normally. More details at: gitlab.com/gitlab-com/gl-inf… status.gitlab.com

We have taken steps to resolve the slowness and 503s on GitLab.com and are monitoring the situation. More details at: gitlab.com/gitlab-com/gl-inf… status.gitlab.com

Most services on GitLab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: gitlab.com/gitlab-com/gl-inf… status.gitlab.com

We have identified the cause of 503s on GitLab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: gitlab.com/gitlab-com/gl-inf… status.gitlab.com

We are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: gitlab.com/gitlab-com/gl-inf… status.gitlab.com

We are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details. status.gitlab.com

The issue causing CI/CD failures and UI slowness for a limited number of GitLab.com customers has been resolved. Thank you for your patience. status.gitlab.com

We've applied a temporary mitigation to address CI/CD failures and UI slowness affecting a limited number of GitLab.com customers. We're monitoring recovery while working on a longer-term solution. status.gitlab.com

We’re investigating an issue affecting CI/CD on GitLab.com for a limited number of customers.  Pipelines may fail with the following error: “CI configuration fetch from Gitaly timed out. This may indicate Gitaly service slowness ... status.gitlab.com

We have taken steps to mitigate the delays on CI/CD jobs on GitLab.com and services have returned to normal. More details at: gitlab.com/gitlab-com/gl-inf… status.gitlab.com

We have identified the cause of the issue causing CI/CD delays on GitLab.com and are working to take corrective actions. The issue may persists intermittently as we do so. More details at: gitlab.com/gitlab-com/gl-inf… status.gitlab.com