GitLab experienced a minor incident on June 30, 2026 affecting Website and CI/CD and 1 more component, lasting 3h 14m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 30, 2026, 08:52 AM UTC
We are currently investigating an issue affecting CI pipelines not starting on merge requests. Our team is actively investigating the root cause. 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 30, 2026, 08:52 AM UTC
We are currently investigating an issue affecting CI pipelines not starting on merge requests. Our team is actively investigating the root cause.
- identified Jun 30, 2026, 09:37 AM UTC
We have identified that the sidekiq workers processing the jobs are getting deferred. The team is working on identifying the remediation steps.
- identified Jun 30, 2026, 09:37 AM UTC
We have identified that the sidekiq workers processing the jobs are getting deferred. The team is working on identifying the remediation steps.
- identified Jun 30, 2026, 10:51 AM UTC
No material updates to report. We are continuing to investigate the current issue and engineers are working to determine remediation steps.
- identified Jun 30, 2026, 10:51 AM UTC
No material updates to report. We are continuing to investigate the current issue and engineers are working to identify the cause.
- identified Jun 30, 2026, 11:19 AM UTC
Our engineers are still investigating the issue but jobs are starting to be processed with a delay. More details can be found here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22412
- identified Jun 30, 2026, 11:19 AM UTC
Our engineers are still investigating the issue but jobs are starting to be processed with a delay. More details can be found here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22412
- monitoring Jun 30, 2026, 11:39 AM UTC
Queues and runner backlog are trending back towards normal, while systems continue to work through the remaining backlog. Engineers are continuing to monitor this.
- monitoring Jun 30, 2026, 11:39 AM UTC
Queues and runner backlog are trending back towards normal, while systems continue to work through the remaining backlog. Engineers are continuing to monitor this.
- resolved Jun 30, 2026, 12:07 PM UTC
Incident has now been mitigated and runner backlogs are now back to normal. CI pipelines are now resuming. Engineers will continue to monitor this recovery.