Degraded performance affecting Duo features
Affected: GitLab DuoGitLab agent server for Kubernetes (Google Compute Engine)
GitLab Outage History
GitLab is up right nowGitLab had 58 outages in the last 2 years totaling 116h 24m of downtime — averaging 2.4 incidents per month.
There were 58 GitLab outages since April 28, 2026 totaling 116h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.
Slowed pipelines and CI/CD Jobs
Affected: CI/CDGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 3 updates
Elevated 5xx Errors on GitLab.com
Affected: WebsiteGit OperationsCI/CDGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 5 updates
500 errors accessing repositories
Affected: WebsiteGit OperationsGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 3 updates
- investigating May 11, 2026, 08:41 AM UTC
We are currently investigating 500 errors when accessing repositories and Gitaly errors when pushing to a repository. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041
- monitoring May 11, 2026, 09:12 AM UTC
To restore the service, we restarted the Gitaly process. We will monitor for any recurrence. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041
- resolved May 11, 2026, 11:16 AM UTC
The issue has been resolved. The 500 errors when accessing repositories should not seen anymore and affected Git operations should work as expected. More details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22041
Background processing delays
Affected: Background ProcessingGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 7 updates
Intermittent errors observed on GitLab Next
Affected: CanaryGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 2 updates
- identified May 06, 2026, 07:01 PM UTC
A configuration update may cause some intermittent error messages on GitLab Next (Canary). We have identified the cause and the fix is in progress. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22008
- identified May 06, 2026, 07:44 PM UTC
The fix is still in progress. For now, the workaround is to use GitLab - Current instead of GitLab - Next. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22008
Small GitLab Hosted Runners
Affected: CI/CD - Hosted runners on LinuxGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 3 updates
- investigating Apr 30, 2026, 03:51 PM UTC
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-infra/production/-/work_items/21936
- identified Apr 30, 2026, 04:10 PM UTC
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.
- identified Apr 30, 2026, 04:38 PM UTC
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.
parsing error in the vulnerability reports
Affected: WebsiteGitLab agent server for Kubernetes (Google Compute Engine)
Timeline · 2 updates
- investigating Apr 28, 2026, 11:05 AM UTC
We are currently investigating issues with dependency scanning. More details about this incident can be found in `gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905`.
- identified Apr 28, 2026, 12:02 PM UTC
We've identified cause of the issue and are working on resolving it. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905.