Quay experienced a major incident on April 21, 2026 affecting API, lasting 1h 19m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 21, 2026, 10:50 PM UTC
We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.
- identified Apr 21, 2026, 10:55 PM UTC
Pull API is working again. We are actively working on bringing push API back online.
- resolved Apr 22, 2026, 12:09 AM UTC
Pull and Push APIs are fully up again. Service is working as expected.
- postmortem May 15, 2026, 05: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.