RED HAT · Vendor
NO FIX YET
A routine production deployment of Quay.io, Red Hat's hosted container registry, included a dependency upgrade that crashed application pods on startup. Image pulls were down for about 12 minutes and pushes for about 70 more minutes before the service was restored.
first public Apr 21, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
This was an availability incident in Red Hat's hosted Quay.io service, not a vulnerability in software that customers run. Teams that pull images from quay.io could have seen failed pulls and pushes during the outage window. The sources do not describe any action for customers.
Not affected if self-hosted-registry
Who cares containers, quay.io, red-hat, redhat, security
Unknown from the sources.
Unknown from the sources.
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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.