Red Hat incident

Quay.io Intermittent HTTP 502 on Pull/Push

Major Resolved View vendor source →

Red Hat experienced a major incident on May 11, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 11, 2026, 02:12 PM UTC
Resolved
May 09, 2026, 07:30 PM UTC
Duration
Detected by Pingoru
May 11, 2026, 02:12 PM UTC

Update timeline

  1. resolved May 11, 2026, 02:12 PM UTC

    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.

  2. postmortem May 15, 2026, 05:11 PM UTC

    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.