GitLab incident

Background processing delays

GitLab is currently experiencing a minor incident affecting Background Processing and GitLab agent server for Kubernetes (Google Compute Engine), which began 3h ago. The vendor's full update timeline is below.

Started
May 07, 2026, 03:44 PM UTC
Resolved
Ongoing
Duration
● 2h 58m
Detected by Pingoru
May 07, 2026, 03:44 PM UTC

Affected components

Background ProcessingGitLab agent server for Kubernetes (Google Compute Engine)

Update timeline

  1. investigating May 07, 2026, 03:44 PM UTC

    We are investigating an issue background jobs being processed with delay. The problem is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22017.

  2. identified May 07, 2026, 04:45 PM UTC

    We have identified the cause of the background job processing delays. We are working to identify mitigating measures.

  3. monitoring May 07, 2026, 05:52 PM UTC

    The background job backlog has mostly cleared and merge train delays should be significantly reduced. We're keeping this incident in monitoring while we implement performance improvements. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22017

Looking to track GitLab downtime and outages?

Pingoru polls GitLab's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when GitLab reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track GitLab alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring GitLab for free

5 free monitors · No credit card required