Major incident

Red Hat: Quay.io Push/Pull Degraded

Affected: API, Build System, Registry, Frontend, Security Scanning

Current status of Red Hat: Minor issues — live Red Hat status

Timeline

1. Jun 1, 2026, 08:34 UTC
   identified
   We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.
2. Jun 1, 2026, 08:51 UTC
   identified
   registry.redhat.io and registry.access.redhat.com are also affected by this outage
3. Jun 1, 2026, 09:13 UTC
   investigating
   We are currently investigating this issue.
4. Jun 1, 2026, 10:22 UTC
   identified
   We have identified the issue and are actively working to resolve it.
5. Jun 1, 2026, 10:25 UTC
   monitoring
   We have restored manifest pushes and are monitoring the environment for stability.
6. Jun 1, 2026, 12:55 UTC
   identified
   We've issued a fix and working on restoring writes on Quay.io
7. Jun 1, 2026, 13:24 UTC
   monitoring
   A fix has been implemented and we are currently monitoring the service
8. Jun 1, 2026, 14:24 UTC
   investigating
   We are investigating this issue.
9. Jun 1, 2026, 15:54 UTC
   investigating
   Pushes have been disabled while we work to identify a root cause. Pulls are available.
10. Jun 1, 2026, 20:23 UTC
    identified
    Push functionality has been restored for most quay.io traffic. Some traffic remains in read-only mode as recovery efforts continue
11. Jun 1, 2026, 21:39 UTC
    monitoring
    Image pushes have been restored. We are monitoring for recurrence. Security scanning will temporarily be unavailable.
12. Jun 2, 2026, 02:17 UTC
    resolved
    The service has been restored and is operating normally.

Updates as published by Red Hat (original).