- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API, Build System, Registry, Frontend, Security Scanning
- Down Index
- 53of 100
What to do
Check whether you use Red Hat Quay.io API, Build System, Registry, Frontend and 1 more. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 17h 43m it lasted.
Anything that failed between 2026-06-01 08:34 UTC and 2026-06-02 02:17 UTC may need a replay.Subscribe to Red Hat Quay.io's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=quay works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Red Hat Quay.io 12
- identified
We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.
provider
- identified
registry.redhat.io and registry.access.redhat.com are also affected by this outage
provider
- investigating
We are currently investigating this issue.
provider
- identified
We have identified the issue and are actively working to resolve it.
provider
- monitoring
We have restored manifest pushes and are monitoring the environment for stability.
provider
- identified
We've issued a fix and working on restoring writes on Quay.io
provider
- monitoring
A fix has been implemented and we are currently monitoring the service
provider
- investigating
We are investigating this issue.
provider
- investigating
Pushes have been disabled while we work to identify a root cause. Pulls are available.
provider
- identified
Push functionality has been restored for most quay.io traffic. Some traffic remains in read-only mode as recovery efforts continue
provider
- monitoring
Image pushes have been restored. We are monitoring for recurrence. Security scanning will temporarily be unavailable.
provider
- resolved
The service has been restored and is operating normally.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-37d01c7fed
Is Red Hat Quay.io still down?
No, this incident was resolved 2026-06-02 02:17 UTC. For Red Hat Quay.io's live state, see https://down.guide/quay.
How long did it last?
17h 43m, from 2026-06-01 08:34 UTC to 2026-06-02 02:17 UTC, by the times Red Hat Quay.io posted.
What was affected?
Red Hat Quay.io named API, Build System, Registry, Frontend and 1 more.
What caused it?
Red Hat Quay.io hasn't published a root cause. If it does, it shows here.
Where does this come from?
Red Hat Quay.io's official status page, https://status.redhat.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.