Partial Service Disruption
July 2, 2025 17:29 UTC
[Monitoring] GitLab is continuing to monitor this incident. User impact is minimal and we are waiting for deployments to complete. No further updates are anticipated until the deployment completes. More details at gitlab.com/gitlab-com/gl-infra/production/-/issues/20101
July 2, 2025 15:47 UTC
[Identified] No material updates to report. We are still applying mitigating steps and the user impact is still minimal. More details at gitlab.com/gitlab-com/gl-infra/production/-/issues/20101
July 2, 2025 14:51 UTC
[Identified] We are still applying mitigating steps. Impact for our users should be minimal at the moment. More details at gitlab.com/gitlab-com/gl-infra/production/-/issues/20101
July 2, 2025 13:56 UTC
[Identified] We are reverting back the incident as active, we are still implementing mitigation steps. Users might experience delays in job creation or intermittent errors linked to background jobs queuing. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20101
July 2, 2025 13:20 UTC
[Monitoring] No material updates to report. We are still applying mitigating steps. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20101
July 2, 2025 12:13 UTC
[Monitoring] We continue to monitor the situation and there is no user impact at the moment. To resolve the underlying issue, we are currently applying mitigating steps. Next update expected in one hour. https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20101
July 2, 2025 09:18 UTC
[Monitoring] We are seen an improvement in the situation, CI/CD jobs should execute normally. As we are still working on fixing the underline issue we will keep monitoring the situation, next update expected in 3 hours. gitlab.com/gitlab-com/gl-infra/production/-/issues/20101
July 2, 2025 08:51 UTC
[Investigating] We are investigating possible solutions to relieve pressure on the database and job queues. This incident could affect pipeline job executions as well as prefilled CI/CD variables. More details can be found at: gitlab.com/gitlab-com/gl-infra/production/-/issues/20101
July 2, 2025 08:10 UTC
[Investigating] We are investigating a possible cause related to slow queries, this incident could impact more than prefilled CI/CD variables. More details can be found at: gitlab.com/gitlab-com/gl-infra/production/-/issues/20101
July 2, 2025 07:52 UTC
[Investigating] We continue to investigate the issue where prefilled CI/CD variables are not loading when starting a new pipeline on GitLab.com. More details can be found at: gitlab.com/gitlab-com/gl-infra/production/-/issues/20101
July 2, 2025 07:31 UTC
[Investigating] We continue to investigate the issue where prefilled CI/CD variables are not loading when starting a new pipeline on GitLab.com. More details can be found at: gitlab.com/gitlab-com/gl-infra/production/-/issues/20101
July 2, 2025 07:13 UTC
[Investigating] We continue to investigate the issue where prefilled CI/CD variables are not loading when starting a new pipeline on GitLab.com. More details can be found at: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20101
July 2, 2025 06:50 UTC
[Investigating] We continue to investigate the issue where prefilled CI/CD variables are not loading when starting a new pipeline on GitLab.com. More details can be found at: gitlab.com/gitlab-com/gl-infra/production/-/issues/20101
July 2, 2025 06:06 UTC
[Investigating] We are currently investigating an issue where prefilled CI/CD variables are not loading when starting a new pipeline on GitLab.com. More details can be found at: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20101
