GitLab outage on April 14, 2026
April 14, 2026 05:23 UTCInvestigating - We are investigating the failure of GitLab runners to pull container images. We will provide updates as more information becomes available.April 14, 2026 06:09 UTCIdentified - We have identified an MR that causes this issue. We are working on reverting this change.April 14, 2026 07:01 UTCMonitoring - The rollback is finished and our internal testing indicates that GitLab-maintained images are once again pulling as expected. We will monitor the situation before marking this incident as resolved. More details https://gitlab.com/gitlab-com/gl-infra/producti
Deterministic readout · awaiting AI summary pass
Incident detected
Minor confidence crossed the incident threshold for Failures when GitLab Runners pull container image.
Marked resolved
The incident was closed after 45 min of observed impact.
No per-source signal payloads were preserved in this incident's snapshot window.
Confidence scoring
45.00The incident reached 45.00 peak confidence across available stored status snapshots.
User reports
0 / 15mNo elevated user-report volume was preserved in the incident window snapshots.
Status samples
0 affectedThe incident row exists, but the bounded snapshot window does not include affected status samples.
Recovery signal
ResolvedRecovery was recorded at Tue, Apr 14, 2026, 08:50 AM UTC.
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.