GitLab.com Status

With the configuration changes, we were able to process the backlog and jobs are being processed normally. More details can be found in the issue: gitlab.com/gitlab-com/gl-… status.gitlab.com

Our team is working on configuration changes to improve resourcing. We're still seeing a job backlog and are continuing to monitor with these changes. status.gitlab.com

Our team has identified a resource issue that has lead to a delay in pending jobs on Small GitLab Hosted Runners. Users with CI jobs tagged for small runners (saas-linux-small-amd64) might experience some delays. Our team is continuing to work on this. status.gitlab.com

We are currently investigating issues with hosted `saas-linux-small-amd64` GitLab runners. More details about this incident can be found in gitlab.com/gitlab-com/gl-… status.gitlab.com

This incident has been resolved and dependency scanning is now operational. More information can be found in gitlab.com/gitlab-com/gl-…. status.gitlab.com

We've identified cause of the issue and are working on resolving it. More details can be found in gitlab.com/gitlab-com/gl-…. status.gitlab.com

We are currently investigating issues with dependency scanning. More details about this incident can be found in `gitlab.com/gitlab-com/gl-…`. status.gitlab.com

Latency and service health has stabalized after a period of monitoring. Incident is considered resolved. More details in: gitlab.com/gitlab-com/gl-… status.gitlab.com

We have increased max concurrency and are monitoring the impact on latency. We'll further investigate segfaults, which may have contributed to this incident. More details in: gitlab.com/gitlab-com/gl-… status.gitlab.com

The root cause is still under investigation. We are taking steps to address the sustained request saturation in order to mitigate latency issues. More details in: gitlab.com/gitlab-com/gl-… status.gitlab.com

We are investigating which model and provider are causing the latency. Apdex for ai-assisted service is not stable yet. More details in: gitlab.com/gitlab-com/gl-… status.gitlab.com

We are investigating issues related to our ai-assisted service and ai-gateway. Some users may experience higher latency or errors affecting Duo features. More details here: gitlab.com/gitlab-com/gl-… status.gitlab.com

The root cause has been identified and addressed, and monitoring shows the incident to be resolved. status.gitlab.com

We detected increased error rates for web services on gitlab.com. This recovered after 5 minutes. We're monitoring the situation to ensure the service remains stable. status.gitlab.com

Pipeline job metrics have returned to a healthy state and jobs are being picked up and processed normally. We consider this incident resolved. Follow the incident: gitlab.com/gitlab-com/gl-… status.gitlab.com

We’ve rolled out an infrastructure change and pending job metrics are improving. We’ll continue to monitor. Follow the incident: gitlab.com/gitlab-com/gl-… status.gitlab.com

We are seeing infrastructure capacity errors and we’re inclined to treat this as the likely cause; investigation continues. Details: gitlab.com/gitlab-com/gl-… status.gitlab.com

We’ve identified some potential causes but haven’t yet confirmed the root cause of the problem. Investigation continues. Track progress: gitlab.com/gitlab-com/gl-… status.gitlab.com

We are continuing to investigate the issue; there are no material updates to share at this time. Follow gitlab.com/gitlab-com/gl-… for details. status.gitlab.com

We are investigating an issue with pipelines where jobs are not being picked up or they are stuck in pending. See issue for more details: gitlab.com/gitlab-com/gl-… status.gitlab.com