# quay.io API failures

- Provider: [Red Hat Quay.io](https://down.guide/quay)
- Level: confirmed
- Impact: Partial outage
- lasted 3h 5m
- started 2026-03-30 20:11 UTC
- Registry Account Management, API, registry.redhat.io +4
- id: DWN-98c6a3a4e0
- Official page: https://stspg.io/rky6skxs2n5r

## Updates from Red Hat Quay.io
### 2026-03-30 20:11 UTC: identified
We are seeing 502s with quay.io pushes & pulls

### 2026-03-30 20:58 UTC: identified
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.

### 2026-03-30 23:03 UTC: monitoring
We've implemented a fix for the issue, pushes have been restored now.

### 2026-03-30 23:15 UTC: resolved
Quay.io functionality has been restored.

### 2026-04-20 14:42 UTC: postmortem
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.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).