Critical incident

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

Affected: API, Registry

Current status of Red Hat: Minor issues — live Red Hat status

Timeline

1. May 7, 2026, 18:05 UTC
   investigating
   We are currently investigating this issue.
2. May 7, 2026, 18:20 UTC
   investigating
   Pulls have been restored. Pushes are unavailable while we continue to investigate.
3. May 7, 2026, 20:06 UTC
   identified
   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. May 7, 2026, 20:34 UTC
   monitoring
   A fix has been implemented and we are monitoring the results.
5. May 7, 2026, 20:44 UTC
   monitoring
   We are continuing to monitor for any further issues.
6. May 7, 2026, 21:10 UTC
   resolved
   This incident has been resolved.
7. May 15, 2026, 17:12 UTC
   postmortem
   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.

Updates as published by Red Hat (original).