Resolved after 41 minutes, affecting Frontend, on February 9, 2026.
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.
Affected components
Update timeline
- investigating Feb 09, 2026, 09:43 PM UTC
We are currently investigating this issue.
- identified Feb 09, 2026, 10:01 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Feb 09, 2026, 10:11 PM 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 Feb 09, 2026, 10:24 PM UTC
This incident has been resolved.
- postmortem Jun 18, 2026, 05:41 PM 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.
Your product runs on more than Quay
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services