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

We are investigating an issue affecting GitLab.com CI/CD. Some pipelines may remain in the created state for an extended period or fail to start, causing CI/CD workflows to stall. More Details at gitlab.com/gitlab-com/gl-inf… status.gitlab.com

The issue affecting customers.gitlab.com has been resolved. Customers Portal pages and subscription-related operations have returned to normal. More details: gitlab.com/gitlab-com/gl-inf… status.gitlab.com

Mitigations have been applied to customers.gitlab.com, and we are monitoring service availability. Intermittent errors may continue to affect Customers Portal pages and GitLab.com groups that rely on the portal for subscription-re... status.gitlab.com

No material updates to report. We'll share another update when we have more information. status.gitlab.com

No material updates to report. We are still investigating the root cause. status.gitlab.com

We have received reports that some groups on GitLab.com are experiencing HTTP 500 errors because the group is unable to sync with customers.gitlab.com. We are continuing to investigate the issue. status.gitlab.com

We're investigating an issue that's stopping pages on customers.gitlab.com from loading. Purchasing, renewing, and managing subscriptions may be affected. GitLab.com itself is not affected. status.gitlab.com

We have been monitoring this issue for a few days with no reported occurrences. status.gitlab.com

The source of the issue has been identified and we have taken steps to remediate and resolve the issue. GitLab.com is stable now. More details: gitlab.com/gitlab-com/gl-inf… status.gitlab.com