Red Hat · Apps and SaaSJan 29, 2026, 18:59 UTC

quay.io & registry.redhat logins failing with RHSSO

MajorCapacityUpdated 1h ago

Jan 29, 18:59 UTCJan 29, 19:51 UTC

Duration

53m

Impact

Major

Root cause

Capacity

Red Hat, 90 days

32 incidents

Affected

APIregistry.redhat.ioregistry.access.redhat.comregistry.connect.redhat.comContainer Registries - registry.redhat.ioContainer Registries - registry.access.redhat.comContainer Registries - registry.connect.redhat.comQuay.io - API

Status page

Final update

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.

Timeline

Postmortem · Jun 18, 17:46 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.
Resolved · Jan 29, 19:51 UTC
We identified an issue related to rate limiting and have rolled out a fix that has restored service.
Investigating · Jan 29, 18:59 UTC
Users are facing login issues to Quay.io & registry.redhat with 403 errors.