Quay.io UI Could Not Be Loaded

Final update

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.

1. Postmortem · Jun 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.
2. Resolved · Feb 9, 22:24 UTC
   This incident has been resolved.
3. Monitoring · Feb 9, 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.
4. Identified · Feb 9, 22:01 UTC
   The issue has been identified and a fix is being implemented.
5. Investigating · Feb 9, 21:43 UTC
   We are currently investigating this issue.