Skip to main content
Red Hat

Quay.io Push/Pull Degraded

Partial outage Lasted 17h 43m · started · Red Hat's page

Level
confirmed
Worst impact
Partial outage
Components
API, Build System, Registry, Frontend, Security Scanning
Down Index
34of 100

What to do

  • Check whether you use Red Hat 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'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 12

  1. identified

    We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.

    provider

  2. identified

    registry.redhat.io and registry.access.redhat.com are also affected by this outage

    provider

  3. investigating

    We are currently investigating this issue.

    provider

  4. identified

    We have identified the issue and are actively working to resolve it.

    provider

  5. monitoring

    We have restored manifest pushes and are monitoring the environment for stability.

    provider

  6. identified

    We've issued a fix and working on restoring writes on Quay.io

    provider

  7. monitoring

    A fix has been implemented and we are currently monitoring the service

    provider

  8. investigating

    We are investigating this issue.

    provider

  9. investigating

    Pushes have been disabled while we work to identify a root cause. Pulls are available.

    provider

  10. identified

    Push functionality has been restored for most quay.io traffic. Some traffic remains in read-only mode as recovery efforts continue

    provider

  11. monitoring

    Image pushes have been restored. We are monitoring for recurrence. Security scanning will temporarily be unavailable.

    provider

  12. 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-737a89cb15

Is Red Hat still down?

No, this incident was resolved 2026-06-02 02:17 UTC. For Red Hat's live state, see https://down.guide/red-hat.

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 posted.

What was affected?

Red Hat named API, Build System, Registry, Frontend and 1 more.

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.