Resolved after 3 hours 4 minutes, affecting Registry Account Management and API and 1 more, on March 30, 2026.
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.
Affected components
Update timeline
- identified Mar 30, 2026, 08:11 PM UTC
We are seeing 502s with quay.io pushes & pulls
- identified Mar 30, 2026, 08:58 PM UTC
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.
- monitoring Mar 30, 2026, 11:03 PM UTC
We've implemented a fix for the issue, pushes have been restored now.
- resolved Mar 30, 2026, 11:15 PM UTC
Quay.io functionality has been restored.
- postmortem Apr 20, 2026, 02:42 PM UTC
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.
Your product runs on more than Red Hat
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services