Isitreallydown?
// Incident Post-MortemDRN-B3E384D5

GitLab outage on April 20, 2026

Minor severityResolved45 minDeveloper
Started · UTC
Apr 20, 05:41 PM
22d ago
Resolved · UTC
Apr 20, 06:26 PM
22d ago
Duration
45 min
End-to-end
Peak confidence
45.00
0 snapshots
// What happened

April 20, 2026 15:42 UTCInvestigating - We are investigating an issue with pipelines where jobs are not being picked up or they are stuck in pending. See issue for more details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21835April 20, 2026 16:11 UTCInvestigating - We are continuing to investigate the issue; there are no material updates to share at this time. Follow https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21835 for details.April 20, 2026 16:27 UTCInvestigating - We’ve identified some potential causes but haven’t yet confirmed the root cause of the pr

Deterministic readout · awaiting AI summary pass

// Timeline

  1. Incident detected

    Minor confidence crossed the incident threshold for CI pipelines processing delays.

  2. Marked resolved

    The incident was closed after 45 min of observed impact.

// Signals by source0 sources

No per-source signal payloads were preserved in this incident's snapshot window.

// Aggregate evidence

Confidence scoring

45.00

The incident reached 45.00 peak confidence across available stored status snapshots.

User reports

0 / 15m

No elevated user-report volume was preserved in the incident window snapshots.

Status samples

0 affected

The incident row exists, but the bounded snapshot window does not include affected status samples.

Recovery signal

Resolved

Recovery was recorded at Mon, Apr 20, 2026, 06:26 PM UTC.

// User impact

GitLab users likely saw failed connections, degraded availability, or session instability for this Developer service. The incident reached Minor severity and lasted 45 min. The stored report window does not show a preserved user-report spike.