Companies/Red Hat (incl. Quay.io)/Incidents

Red Hat (incl. Quay.io): quay.io API failures

Affected components: FrontendQuay.io - FrontendContainer Registries - registry.connect.redhat.comregistry.connect.redhat.comContainer Registries - registry.redhat.ioregistry.redhat.ioQuay.io - RegistryRegistryAPIQuay.io - APIContainer Registries - registry.access.redhat.comregistry.access.redhat.comContainer Registries - Registry Account ManagementRegistry Account Management

Timeline of updates

1. identified2026-03-30 20:11 UTC

   We are seeing 502s with quay.io pushes & pulls

2. identified2026-03-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.

3. monitoring2026-03-30 23:03 UTC

   We've implemented a fix for the issue, pushes have been restored now.

4. resolved2026-03-30 23:15 UTC

   Quay.io functionality has been restored.

5. postmortem2026-04-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.

Changes Rewindex caught on this incident

• Mar 30Major incident: quay.io API failures

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Red Hat (incl. Quay.io) profileRecent Red Hat (incl. Quay.io) incidentsMarkdownJSON