Active Incident

Updated a few seconds ago

This status page is exclusively intended for monitoring GitLab.com and its associated services. If there are any performance or service interruptions, an update will be posted here. If you are experiencing an issue that is not related to an active GitLab.com incident, or if you are encountering service interruptions on GitLab Dedicated, please submit a request via https://support.gitlab.com.
Elevated error rates on GitLab.comDegraded Performance

Incident Status

Degraded Performance

Components

Website, API, Git Operations, Package Registry, Container Registry, GitLab Pages, CI/CD, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners on macOS, CI/CD - Hosted runners for GitLab community contributions, CI/CD - Self-managed runners, SAML SSO - GitLab SaaS, Background Processing

Locations

Google Compute Engine, AWS, Self-Managed Runner Connectivity


May 12, 2026 18:38 UTC
MONITORING

Error rates have started to lower and return to normal values and we are actively monitoring the issue. The issue is being tracked in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22103

May 12, 2026 18:28 UTC
IDENTIFIED

We are continuing to investigate the issue. A major Redis Sidekiq cluster outage caused widespread elevated error rates and authentication failures for git, CI runners, and web services. We've performed targeted restarts and forced resets to restore service and are now seeing a drop in error rates. We are monitoring the recovery and health of the cluster. The issue is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22103

May 12, 2026 18:25 UTC
IDENTIFIED

We have identified the cause of the elevated error rates and are working to correct the issue. We will continue to post updates as we have them.

May 12, 2026 18:04 UTC
INVESTIGATING

We're investigating elevated error rates on GitLab.com. Some users may experience intermittent failures or degraded performance while we work to identify the cause. Users may experience delayed pipelines or pipelines not running. We'll share another update as soon as we have more information.

May 12, 2026 17:56 UTC
INVESTIGATING

We are seeing elevated error rates across GitLab.com and GitLab.com services. We are investigating the issue and will continue to update as we have more information.

May 12, 2026 17:37 UTC
INVESTIGATING

We're investigating elevated error rates on GitLab.com. Some users may experience intermittent failures or degraded performance while we work to identify the cause. We'll share another update as soon as we have more information.

Website




Degraded Performance

API




Degraded Performance

Git Operations




Degraded Performance

Package Registry




Degraded Performance

Container Registry




Degraded Performance

GitLab Pages




Degraded Performance

CI/CD




Degraded Performance

CI/CD - Hosted runners on Linux




Degraded Performance

CI/CD - Hosted runners on Windows




Degraded Performance

CI/CD - Hosted runners on macOS




Degraded Performance

CI/CD - Hosted runners for GitLab community contributions




Degraded Performance

CI/CD - Self-managed runners




Degraded Performance

SAML SSO - GitLab SaaS




Degraded Performance

Background Processing




Degraded Performance

GitLab Customers Portal




Operational

Support Services




Operational

packages.gitlab.com




Operational

version.gitlab.com




Operational

forum.gitlab.com




Operational

docs.gitlab.com




Operational

Canary




Operational

GitLab Duo




Operational

GitLab agent server for Kubernetes




Operational