RED HAT · Vendor
NO FIX YET
Not triaged yet. The sources’ own description is below.
first public May 7, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Who cares ops, redhat
Unknown from the sources.
Unknown from the sources.
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.
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.