Quay.io Outage History

Quay.io's catalog.redhat.com experienced a 28-minute outage where users encountered errors when accessing certain pages. The root cause was identified as an intermittent issue with a backend API serving hardware information. The service was fully restored after implementing a fix and monitoring for stability.

Quay.io experienced a major outage affecting the Support Cases functionality on access.redhat.com. Users were unable to access support case services during the incident. The outage was resolved after 17 minutes of investigation and restoration efforts.

Quay.io experienced a major outage affecting connect.redhat.com that lasted approximately 3.1 hours. The incident was resolved after investigation and remediation efforts. No specific details about the root cause or affected functionality were provided in the incident report.

Quay.io experienced a major outage affecting the repository.jboss.org service that lasted 14.6 hours. The issue was identified and a fix was implemented to restore service. The incident has been fully resolved.

Quay.io experienced degraded performance affecting push and pull operations for container images, with the incident lasting 17.7 hours. During the outage, push functionality was temporarily disabled while pulls remained available, and related services registry.redhat.io and registry.access.redhat.com were also affected. The service was fully restored with push/pull operations returning to normal, though security scanning was temporarily unavailable during the recovery period.

Quay.io experienced HTTP 502 errors that prevented users from pulling and pushing container images, caused by a problematic deployment. The team identified the root cause, reverted the deployment, and gradually restored traffic to the primary region, with pulls restored first followed by pushes. The incident was fully resolved after 3.1 hours of service disruption.

A gateway configuration mismatch caused cert-api.access.redhat.com to return HTTP 500 errors for certificate-based requests, impacting Red Hat Lightspeed registrations and data uploads for both direct and Satellite-connected hosts. The issue was resolved after 3.1 hours by implementing a configuration fix.

Quay.io experienced degraded performance affecting both push and pull API operations for 1.4 hours. The pull API was restored first, followed by the push API being brought back online. The service was fully operational with both APIs working as expected by the end of the incident.

Quay.io's backend service processed incorrect data for non-Pay as you go products, causing users to receive erroneous subscription threshold exceeded notifications with misleading usage values. The notifications capability within Subscription Watch was temporarily disabled to prevent further incorrect alerts from being sent. The issue was resolved after 312.6 hours with notifications for non-PAYGO products now functioning correctly.