Major incident

Red Hat: quay.io API failures

Affected: Registry Account Management, API, registry.redhat.io, registry.access.redhat.com, Registry, registry.connect.redhat.com, Frontend

Current status of Red Hat: Minor issues — live Red Hat status

Timeline

1. Mar 30, 2026, 20:11 UTC
   identified
   We are seeing 502s with quay.io pushes & pulls
2. Mar 30, 2026, 20:58 UTC
   identified
   The team has identified the issue and is investigating. We've shifted Quay to be read-only now so pulls should gradually begin restoring but pushes will still fail.
3. Mar 30, 2026, 23:03 UTC
   monitoring
   We've implemented a fix for the issue, pushes have been restored now.
4. Mar 30, 2026, 23:15 UTC
   resolved
   Quay.io functionality has been restored.
5. Apr 20, 2026, 14:42 UTC
   postmortem
   On March 30, 2026, Quay.io experienced a service disruption affecting image pulls and pushes, caused by an unexpected burst of resource-intensive operations that temporarily overloaded our primary database. Our engineering team mitigated the issue by failing over read traffic, restoring image pull capabilities within 45 minutes, and subsequently restored full push functionality once the database stabilized. We have since implemented enhanced traffic filtering and are actively optimizing our systems to prevent this from happening in the future.

Updates as published by Red Hat (original).