# Quay.io HTTP 502 on Pull/Push

- Provider: [Red Hat](https://down.guide/red-hat)
- Level: confirmed
- Impact: Major outage
- lasted 3h 4m
- started 2026-05-07 18:05 UTC
- API, Registry
- id: DWN-6975a03391
- Official page: https://stspg.io/wzmcf9349ldh

## Updates from Red Hat
### 2026-05-07 18:05 UTC: investigating
We are currently investigating this issue.

### 2026-05-07 18:20 UTC: investigating
Pulls have been restored. Pushes are unavailable while we continue to investigate.

### 2026-05-07 20:06 UTC: identified
We have identified the issue as caused by a recent deployment. Our team has reverted the deployment, and are gradually rolling back traffic to our primary region to re-enable pushes while monitoring.

### 2026-05-07 20:34 UTC: monitoring
A fix has been implemented and we are monitoring the results.

### 2026-05-07 20:44 UTC: monitoring
We are continuing to monitor for any further issues.

### 2026-05-07 21:10 UTC: resolved
This incident has been resolved.

### 2026-05-15 17:12 UTC: postmortem
On May 7, a production deployment introduced a database locking conflict that caused Quay.io to become unhealthy. Image pulls were intermittently degraded for approximately 30 minutes and image pushes were unavailable for approximately 3 hours. The team failed over to a secondary region to restore pulls, then reverted the deployment to fully restore service. We are implementing multi-phase deployment rollouts, stricter canary processes, and health probe improvements to prevent recurrence.

---
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).