Isitreallydown?
// Incident Post-MortemDRN-4D2963FA

GitLab outage on April 30, 2026

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

April 30, 2026 15:51 UTCInvestigating - We are currently investigating issues with hosted `saas-linux-small-amd64` GitLab runners. More details about this incident can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21936April 30, 2026 16:10 UTCIdentified - Our team has identified a resource issue that has lead to a delay in pending jobs on Small GitLab Hosted Runners. Users with CI jobs tagged for small runners (saas-linux-small-amd64) might experience some delays. Our team is continuing to work on this.April 30, 2026 16:38 UTCIdentified - Our team is working on configurati

Deterministic readout · awaiting AI summary pass

// Timeline

  1. Incident detected

    Minor confidence crossed the incident threshold for Small GitLab Hosted Runners.

  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 30, 2026, 05:45 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.