Red Hat experienced a critical incident on May 7, 2026 affecting API and Registry, lasting 3h 4m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 07, 2026, 06:05 PM UTC
We are currently investigating this issue.
- investigating May 07, 2026, 06:20 PM UTC
Pulls have been restored. Pushes are unavailable while we continue to investigate.
- identified May 07, 2026, 08:06 PM UTC
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.
- monitoring May 07, 2026, 08:34 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 07, 2026, 08:44 PM UTC
We are continuing to monitor for any further issues.
- resolved May 07, 2026, 09:10 PM UTC
This incident has been resolved.
- postmortem May 15, 2026, 05:12 PM UTC
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.