What Happened
GitLab experienced an outage on June 11, 2026. The incident lasted approximately 13 hours 5 minutes.
Complete DevOps platform delivered as a single application covering the entire software development lifecycle from planning to monitoring.
Timeline
| Time (UTC) | Status | Details |
|---|---|---|
| 12:16 | Investigating | GitLab.com is currently operating normally. We have confirmed the root cause was a Cloud provider incident affecting a disk backing our primary database, and we are continuing to monitor closely. |
| 08:06 | Investigating | The GitLab.com service is now operational. We are keep investigating why it is occurring intermittently. |
| 07:23 | Investigating | We changed the status title to reflect the intermittent nature of this incident. We'll share another update as soon as we have more information. |
| 07:11 | Investigating | We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information. |
| 07:08 | Investigating | We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information. |
| 20:22 | Resolved | All systems operational |
Impact
The outage lasted approximately 13 hours 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
- View GitLab live status and outage history
- Set up alerts to get notified instantly next time GitLab has an issue
- Compare GitLab reliability with other services
---
This post was automatically generated by ServiceAlert.ai's monitoring system. View live status →