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.
Posted May 15, 2026 - 17:12 UTC
Resolved
This incident has been resolved.
Posted May 07, 2026 - 21:10 UTC
Update
We are continuing to monitor for any further issues.
Posted May 07, 2026 - 20:44 UTC
Monitoring
A fix has been implemented and we are monitoring the results.
Posted May 07, 2026 - 20:34 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.
Posted May 07, 2026 - 20:06 UTC
Update
Pulls have been restored. Pushes are unavailable while we continue to investigate.
