Red Hat: Quay.io Pull/Push

What to do

Check whether you use Red Hat registry.redhat.io, registry.access.redhat.com, Registry, registry.connect.redhat.com. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide 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-11-12 21:24 UTC and 2026-11-12 21:24 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.

This incident was due to a database incident resulting in high CPU.

resolvedNov 12, 2026, 9:24 PM UTC
Quay.io and Red Hat Registry experienced a degradation where pulls and pushes failed between 20:14 - 20:25 UTC. During this period, customers may have experienced failed registry operations returning 500 errors. This incident was due to a database incident resulting in high CPU. This issue has since been resolved and registry operations have been restored.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Red Hat still down?

No, this incident was resolved 2026-11-12 21:24 UTC. For Red Hat's live state, see https://down.guide/providers/red-hat.

How long did it last?

0m, from 2026-11-12 21:24 UTC to 2026-11-12 21:24 UTC, by the times Red Hat posted.

What was affected?

Red Hat named registry.redhat.io, registry.access.redhat.com, Registry, registry.connect.redhat.com.

What caused it?

Red Hat wrote: "This incident was due to a database incident resulting in high CPU." The postmortem: https://stspg.io/nzbmnhx6g6y2

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.