# Red Hat (incl. Quay.io): quay.io intermittent API failures

- Impact (vendor’s label): minor
- Status: postmortem
- Started: 2026-02-18 20:51 UTC · Resolved: 2026-02-18 21:40 UTC · Duration: 50 min
- Updates: 4 · Affected components: Quay.io - Registry, Registry, API, Quay.io - API
- [Vendor status page: https://stspg.io/77rnz2tz8992](https://stspg.io/77rnz2tz8992)
- [Company: Red Hat (incl. Quay.io)](https://rewindex.com/company/red-hat.md)

## Timeline of updates

- **identified** 2026-02-18 20:51 UTC: We are observing an increase in 500s on pulls and pushes, the team is current investigating.
- **monitoring** 2026-02-18 21:16 UTC: A fix has been implemented and we are monitoring the results.
- **resolved** 2026-02-18 21:40 UTC: Incident has been resolved and service is restored
- **postmortem** 2026-02-26 18:02 UTC: This incident was caused by a database change which was improperly rolled out. Quay engineers were deploying an update which dropped a no longer utilized table, however, this was deployed all at once rather than in phases. That meant that our existing deployment began crashing once the table was dropped, causing API failures since the table was being queried with every request to the API. The SRE team had to manually scale down the old deployment to allow the newer one to progress which restored API functionality. Going forward we are reviewing our process for database migrations and implementing additional checks to ensure that these migrations happen in two steps: application update first and database migrations second.


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