Struck in red is what Red Hat (incl. Quay.io) removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
AddedTitle#1
Before: not present
After: Quay.io UI Could Not Be Loaded
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: postmortem
AddedStart time#4
Before: not present
After: 2026-02-09 21:43 UTC
AddedResolved time#5
Before: not present
After: 2026-02-09 22:24 UTC
AddedAffected components#6
Before: not present
After: Frontend, Quay.io - Frontend
AddedUpdateinvestigating#7
Before: not present
After: We are currently investigating this issue.
AddedUpdateidentified#8
Before: not present
After: The issue has been identified and a fix is being implemented.
AddedUpdatemonitoring#9
Before: not present
After: 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.
AddedUpdateresolved#10
Before: not present
After: This incident has been resolved.
AddedUpdatepostmortem#11
Before: not present
After: 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 commits each version of an incident to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.