Isitreallydown?
// Incident Post-MortemDRN-C66ED574

GitLab outage on April 8, 2026

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

April 8, 2026 14:46 UTCInvestigating - We are currently investigating an issue affecting the response time of database queries. Our team is actively investigating the root cause. More details can be found here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21732April 8, 2026 15:20 UTCMonitoring - Performance has improved following an earlier database performance issue that caused slower than normal responses on GitLab.com. We are continuing to monitor closely while we investigate the underlying cause. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items

Deterministic readout · awaiting AI summary pass

// Timeline

  1. Incident detected

    Minor confidence crossed the incident threshold for GitLab.com Service Degradation.

  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 Wed, Apr 08, 2026, 05:05 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.