Isitreallydown?
// Incident Post-MortemDRN-1FBBF917

GitLab outage on April 28, 2026

Minor severityResolved45 minDeveloper
Started · UTC
Apr 28, 01:17 PM
14d ago
Resolved · UTC
Apr 28, 02:02 PM
14d ago
Duration
45 min
End-to-end
Peak confidence
45.00
0 snapshots
// What happened

April 28, 2026 11:05 UTCInvestigating - We are currently investigating issues with dependency scanning. More details about this incident can be found in `gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905`.April 28, 2026 12:02 UTCIdentified - We've identified cause of the issue and are working on resolving it. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905.April 28, 2026 13:17 UTCResolved - This incident has been resolved and dependency scanning is now operational. More information can be found in gitlab.com/gitlab-com/gl-infra/production/-/

Deterministic readout · awaiting AI summary pass

// Timeline

  1. Incident detected

    Minor confidence crossed the incident threshold for parsing error in the vulnerability reports.

  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 Tue, Apr 28, 2026, 02:02 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.