What Happened
GitLab experienced an outage on June 30, 2026. The incident lasted approximately 2 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 |
|---|---|---|
| 08:52 | Resolved | We are currently investigating an issue affecting CI pipelines not starting on merge requests. Our team is actively investigating the root cause. |
| 18:26 | Monitoring | We have identified the issue and taken action to correct the matter and are monitoring GitLab.com. We will provide further updates as information is available or when the issue is confirmed resolved. |
| 17:39 | Monitoring | We are continuing to investigate and work to resolve the degraded performance on GitLab.com |
| 16:52 | Monitoring | We have identified the cause of the increased error rate and are taking corrective action and monitoring the incident. |
| 16:44 | Monitoring | We are continuing to investigate and look into the increased errors on GitLab.com |
| 16:08 | Monitoring | We are investigating the cause, but the symptoms are: 500 errors, CI jobs can't check out repos, slow merge request page loading, slow page loading |
| 21:53 | Resolved | We are investigating errors with code suggestion not completing. |
| 00:02 | Resolved | All systems operational |
Impact
The outage lasted approximately 2 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 →