Companies/Red Hat (incl. Quay.io)/Incidents

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

Affected components: Quay.io - RegistryRegistryAPIQuay.io - API

Timeline of updates

1. investigating2026-05-07 18:05 UTC

   We are currently investigating this issue.

2. investigating2026-05-07 18:20 UTC

   Pulls have been restored. Pushes are unavailable while we continue to investigate.

3. identified2026-05-07 20:06 UTC

   We have identified the issue as caused by a recent deployment. Our team has reverted the deployment, and are gradually rolling back traffic to our primary region to re-enable pushes while monitoring.

4. monitoring2026-05-07 20:34 UTC

   A fix has been implemented and we are monitoring the results.

5. monitoring2026-05-07 20:44 UTC

   We are continuing to monitor for any further issues.

6. resolved2026-05-07 21:10 UTC

   This incident has been resolved.

7. postmortem2026-05-15 17:12 UTC

   On May 7, a production deployment introduced a database locking conflict that caused Quay.io to become unhealthy. Image pulls were intermittently degraded for approximately 30 minutes and image pushes were unavailable for approximately 3 hours. The team failed over to a secondary region to restore pulls, then reverted the deployment to fully restore service. We are implementing multi-phase deployment rollouts, stricter canary processes, and health probe improvements to prevent recurrence.

Changes Rewindex caught on this incident

• May 7Critical incident: Quay.io HTTP 502 on Pull/Push

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Red Hat (incl. Quay.io) profileRecent Red Hat (incl. Quay.io) incidentsMarkdownJSON