# Red Hat (incl. Quay.io): Quay.io UI Could Not Be Loaded

- Impact (vendor’s label): critical
- Status: postmortem
- Started: 2026-02-09 21:43 UTC · Resolved: 2026-02-09 22:24 UTC · Duration: 42 min
- Updates: 5 · Affected components: Frontend, Quay.io - Frontend
- [Vendor status page: https://stspg.io/6fz9dqh2n56j](https://stspg.io/6fz9dqh2n56j)
- [Company: Red Hat (incl. Quay.io)](https://rewindex.com/company/red-hat.md)

## Timeline of updates

- **investigating** 2026-02-09 21:43 UTC: We are currently investigating this issue.
- **identified** 2026-02-09 22:01 UTC: The issue has been identified and a fix is being implemented.
- **monitoring** 2026-02-09 22:11 UTC: An issue was identified with a recent production deploy. We have reverted the change and initiated a new deploy. The changes are rolling out now and we have observed a decrease in failures.
- **resolved** 2026-02-09 22:24 UTC: This incident has been resolved.
- **postmortem** 2026-06-18 17:41 UTC: On February 9, 2026, a frontend routing regression caused the legacy Quay.io UI to become temporarily inaccessible for roughly 45 minutes, though all backend APIs and image pulls remained fully operational. We restored access by deploying a fix to the routing configuration. Moving forward, we are strengthening our deployment procedures by requiring staging validations and integrating automated UI tests into our release pipeline to catch similar regressions before they reach production.

## Rewindex changes for this incident

- 2026-02-09 21:43 UTC: [Critical incident: Quay.io UI Could Not Be Loaded](https://rewindex.com/change/icef494b65f0294.md)


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