Isitreallydown?
// Incident Post-MortemDRN-3416A516

GitLab outage on April 2, 2026

Minor severityResolved45 minDeveloper
Started · UTC
Apr 02, 03:50 AM
41d ago
Resolved · UTC
Apr 02, 04:35 AM
40d ago
Duration
45 min
End-to-end
Peak confidence
45.00
0 snapshots
// What happened

April 1, 2026 16:01 UTCInvestigating - We are investigating reports of Git clone failures and CI pipeline timeouts. Affected users may see "GitLab is currently unable to handle this request due to load" or "CI configuration fetch from Gitaly timed out." We are actively investigating and will provide updates as we learn more.April 1, 2026 17:04 UTCIdentified - We have begun rolling out a feature flag to address the intermittent Git clone failures and timeouts within pipelines. More details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21689.April 1, 2026 19:14 UTCIdentified

Deterministic readout · awaiting AI summary pass

// Timeline

  1. Incident detected

    Minor confidence crossed the incident threshold for Intermittent Git and CI/CD pipeline failures.

  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 Thu, Apr 02, 2026, 04:35 AM 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.