- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 18of 100
What to do
Check whether your product depends on Red Hat. 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 0m it lasted.
Anything that failed between 2026-05-11 14:12 UTC and 2026-05-09 19:30 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 2
- resolved
For a period of 12 minutes (15:52–16:04 UTC), ~62% of manifest pulls and ~39% of manifest pushes failed with 502s. Quota insights has temporarily been disabled as part of remediation.
provider
- postmortem
On May 9, a surge of concurrent automated image pushes caused database lock contention that degraded Quay.io for approximately 18 minutes. Both image pushes and pulls returned errors during this window. The team identified and disabled an internal feature that amplified the contention, restoring service. We are redesigning this feature to operate asynchronously and improving our database locking mechanisms to better handle high-concurrency traffic.
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-f1165ccdc9
Is Red Hat still down?
No, this incident was resolved 2026-05-09 19:30 UTC. For Red Hat's live state, see https://down.guide/red-hat.
How long did it last?
0m, from 2026-05-11 14:12 UTC to 2026-05-09 19:30 UTC, by the times Red Hat posted.
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.