This incident is now resolved, as we didn’t see the issue return during our monitoring period and CI/CD pipelines are running normally. We’re continuing to investigate the root cause internally with details in gitlab.com/gitlab-com/gl-…. status.gitlab.com

We’re seeing recovery, and CI/CD pipelines should be running normally again. We’re continuing to monitor to confirm the issue doesn’t return while we investigate the root cause. status.gitlab.com

We’re continuing to investigate this issue and don’t have any new information to share at this time. Our team is working to identify the cause, and we’ll provide another update within an hour. status.gitlab.com

We're investigating reports of customers being unable to run pipelines on GitLab.com without encountering Gitaly-related errors. Details in gitlab.com/gitlab-com/gl-…. status.gitlab.com

After continuous monitoring, the latency has returned to baseline. We're marking this incident resolved.

Find more information about the incident here: gitlab.com/gitlab-com/gl-… status.gitlab.com

We continue to monitor the incident to ensure the issue doesn't recur.

Find more information about the incident here: gitlab.com/gitlab-com/gl-… status.gitlab.com

We've applied a mitigation for the intermittent slowness affecting CI/CD on GitLab.com, and performance has returned to normal. We're monitoring to make sure the issue doesn't recur. status.gitlab.com

We've identified a contributing factor to intermittent slowness affecting CI/CD on GitLab.com, including slower job requests, job updates and artifact uploads. We're still investigating the root cause and working to mitigate the issue. status.gitlab.com

Some users may have seen intermittent slowness with CI/CD jobs, including slower job updates and artifact uploads. Latency is recovering and we're continuing to investigate. status.gitlab.com

We're investigating elevated latency affecting CI/CD on GitLab.com. No user impact has been observed at this time. We'll update as we learn more. status.gitlab.com

The database maintenance for the Customers Portal (customers.gitlab.com) is complete. The Customers Portal and its APIs are available again and working normally. Thank you for your patience. status.gitlab.com

The database maintenance for the Customers Portal (customers.gitlab.com) is taking longer than planned. Our team needs more time to complete it. The Customers Portal and its APIs remain unavailable. We apologize for the inconvenie... status.gitlab.com

The scheduled database maintenance for the Customers Portal (customers.gitlab.com) has started. The Customers Portal and its APIs are temporarily unavailable. We expect the maintenance to end by 12:00 UTC. We’ll post an update when it’s complete. status.gitlab.com

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-… 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-… 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-… status.gitlab.com