What Happened
GitLab experienced an outage on August 18, 2026. The incident lasted approximately 3 hours 35 minutes.
Complete DevOps platform delivered as a single application covering the entire software development lifecycle from planning to monitoring.
Timeline
| Time (UTC) | Status | Details |
|---|---|---|
| 16:11 | Investigating | The error rate has continued to remain within normal thresholds. We're continuing to monitor the error rate. Further developments can be read here: gitlab.com/gitlab-com/gl-infra/production/-/work... |
| 14:49 | Investigating | Our monitoring shows the error rate decreasing towards normal thresholds. We're continuing to monitor the incident. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_... |
| 14:31 | Investigating | Investigation for the root cause of 500 errors while fetching commits on GitLab.com is still ongoing. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729 |
| 14:16 | Investigating | We are still investigating the root cause for 500 errors while fetching commits on GitLab.com. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729 |
| 13:55 | Investigating | We are investigating an issue causing a subset of requests to GitLab.com receiving 500 errors. We will provide updates as we learn more from our investigation. More information here: https://gitla... |
| 17:37 | Resolved | All systems operational |
Impact
The outage lasted approximately 3 hours 35 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 →