Quay experienced a major incident on June 1, 2026 affecting API and Build System and 1 more component, lasting 17h 42m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 01, 2026, 08:34 AM UTC
We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.
- identified Jun 01, 2026, 08:51 AM UTC
registry.redhat.io and registry.access.redhat.com are also affected by this outage
- investigating Jun 01, 2026, 09:13 AM UTC
We are currently investigating this issue.
- identified Jun 01, 2026, 10:22 AM UTC
We have identified the issue and are actively working to resolve it.
- monitoring Jun 01, 2026, 10:25 AM UTC
We have restored manifest pushes and are monitoring the environment for stability.
- identified Jun 01, 2026, 12:55 PM UTC
We've issued a fix and working on restoring writes on Quay.io
- monitoring Jun 01, 2026, 01:24 PM UTC
A fix has been implemented and we are currently monitoring the service
- investigating Jun 01, 2026, 02:24 PM UTC
We are investigating this issue.
- investigating Jun 01, 2026, 03:54 PM UTC
Pushes have been disabled while we work to identify a root cause. Pulls are available.
- identified Jun 01, 2026, 08:23 PM UTC
Push functionality has been restored for most quay.io traffic. Some traffic remains in read-only mode as recovery efforts continue
- monitoring Jun 01, 2026, 09:39 PM UTC
Image pushes have been restored. We are monitoring for recurrence. Security scanning will temporarily be unavailable.
- resolved Jun 02, 2026, 02:17 AM UTC
The service has been restored and is operating normally.