RED HAT · Vendor
NO FIX YET
Not triaged yet. The sources’ own description is below.
first public May 9, 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 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.
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.