Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Quay.io Outage History

Every past Quay.io outage tracked by IsDown, with detection times, duration, and resolution details.

There were 250 Quay.io outages since December 2016. The 75 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor June 9, 2026

June 2026: catalog.redhat.com - Outage

Detected Jun 9, 2026 3:32 PM BST · Resolved Jun 9, 2026 4:00 PM BST · Duration 28 minutes

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.

Major June 9, 2026

June 2026: Support Cases - Access.redhat.com Outage

Detected Jun 9, 2026 11:22 AM BST · Resolved Jun 9, 2026 11:39 AM BST · Duration 17 minutes

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.

Major June 8, 2026

June 2026: connect.redhat.com - Outage

Detected Jun 8, 2026 2:32 PM BST · Resolved Jun 8, 2026 5:39 PM BST · Duration about 3 hours

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.

Major June 3, 2026

June 2026: repository.jboss.org - Outage

Detected Jun 3, 2026 1:28 AM BST · Resolved Jun 3, 2026 4:02 PM BST · Duration about 15 hours

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.

Major June 1, 2026

June 2026: Quay.io Push/Pull Degraded

Detected Jun 1, 2026 9:34 AM BST · Resolved Jun 2, 2026 3:18 AM BST · Duration about 18 hours

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.

Major May 7, 2026

May 2026: Quay.io HTTP 502 on Pull/Push

Detected May 7, 2026 7:05 PM BST · Resolved May 7, 2026 10:11 PM BST · Duration about 3 hours

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.

Major May 5, 2026

May 2026: cert-api.access.redhat.com outage

Detected May 5, 2026 1:28 PM BST · Resolved May 5, 2026 4:34 PM BST · Duration about 3 hours

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.

Major April 21, 2026

April 2026: Quay.io Push/Pull Degraded

Detected Apr 21, 2026 11:50 PM BST · Resolved Apr 22, 2026 1:10 AM BST · Duration about 1 hour

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.

Minor April 3, 2026

April 2026: Subscription threshold exceeded notifications for non-Pay as you go products are showing misleading values

Detected Apr 3, 2026 3:04 PM BST · Resolved Apr 16, 2026 3:38 PM BST · Duration 13 days

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.