quay.io API failures

What to do

• Check whether you use Red Hat Registry Account Management, API, registry.redhat.io, registry.access.redhat.com and 3 more. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 3h 5m it lasted.

  Anything that failed between 2026-03-30 20:11 UTC and 2026-03-30 23:15 UTC may need a replay.

• Subscribe to Red Hat's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=red-hat works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Red Hat 5

1. identifiedMar 30, 2026, 8:11 PM UTC

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

   provider

2. identifiedMar 30, 2026, 8: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.

   provider

3. monitoringMar 30, 2026, 11:03 PM UTC

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

   provider

4. resolvedMar 30, 2026, 11:15 PM UTC

   Quay.io functionality has been restored.

   provider

5. postmortemApr 20, 2026, 2: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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.