GitLab experienced a major incident on August 18, 2026 affecting Website and API and 1 more component, lasting 3h 34m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 18, 2026, 01:55 PM UTC
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://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729 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 Aug 18, 2026, 01:55 PM UTC
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://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729
- investigating Aug 18, 2026, 02:16 PM UTC
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
- investigating Aug 18, 2026, 02:16 PM UTC
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
- investigating Aug 18, 2026, 02:31 PM UTC
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
- investigating Aug 18, 2026, 02:31 PM UTC
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
- monitoring Aug 18, 2026, 02:49 PM UTC
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_items/22729
- monitoring Aug 18, 2026, 02:49 PM UTC
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_items/22729
- monitoring Aug 18, 2026, 04:11 PM UTC
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_items/22729
- monitoring Aug 18, 2026, 04:11 PM UTC
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_items/22729
- resolved Aug 18, 2026, 05:30 PM UTC
The error rate remains within normal thresholds and the issue is now resolved. Further details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729