Isitreallydown?
// Incident Post-MortemDRN-E1EDB2E6

GitLab outage on May 6, 2026

Minor severityResolved45 minDeveloper
Started · UTC
May 06, 08:46 PM
6d ago
Resolved · UTC
May 06, 09:31 PM
6d ago
Duration
45 min
End-to-end
Peak confidence
25.00
18 snapshots
// What happened

May 6, 2026 19:01 UTCIdentified - A configuration update may cause some intermittent error messages on GitLab Next (Canary). We have identified the cause and the fix is in progress. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22008May 6, 2026 19:44 UTCIdentified - The fix is still in progress. For now, the workaround is to use GitLab - Current instead of GitLab - Next. More: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22008May 6, 2026 20:46 UTCResolved - We've applied our fix and confirmed this is no longer occurring. We will now mark this as resolve

Deterministic readout · awaiting AI summary pass

// Timeline

  1. Status changed to Operational

    The stored readout moved to Operational with confidence 55.00.

  2. Incident detected

    Minor confidence crossed the incident threshold for Intermittent errors observed on GitLab Next.

  3. Marked resolved

    The incident was closed after 45 min of observed impact.

  4. Peak confidence reached

    Confidence peaked at 55.00 while the service was marked Operational.

// Signals by source0 sources

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

// Aggregate evidence

Confidence scoring

25.00

The incident reached 25.00 peak confidence across 18 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 Wed, May 06, 2026, 09:31 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.