Changes / Red Hat (incl. Quay.io) / Quay.io Push/Pull Degraded
Red Hat (incl. Quay.io): Major incident: Quay.io Push/Pull Degraded Summary
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed Struck in red is what Red Hat (incl. Quay.io) removed; blue is what they added. Muted text is unchanged context.
Before After
Added Title #1
Before: not present
After: Quay.io Push/Pull Degraded
Added Impact #2
Before: not present
After: major
Added Status #3
Before: not present
After: resolved
Added Start time #4
Before: not present
After: 2026-06-01 08:34 UTC
Added Resolved time #5
Before: not present
After: 2026-06-02 02:17 UTC
Added Affected components #6
Before: not present
After: API, Build System, Frontend, Quay.io - API, Quay.io - Build System, Quay.io - Frontend, Quay.io - Registry, Quay.io - Security Scanning, Registry, Security Scanning
Added Update identified 2026-06-01 08:34 UTC #7
Before: not present
After: We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.
Added Update identified 2026-06-01 08:51 UTC #8
Before: not present
After: registry.redhat.io and registry.access.redhat.com are also affected by this outage
Added Update investigating 2026-06-01 09:13 UTC #9
Before: not present
After: We are currently investigating this issue.
Added Update identified 2026-06-01 10:22 UTC #10
Before: not present
After: We have identified the issue and are actively working to resolve it.
Added Update monitoring 2026-06-01 10:25 UTC #11
Before: not present
After: We have restored manifest pushes and are monitoring the environment for stability.
Added Update identified 2026-06-01 12:55 UTC #12
Before: not present
After: We've issued a fix and working on restoring writes on Quay.io
Added Update monitoring 2026-06-01 13:24 UTC #13
Before: not present
After: A fix has been implemented and we are currently monitoring the service
Added Update investigating 2026-06-01 14:24 UTC #14
Before: not present
After: We are investigating this issue.
Added Update investigating 2026-06-01 15:54 UTC #15
Before: not present
After: Pushes have been disabled while we work to identify a root cause. Pulls are available.
Added Update identified 2026-06-01 20:23 UTC #16
Before: not present
After: Push functionality has been restored for most quay.io traffic. Some traffic remains in read-only mode as recovery efforts continue
Added Update monitoring 2026-06-01 21:39 UTC #17
Before: not present
After: Image pushes have been restored. We are monitoring for recurrence. Security scanning will temporarily be unavailable.
Added Update resolved 2026-06-02 02:17 UTC #18
Before: not present
After: The service has been restored and is operating normally.
First version of this incident archived by Rewindex. View the live incident (opens in new tab) .
Archive proof Rewindex commits each version of an incident to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked , and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run (00:41 UTC) commits it.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
History of this incident Monday, June 1 1 incident change
Major
08:34 Major incident Quay.io Push/Pull Degraded this change