Red Hat Status

Resolved: This issue has been resolved, and a fix has been successfully deployed.

Investigating: We are continuing to investigate this issue.

Investigating: We are experiencing intermittent performance issues on catalog.redhat.com detail pages. Some users may see slow page loads, timeouts, or pages that fail to load. We are currently investigating the issue.

Identified: AWS continues to make progress on recovery efforts across multiple workstreams. From now on, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center.

AWS Status Page: https://health.aws.amazon.com/health/status

Identified: The outage is still ongoing on AWS side. The AWS Management Console is now operational, and AWS is recommending to retry operations where possible, although most of the underlying service are still offline.

Identified: ROSA clusters deployed in me-central-1 are degraded due to availability zone outages. We recommend customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions, ideally in Europe. Please refer to AWS Health for more information and recommendations on workload relocation.

Identified: Availability Zones in the ME-CENTRAL-1 Region (mec1-az2, mec1-az3) have been impacted by a power outage. Customers are advised to schedule their workloads into another availability zone.

Identified: An Availability Zone in the ME-CENTRAL-1 Region (mec1-az2) has been impacted by a power outage. Customers are advised to schedule their workloads into another availability zone.

Identified: ROSA clusters degraded in me-central

AWS Status Page: https://health.aws.amazon.com/health/status

Resolved: 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.

Monitoring: Registry is operational, security scanning is under maintenance.

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

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

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

Identified: 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.

Identified: 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.

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

Identified: 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

Identified: 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

Investigating: 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

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

Resolved: 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.

Monitoring: Registry is operational, security scanning is under maintenance.

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

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

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

Identified: 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.

Identified: 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.

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

Identified: 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

Identified: 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

Investigating: 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

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