Rewindex

ChangesRed Hat (incl. Quay.io)Quay.io Intermittent HTTP 502 on Pull/Push

Red Hat (incl. Quay.io): Major incident: Quay.io Intermittent HTTP 502 on Pull/Push

Major incidentmajor (vendor)Changed Detected stspg.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Red Hat (incl. Quay.io) removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: Quay.io Intermittent HTTP 502 on Pull/Push
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: postmortem
AddedStart time#4
Before: not present
After: 2026-05-11 14:12 UTC
AddedResolved time#5
Before: not present
After: 2026-05-09 19:30 UTC
AddedUpdateresolved#6
Before: not present
After: For a period of 12 minutes (15:52–16:04 UTC), ~62% of manifest pulls and ~39% of manifest pushes failed with 502s. Quota insights has temporarily been disabled as part of remediation.
AddedUpdatepostmortem#7
Before: not present
After: On May 9, a surge of concurrent automated image pushes caused database lock contention that degraded Quay.io for approximately 18 minutes. Both image pushes and pulls returned errors during this window. The team identified and disabled an internal feature that amplified the contention, restoring service. We are redesigning this feature to operate asynchronously and improving our database locking mechanisms to better handle high-concurrency traffic.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run (00:41 UTC) commits it.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

History of this incident

Monday, May 11

1 incident change

All Red Hat (incl. Quay.io) changesRed Hat (incl. Quay.io) profileMarkdownJSON