Red Hat Status Page

May 9, 2026 · resolved May 9

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.

May 7, 2026 · resolved May 7

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.

May 5, 2026 · resolved May 5

This incident has been resolved.

Apr 21, 2026 · resolved Apr 22

On April 21, a routine production deployment included a dependency upgrade that exposed a latent incompatibility, causing Quay.io application pods to crash on startup. Image pulls and pushes were fully unavailable for approximately 12 minutes before the team failed over to a secondary region, restoring pulls. Pushes remained unavailable for approximately 70 additional minutes while the deployment was reverted and traffic was incrementally shifted back to the primary region. We are enabling staging parity for all runtime features, improving automated rollback mechanisms, and isolating observability subsystems from the critical request path to prevent recurrence.

Apr 3, 2026 · resolved Apr 16

The notifications for non-payg should work correctly.