GitLab experienced a minor incident on June 23, 2026 affecting Git Operations and GitLab agent server for Kubernetes (Google Compute Engine), lasting 2h 18m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 23, 2026, 05:33 PM UTC
We are investigating ongoing errors when attempting to interact with repositories via SSH. HTTPS does not appear to be impacted at this time. We are investigating. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364 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 23, 2026, 05:33 PM UTC
We are investigating ongoing errors when attempting to interact with repositories via SSH. HTTPS does not appear to be impacted at this time. We are investigating. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364
- identified Jun 23, 2026, 05:52 PM UTC
We have identified the problematic change causing this behavior and are working to revert it. Details will be posted in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364
- identified Jun 23, 2026, 05:52 PM UTC
We have identified the problematic change causing this behavior and are working to revert it. Details will be posted in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364
- identified Jun 23, 2026, 06:09 PM UTC
We are still working to revert this problematic change as quickly as possible. Once reverted, we will post an update here. Details will be made available in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364
- identified Jun 23, 2026, 06:09 PM UTC
We are still working to revert this problematic change as quickly as possible. Once reverted, we will post an update here. Details will be made available in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364
- monitoring Jun 23, 2026, 06:25 PM UTC
We've addressed the underlying issue and are observing SSH interactions succeed. We will place this incident in a monitoring state as we keep an eye on things. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364
- monitoring Jun 23, 2026, 06:25 PM UTC
We've addressed the underlying issue and are observing SSH interactions succeed. We will place this incident in a monitoring state as we keep an eye on things. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364
- resolved Jun 23, 2026, 07:52 PM UTC
We have continued to observe successful SSH interactions after implementing our mitigating changes. We will now mark this as resolved. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22364