GitLab experienced a minor incident on June 18, 2026 affecting Background Processing and GitLab agent server for Kubernetes (Google Compute Engine), lasting 2h 45m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 18, 2026, 02:02 PM UTC
We've identified a recent code change as the likely cause of elevated Sidekiq job execution errors on the low-urgency-cpu-bound shard, which may delay processing of some background jobs. Mitigations are in progress. We'll continue to update as soon as the mitigation is merged and deployed. 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
- identified Jun 18, 2026, 02:02 PM UTC
We've identified a recent code change as the likely cause of elevated Sidekiq job execution errors on the low-urgency-cpu-bound shard, which may delay processing of some background jobs. Mitigations are in progress. We'll continue to update as soon as the mitigation is merged and deployed.
- resolved Jun 18, 2026, 04:48 PM UTC
A recent code change was rolled back and the error rates have subsided since it was merged. Our team has been monitoring and performance has returned to expected levels. This incident is now resolved. https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22335