# Red Hat (incl. Quay.io): quay.io & registry.redhat logins failing with RHSSO

- Impact (vendor’s label): major
- Status: postmortem
- Started: 2026-01-29 18:59 UTC · Resolved: 2026-01-29 19:51 UTC · Duration: 53 min
- Updates: 3 · Affected components: Container Registries - registry.connect.redhat.com, registry.connect.redhat.com, Container Registries - registry.redhat.io, registry.redhat.io, API, Quay.io - API, Container Registries - registry.access.redhat.com, registry.access.redhat.com
- [Vendor status page: https://stspg.io/2wr6jpzld20y](https://stspg.io/2wr6jpzld20y)
- [Company: Red Hat (incl. Quay.io)](https://rewindex.com/company/red-hat.md)

## Timeline of updates

- **investigating** 2026-01-29 18:59 UTC: Users are facing login issues to Quay.io & registry.redhat with 403 errors.
- **resolved** 2026-01-29 19:51 UTC: We identified an issue related to rate limiting and have rolled out a fix that has restored service.
- **postmortem** 2026-06-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.

## Rewindex changes for this incident

- 2026-01-29 18:59 UTC: [Major incident: quay.io & registry.redhat logins failing with RHSSO](https://rewindex.com/change/i9c1550f9d7c227.md)


---
Canonical: https://rewindex.com/company/red-hat/incidents/vhp326mcz67s · Markdown: https://rewindex.com/company/red-hat/incidents/vhp326mcz67s.md · JSON: https://rewindex.com/api/v1/companies/red-hat/incidents/vhp326mcz67s · Generated 2026-10-19T23:36:16.005Z