# Red Hat (incl. Quay.io): Critical incident: Quay.io HTTP 502 on Pull/Push

**Summary:** _summary pending_
- Kind: Major incident · Label: critical (vendor)
- Changed: 2026-05-07 18:05 UTC · Detected: 2026-10-19 18:53 UTC
- [Source: https://stspg.io/wzmcf9349ldh](https://stspg.io/wzmcf9349ldh)
- [Company: Red Hat (incl. Quay.io)](https://rewindex.com/company/red-hat.md)
- Versions: before (none: first archived) → after incident\_version:753/3vlkclps2214@d3d293ffb236
- Change 1 of 1 for this incident

Incident page (full timeline): [Quay.io HTTP 502 on Pull/Push](https://rewindex.com/company/red-hat/incidents/3vlkclps2214.md)
## What changed

**1. Added: Title**

```diff
+ Quay.io HTTP 502 on Pull/Push
```

**2. Added: Impact**

```diff
+ critical
```

**3. Added: Status**

```diff
+ postmortem
```

**4. Added: Start time**

```diff
+ 2026-05-07 18:05 UTC
```

**5. Added: Resolved time**

```diff
+ 2026-05-07 21:10 UTC
```

**6. Added: Affected components**

```diff
+ API, Quay.io - API, Quay.io - Registry, Registry
```

**7. Added: Update** (investigating) · 2026-05-07 18:05 UTC

```diff
+ We are currently investigating this issue.
```

**8. Added: Update** (investigating) · 2026-05-07 18:20 UTC

```diff
+ Pulls have been restored. Pushes are unavailable while we continue to investigate.
```

**9. Added: Update** (identified) · 2026-05-07 20:06 UTC

```diff
+ 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.
```

**10. Added: Update** (monitoring) · 2026-05-07 20:34 UTC

```diff
+ A fix has been implemented and we are monitoring the results.
```

**11. Added: Update** (monitoring) · 2026-05-07 20:44 UTC

```diff
+ We are continuing to monitor for any further issues.
```

**12. Added: Update** (resolved) · 2026-05-07 21:10 UTC

```diff
+ This incident has been resolved.
```

**13. Added: Update** (postmortem) · 2026-05-15 17:12 UTC

```diff
+ 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.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-05-07 18:05 UTC | Critical incident: Quay.io HTTP 502 on Pull/Push (this change) | critical |

All Red Hat (incl. Quay.io) changes: [timeline](https://rewindex.com/company/red-hat/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._


---
Canonical: https://rewindex.com/change/i50b26d33dc3701 · Markdown: https://rewindex.com/change/i50b26d33dc3701.md · JSON: https://rewindex.com/api/v1/changes/i50b26d33dc3701 · Generated 2026-10-20T00:17:20.684Z