Quay incident

quay.io & registry.redhat logins failing with RHSSO

Major Resolved View vendor source →

Quay experienced a major incident on January 29, 2026 affecting API and registry.redhat.io and 1 more component, lasting 52m. The incident has been resolved; the full update timeline is below.

Started
Jan 29, 2026, 06:59 PM UTC
Resolved
Jan 29, 2026, 07:51 PM UTC
Duration
52m
Detected by Pingoru
Jan 29, 2026, 06:59 PM UTC

Affected components

APIregistry.redhat.ioregistry.access.redhat.comregistry.connect.redhat.com

Update timeline

  1. investigating Jan 29, 2026, 06:59 PM UTC

    Users are facing login issues to Quay.io & registry.redhat with 403 errors.

  2. resolved Jan 29, 2026, 07:51 PM UTC

    We identified an issue related to rate limiting and have rolled out a fix that has restored service.

  3. postmortem Jun 18, 2026, 05:46 PM UTC

    On January 29, 2026, Quay.io and Registry Proxy experienced a partial outage that caused approximately 50% of image pulls to fail and blocked new user logins. The failure occurred during a migration to a new cluster whose egress IPs had not been added to the RHSSO allowlist, which triggered automatic rate-limiting and blocked the authentication requests. Service was quickly restored by temporarily routing traffic back to the legacy cluster, and the team is implementing better rate limiting and authentication alerting to prevent a recurrence.