Quay.io Push/Pull Degraded

What to do

• Check whether you use Red Hat API. 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 1h 19m it lasted.

  Anything that failed between 2026-04-21 22:50 UTC and 2026-04-22 00:09 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 4

1. investigatingApr 21, 2026, 10:50 PM UTC

   We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.

   provider

2. identifiedApr 21, 2026, 10:55 PM UTC

   Pull API is working again. We are actively working on bringing push API back online.

   provider

3. resolvedApr 22, 2026, 12:09 AM UTC

   Pull and Push APIs are fully up again. Service is working as expected.

   provider

4. postmortemMay 15, 2026, 5:18 PM UTC

   On April 21, a routine production deployment included a dependency upgrade that exposed a latent incompatibility, causing Quay.io application pods to crash on startup. Image pulls and pushes were fully unavailable for approximately 12 minutes before the team failed over to a secondary region, restoring pulls. Pushes remained unavailable for approximately 70 additional minutes while the deployment was reverted and traffic was incrementally shifted back to the primary region. We are enabling staging parity for all runtime features, improving automated rollback mechanisms, and isolating observability subsystems from the critical request path to prevent recurrence.

   provider

Corrections

None so far.

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