GitLab experienced a major incident on June 11, 2026 affecting Website and GitLab agent server for Kubernetes (Google Compute Engine), lasting 13h 10m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 11, 2026, 07:08 AM UTC
We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information. 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 Jun 11, 2026, 07:08 AM UTC
We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information.
- investigating Jun 11, 2026, 07:11 AM UTC
We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information.
- investigating Jun 11, 2026, 07:11 AM UTC
We are currently investigating 5XX errors when accessing GitLab.com. We'll share another update as soon as we have more information.
- investigating Jun 11, 2026, 07:23 AM UTC
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.
- investigating Jun 11, 2026, 07:23 AM UTC
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.
- monitoring Jun 11, 2026, 08:06 AM UTC
The GitLab.com service is now operational. We are keep investigating why it is occurring intermittently.
- monitoring Jun 11, 2026, 08:06 AM UTC
The GitLab.com service is now operational. We are keep investigating why it is occurring intermittently.
- monitoring Jun 11, 2026, 12:16 PM UTC
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.
- monitoring Jun 11, 2026, 12:16 PM UTC
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.
- resolved Jun 11, 2026, 08:19 PM UTC
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 the issue should be resolved now.