Red Hat outage, 12 November 2026

Quay.io Pull/Push

Started
Resolved
12 Nov 2026, 21:24 UTC
Impact
Major
Affected
registry.redhat.io, registry.access.redhat.com, Registry, registry.connect.redhat.com

Is this still happening?

No. Red Hat marked this incident resolved on 12 Nov 2026, 21:24 UTC.

Right now: Red Hat is running scheduled maintenance - some features may be briefly unavailable. (as of 13 Nov, 20:53 UTC) Live Red Hat status

At a glance

Our summary from the Red Hat incidents we have recorded since 12 Jun 2026 - how we count.

Last update from Red Hat

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.

12 Nov 2026, 21:24 UTC

Read the full incident on the official Red Hat status page

Similar Red Hat incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 2 h 32 min

    Quay.io Push & Pulls Returning Intermittent 500 Issues

  2. , resolved after 19 h 41 min

    Initial: Quay.io Push/Pull Degraded

  3. , resolved after 3 days

    Intermittent HTTP 504 for registry.redhat.io and registry.connect.redhat.com

  4. , resolved after 18 h 29 min

    Intermittent pull failures in AU East

  5. , resolved after 8 h 55 min

    Quayio Is Facing Intermittent 500s Due to a Service Maintenance

Other recent Red Hat incidents

  1. access.redhat.com - Home & Community Outage

  2. access.redhat.com Community and Discussions

  3. Docs.redhat.com - Intermittent performance degradation

  4. access.redhat.com - Community and Discussions

  5. API errors

  6. Red Hat Lightspeed Compliance Degraded Performance

  7. Red Hat Connect Major Outage - Investigating

  8. access.redhat.com - Security Pages - CVE Outage

All recorded Red Hat incidents

Something wrong on this page?

A person reads every report. We fix our own mistakes - wording, mapping, a moved status page; the status itself always comes from Red Hat's official page. How we handle corrections.

Thanks - your report is on its way to us. We read every one.