What Happened

GitLab experienced an outage on May 12, 2026. The incident lasted approximately 5 minutes.

Complete DevOps platform delivered as a single application covering the entire software development lifecycle from planning to monitoring.

Timeline

Time (UTC)StatusDetails
18:38MonitoringError 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
18:28MonitoringWe 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 per...
18:25MonitoringWe 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.
18:04MonitoringWe'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 pi...
17:56MonitoringWe 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.
17:37MonitoringWe'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 s...
21:04ResolvedWe are seeing an increase in 5xx errors on GitLab.com and are investigating the issue. User may experience issues on GitLab.com. We will provide updates as we have them.
21:11ResolvedAll systems operational

Impact

The outage lasted approximately 5 minutes. GitLab runs on Google Cloud (GCP), AWS — check those status pages if you experienced cascading issues.

Resolution

GitLab has recovered and is now operational.

What To Do Next

---

This post was automatically generated by ServiceAlert.ai's monitoring system. View live status →