- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Registry Account Management, API, registry.redhat.io, registry.access.redhat.com, Registry, registry.connect.redhat.com, Frontend
- Down Index
- 50of 100
What to do
Check whether you use Red Hat Quay.io Registry Account Management, API, registry.redhat.io, registry.access.redhat.com and 3 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 3h 5m it lasted.
Anything that failed between 2026-03-30 20:11 UTC and 2026-03-30 23:15 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 5
- identified
We are seeing 502s with quay.io pushes & pulls
provider
- identified
The team has identified the issue and is investigating. We've shifted Quay to be read-only now so pulls should gradually begin restoring but pushes will still fail.
provider
- monitoring
We've implemented a fix for the issue, pushes have been restored now.
provider
- resolved
Quay.io functionality has been restored.
provider
- postmortem
On March 30, 2026, Quay.io experienced a service disruption affecting image pulls and pushes, caused by an unexpected burst of resource-intensive operations that temporarily overloaded our primary database. Our engineering team mitigated the issue by failing over read traffic, restoring image pull capabilities within 45 minutes, and subsequently restored full push functionality once the database stabilized. We have since implemented enhanced traffic filtering and are actively optimizing our systems to prevent this from happening in the future.
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-98c6a3a4e0
Is Red Hat Quay.io still down?
No, this incident was resolved 2026-03-30 23:15 UTC. For Red Hat Quay.io's live state, see https://down.guide/quay.
How long did it last?
3h 5m, from 2026-03-30 20:11 UTC to 2026-03-30 23:15 UTC, by the times Red Hat Quay.io posted.
What was affected?
Red Hat Quay.io named Registry Account Management, API, registry.redhat.io, registry.access.redhat.com and 3 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.