# Red Hat (incl. Quay.io): Major incident: quay.io API failures

**Summary:** _summary pending_
- Kind: Major incident · Label: major (vendor)
- Changed: 2026-03-30 20:11 UTC · Detected: 2026-10-19 18:53 UTC
- [Source: https://stspg.io/rky6skxs2n5r](https://stspg.io/rky6skxs2n5r)
- [Company: Red Hat (incl. Quay.io)](https://rewindex.com/company/red-hat.md)
- Versions: before (none: first archived) → after incident\_version:753/04vm68m00t61@b6335a576e1c
- Change 1 of 1 for this incident

Incident page (full timeline): [quay.io API failures](https://rewindex.com/company/red-hat/incidents/04vm68m00t61.md)
## What changed

**1. Added: Title**

```diff
+ quay.io API failures
```

**2. Added: Impact**

```diff
+ major
```

**3. Added: Status**

```diff
+ postmortem
```

**4. Added: Start time**

```diff
+ 2026-03-30 20:11 UTC
```

**5. Added: Resolved time**

```diff
+ 2026-03-30 23:15 UTC
```

**6. Added: Affected components**

```diff
+ API, Container Registries - registry.access.redhat.com, Container Registries - Registry Account Management, Container Registries - registry.connect.redhat.com, Container Registries - registry.redhat.io, Frontend, Quay.io - API, Quay.io - Frontend, Quay.io - Registry, Registry, registry.access.redhat.com, Registry Account Management, registry.connect.redhat.com, registry.redhat.io
```

**7. Added: Update** (identified) · 2026-03-30 20:11 UTC

```diff
+ We are seeing 502s with quay.io pushes & pulls
```

**8. Added: Update** (identified) · 2026-03-30 20:58 UTC

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

**9. Added: Update** (monitoring) · 2026-03-30 23:03 UTC

```diff
+ We've implemented a fix for the issue, pushes have been restored now.
```

**10. Added: Update** (resolved) · 2026-03-30 23:15 UTC

```diff
+ Quay.io functionality has been restored.
```

**11. Added: Update** (postmortem) · 2026-04-20 14:42 UTC

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

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-03-30 20:11 UTC | Major incident: quay.io API failures (this change) | major |

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/iff2bc869d239c0 · Markdown: https://rewindex.com/change/iff2bc869d239c0.md · JSON: https://rewindex.com/api/v1/changes/iff2bc869d239c0 · Generated 2026-10-20T00:17:11.134Z