GitLab experienced a minor incident on May 12, 2026 affecting Website and API and 1 more component, lasting 3h 31m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 12, 2026, 05:37 PM UTC
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. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close
- investigating May 12, 2026, 05:37 PM UTC
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.
- investigating May 12, 2026, 05:56 PM UTC
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.
- investigating May 12, 2026, 05:56 PM UTC
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.
- investigating May 12, 2026, 06:04 PM UTC
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.
- investigating May 12, 2026, 06:04 PM UTC
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.
- identified May 12, 2026, 06:25 PM UTC
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.
- identified May 12, 2026, 06:25 PM UTC
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.
- identified May 12, 2026, 06:28 PM UTC
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
- identified May 12, 2026, 06:28 PM UTC
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
- monitoring May 12, 2026, 06:38 PM UTC
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
- monitoring May 12, 2026, 06:38 PM UTC
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
- resolved May 12, 2026, 09:08 PM UTC
This issue has been resolved and the affected Redis sidekiq cluster has recovered. More information can be found in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22103