Incidentsby Ibisquay.io API failures
Mar 30, 20:11 UTCMar 30, 23:15 UTC
Duration
3h 5m
Impact
Major
Root cause
Capacity
Red Hat, 90 days
32 incidents
Affected
Registry Account ManagementAPIregistry.redhat.ioregistry.access.redhat.comRegistryregistry.connect.redhat.comFrontendContainer Registries - Registry Account ManagementContainer Registries - registry.redhat.ioContainer Registries - registry.access.redhat.comContainer Registries - registry.connect.redhat.comQuay.io - APIQuay.io - RegistryQuay.io - Frontend
Final update
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.
Timeline
- Postmortem · Apr 20, 14:42 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.
- Resolved · Mar 30, 23:15 UTC
Quay.io functionality has been restored.
- Monitoring · Mar 30, 23:03 UTC
We've implemented a fix for the issue, pushes have been restored now.
- Identified · Mar 30, 20:58 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.
- Identified · Mar 30, 20:11 UTC
We are seeing 502s with quay.io pushes & pulls
More from Red Hat
Full historyAsk Red Hat - Outagelasted 0mQuay.io Push & Pulls Returning Intermittent 500 Issueslasted 2h 32mconsole.redhat.com Notifications - Emails Degradedlasted 4h 1m[Scheduled] Automation Hub Upgradestill open[Scheduled] Automation Hub Upgradestill open[Scheduled] OpenShift Cluster Manager Database Maintenance 2026-09-19lasted 2d 1h