We are continuing to investigate recent reports of prefilled CI/CD variables not loading when starting a new pipeline on GitLab.com. We are currently applying mitigating steps. More details can be found at: gitlab.com/gitlab-com/gl-… status.gitlab.com

No material updates to report. We are still applying mitigating steps. More details at gitlab.com/gitlab-com/gl-… status.gitlab.com

The additional replica has been added and is taking traffic. We are now monitoring GitLab.com. CI Job processing and background jobs should be returning to normal operations. More details can be found at gitlab.com/gitlab-com/gl-…. status.gitlab.com

No material updates to report. We continue to monitor GitLab.com. More details can be found at gitlab.com/gitlab-com/gl-… status.gitlab.com

We are seeing delays in background processing of the git commit worker. Our engineers are currently investigating. More details in: gitlab.com/gitlab-com/gl-… status.gitlab.com

No material updates at this point, and we are still investigating. More details in: gitlab.com/gitlab-com/gl-… status.gitlab.com

There are no material updates to report. We don't think that users are actually impacted at this point, and we are monitoring the situation. More details in: gitlab.com/gitlab-com/gl-… status.gitlab.com

We have no material updates at this time. We have not observed any More details in: gitlab.com/gitlab-com/gl-… status.gitlab.com

We are resolving this incident. GitLab has been monitoring and we have confirmed the issue is resolved. More details in: gitlab.com/gitlab-com/gl-… status.gitlab.com

The incident has been resolved. GitLab has been monitoring and we have confirmed the issue is fixed. More details can be found at: gitlab.com/gitlab-com/gl-… status.gitlab.com

We're currently looking into the incident of OAuth refresh tokens incorrectly deleted. We're investigating the root cause of this issue. You can refer to the workarounds and follow updates to the incident here: gitlab.com/gitlab-com/gl-… status.gitlab.com

We're still looking into the root cause of the incident. You can refer to the workarounds and follow updates to the incident here: gitlab.com/gitlab-com/gl-… status.gitlab.com

We're still looking into the root cause of the incident. Follow updates of the incident and the mentioned workarounds here: gitlab.com/gitlab-com/gl-… status.gitlab.com

We've identified the root cause of the incident. And we're working on the best course of action to resolve the incident. Follow updates of the incident and the mentioned workarounds here: gitlab.com/gitlab-com/gl-… status.gitlab.com

We've identified the root cause of the incident. And the next course of action to resolve the incident is being worked on. Follow updates of the incident and the mentioned workarounds here: gitlab.com/gitlab-com/gl-… status.gitlab.com

We're still working on the next course of action to resolve the incident. Follow updates of the incident and the mentioned workarounds here: gitlab.com/gitlab-com/gl-… status.gitlab.com

We've identified the root cause and efforts are currently underway to implement a resolution. We’ll share another update as soon as we have more details on next steps. For updates and workarounds, please see: gitlab.com/gitlab-com/gl-… status.gitlab.com

We continue to monitor the issue affecting OAuth refresh tokens on GitLab.com. If you observed errors with your OAuth integrations on Jul 4th or after, please apply the suggested workarounds to restore access. Details in: https://... status.gitlab.com

We're investigating an issue where Cosign signing fails for container images and build artifacts in forked projects due to missing claims. Our team is actively working on a fix. status.gitlab.com

Our team is in the process of reverting the change identified as the root cause of the issue. We will provide our next update once the revert has been deployed and the issue has been successfully mitigated. status.gitlab.com