ChangesRed Hat (incl. Quay.io)Initial: Quay.io Push/Pull Degraded
Red Hat (incl. Quay.io): Major incident: Initial: Quay.io Push/Pull Degraded
Summary
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what Red Hat (incl. Quay.io) removed; blue is what they added. Muted text is unchanged context.
Before: not present
After: Initial: Quay.io Push/Pull Degraded
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-09-14 13:34 UTC
Before: not present
After: 2026-09-15 09:15 UTC
Before: not present
After: API, Quay.io - API, Quay.io - Registry, Quay.io - Security Scanning, Registry, Security Scanning
Before: not present
After: We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.
Before: not present
After: We have identified the cause of the image pull failures and are implementing a fix. Image pushes may continue to fail while remediation is in progress
Before: not present
After: We have identified the cause of the image pull failures and are implementing a fix. Image pushes may continue to fail while remediation is in progress
Before: not present
After: We have identified the cause of the image push failures and are implementing a fix. Image pushes may continue to fail while remediation is in progress
Before: not present
After: Quay is in read-only mode. Only pulls are being served while we implement the fix.
Before: not present
After: We are continuing to apply the fix. Quay.io remains in read-only mode. Image pulls continue to work, but pushes and other write operations are temporarily unavailable. We will provide another update once the fix is complete.
Before: not present
After: We are continuing to apply the fix. 2 out of 3 affected tables have been updated. The final one is currently running. Quay.io remains in read-only mode. Image pulls continue to work, but pushes and other write operations are temporarily unavailable.
Before: not present
After: The affected database tables have been updated. We are working to restoring full read/write traffic. Quay.io remains in read-only mode.
Before: not present
After: The fix has been deployed. Quay.io is serving read/write requests. We are continuing to monitor the service
Before: not present
After: Image push and pull operations are functioning normally. We continue to monitor service health. Clair vulnerability scanning is temporarily disabled.
Before: not present
After: Registry is operational, security scanning is under maintenance.
Before: not present
After: Quay.io registry is operational since 15 Sep 2026, 5:00 AM UTC. Security scanning remains on maintenance until further notice.
During the incident, some write operations were failing. The registry was put into read-only mode to preserve data integrity. The underlying issue was related to database scaling and was resolved successfully without any data loss.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
Monday, September 14
1 incident change
- MajorMajor incident
Initial: Quay.io Push/Pull Degradedthis change
All Red Hat (incl. Quay.io) changesRed Hat (incl. Quay.io) profileMarkdownJSON