Quay.io Push/Pull Degraded

Incident Report for Red Hat

Resolved

The service has been restored and is operating normally.
Posted Jun 02, 2026 - 02:17 UTC

Monitoring

Image pushes have been restored. We are monitoring for recurrence. Security scanning will temporarily be unavailable.
Posted Jun 01, 2026 - 21:39 UTC

Identified

Push functionality has been restored for most quay.io traffic. Some traffic remains in read-only mode as recovery efforts continue
Posted Jun 01, 2026 - 20:23 UTC

Update

Pushes have been disabled while we work to identify a root cause. Pulls are available.
Posted Jun 01, 2026 - 15:54 UTC

Investigating

We are investigating this issue.
Posted Jun 01, 2026 - 14:24 UTC

Monitoring

A fix has been implemented and we are currently monitoring the service
Posted Jun 01, 2026 - 13:24 UTC

Identified

We've issued a fix and working on restoring writes on Quay.io
Posted Jun 01, 2026 - 12:55 UTC

Monitoring

We have restored manifest pushes and are monitoring the environment for stability.
Posted Jun 01, 2026 - 10:25 UTC

Identified

We have identified the issue and are actively working to resolve it.
Posted Jun 01, 2026 - 10:22 UTC

Investigating

We are currently investigating this issue.
Posted Jun 01, 2026 - 09:13 UTC

Update

registry.redhat.io and registry.access.redhat.com are also affected by this outage
Posted Jun 01, 2026 - 08:51 UTC

Identified

We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.
Posted Jun 01, 2026 - 08:34 UTC
This incident affected: Quay.io (API, Build System, Registry, Frontend, Security Scanning).