Initial: Quay.io Push/Pull Degraded

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.

Registry is operational, security scanning is under maintenance.

Image push and pull operations are functioning normally. We continue to monitor service health. Clair vulnerability scanning is temporarily disabled.

The fix has been deployed. Quay.io is serving read/write requests. We are continuing to monitor the service

The affected database tables have been updated. We are working to restoring full read/write traffic. Quay.io remains in read-only mode.

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.

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.

Quay is in read-only mode. Only pulls are being served while we implement the fix.

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

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

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

We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.