- Level
- confirmed
- Worst impact
- Major outage
- Components
- API, Registry
- Down Index
- 42of 100
What to do
Check whether you use Red Hat API, Registry. 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 4m it lasted.
Anything that failed between 2026-05-07 18:05 UTC and 2026-05-07 21:10 UTC may need a replay.Subscribe to Red Hat's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=red-hat works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Red Hat 7
- investigating
We are currently investigating this issue.
provider
- investigating
Pulls have been restored. Pushes are unavailable while we continue to investigate.
provider
- identified
We have identified the issue as caused by a recent deployment. Our team has reverted the deployment, and are gradually rolling back traffic to our primary region to re-enable pushes while monitoring.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
This incident has been resolved.
provider
- postmortem
On May 7, a production deployment introduced a database locking conflict that caused Quay.io to become unhealthy. Image pulls were intermittently degraded for approximately 30 minutes and image pushes were unavailable for approximately 3 hours. The team failed over to a secondary region to restore pulls, then reverted the deployment to fully restore service. We are implementing multi-phase deployment rollouts, stricter canary processes, and health probe improvements to prevent recurrence.
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-6975a03391
Is Red Hat still down?
No, this incident was resolved 2026-05-07 21:10 UTC. For Red Hat's live state, see https://down.guide/red-hat.
How long did it last?
3h 4m, from 2026-05-07 18:05 UTC to 2026-05-07 21:10 UTC, by the times Red Hat posted.
What was affected?
Red Hat named API, Registry.
What caused it?
Red Hat hasn't published a root cause. If it does, it shows here.
Where does this come from?
Red Hat's official status page, https://status.redhat.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.