Quay Outage History
Quay partial outage · 2 active incidents View live status →Pingoru has recorded 137 incidents for Quay: 131 in the last 12 months and 60 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 4 | 320 of 720 (44%) |
| May 2026 | 6 | 93 of 744 (12%) |
| June 2026 | 9 | 257 of 720 (36%) |
| July 2026 | 15 | 334 of 744 (45%) |
| August 2026 | 8 | 465 of 744 (63%) |
| September 2026 | 21 | 580 of 720 (80%) |
| October 2026 | 29 | 375 of 592 (63%) |
Incidents, newest first
Minor May 28, 2026 PQC key exchanges on Entitlement Network 5d 2h subscription.rhsm.redhat.com, cdn.redhat.com
Started May 28, 2026, 01:54 PM UTC· resolved Jun 02, 2026, 04:00 PM UTC
- scheduled May 28, 2026, 01:54 PM UTC
PQC key exchanges will be enabled for cdn.redhat.com and subscription.rhsm.redhat.com. We expect this change to be transparent to end users with no outage. For more information please see https://access.redhat.com/articles/7139604
- completed Jun 02, 2026, 04:00 PM UTC
The scheduled maintenance has been completed.
Notice May 27, 2026 Hybrid Cloud Console - Export-Service 4h 19m Red Hat Lightspeed - Export-Service
Started May 27, 2026, 12:30 PM UTC· resolved May 27, 2026, 04:49 PM UTC
- scheduled May 27, 2026, 12:30 PM UTC
The Red Hat Hybrid Cloud Console will undergo routine maintenance for the Export-Service starting on Wednesday, May 27, 2026, at 2 PM UTC (10 AM ET). The updates are expected to last approximately 4 hours. During this maintenance window, the Export-Service application will still be available.
- completed May 27, 2026, 04:49 PM UTC
The scheduled maintenance has been completed.
Major May 9, 2026 Quay.io Intermittent HTTP 502 on Pull/Push 18m
Started May 09, 2026, 07:30 PM UTC· resolved May 09, 2026, 07:48 PM UTC
- resolved May 11, 2026, 02:12 PM UTC
For a period of 12 minutes (15:52–16:04 UTC), ~62% of manifest pulls and ~39% of manifest pushes failed with 502s. Quota insights has temporarily been disabled as part of remediation.
- postmortem May 15, 2026, 05:11 PM UTC
On May 9, a surge of concurrent automated image pushes caused database lock contention that degraded Quay.io for approximately 18 minutes. Both image pushes and pulls returned errors during this window. The team identified and disabled an internal feature that amplified the contention, restoring service. We are redesigning this feature to operate asynchronously and improving our database locking mechanisms to better handle high-concurrency traffic.
Critical May 7, 2026 Quay.io HTTP 502 on Pull/Push 3h 4m API, Registry
Started May 07, 2026, 06:05 PM UTC· resolved May 07, 2026, 09:10 PM UTC
- investigating May 07, 2026, 06:05 PM UTC
We are currently investigating this issue.
- investigating May 07, 2026, 06:20 PM UTC
Pulls have been restored. Pushes are unavailable while we continue to investigate.
- identified May 07, 2026, 08:06 PM UTC
We have identified the issue as caused by a recent deployment. Our team has reverted the deployment, and are gradually rolling back traffic to our primary region to re-enable pushes while monitoring.
- monitoring May 07, 2026, 08:34 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 07, 2026, 08:44 PM UTC
We are continuing to monitor for any further issues.
- resolved May 07, 2026, 09:10 PM UTC
This incident has been resolved.
- postmortem May 15, 2026, 05:12 PM UTC
On May 7, a production deployment introduced a database locking conflict that caused Quay.io to become unhealthy. Image pulls were intermittently degraded for approximately 30 minutes and image pushes were unavailable for approximately 3 hours. The team failed over to a secondary region to restore pulls, then reverted the deployment to fully restore service. We are implementing multi-phase deployment rollouts, stricter canary processes, and health probe improvements to prevent recurrence.
Major May 5, 2026 cert-api.access.redhat.com outage 3h 5m Red Hat Lightspeed - Advisor, Red Hat Lightspeed - Compliance, Red Hat Lightspeed - Malware Detection, Red Hat Lightspeed - Patch and 4 more
Started May 05, 2026, 12:28 PM UTC· resolved May 05, 2026, 03:33 PM UTC
- investigating May 05, 2026, 12:28 PM UTC
We are currently investigating an issue where certificate-based requests to cert-api.access.redhat.com are returning HTTP 500 errors due to a gateway configuration mismatch. This is impacting Red Hat Lightspeed registrations and data uploads for both direct and Satellite-connected hosts.
- monitoring May 05, 2026, 01:55 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 05, 2026, 03:33 PM UTC
This incident has been resolved.
Minor April 20, 2026 Migration of china.cdn.redhat.com providers 6h 22m cdn.redhat.com
Started Apr 20, 2026, 02:37 PM UTC· resolved Apr 20, 2026, 09:00 PM UTC
- scheduled Apr 20, 2026, 02:37 PM UTC
Our CDN provider is ceasing operations of its delivery network inside China which requires us to perform a migration for china.cdn.redhat.com. This migration should be seamless for most end users in both access and performance. If you experience issues after this migration has completed, please reach out to Red Hat Support for assistance. This change has no effect on our other CDN properties.
- completed Apr 20, 2026, 09:00 PM UTC
The scheduled maintenance has been completed.
Major April 9, 2026 Erraneous Advisory email notifications 16s Red Hat Lightspeed - Patch
Started Apr 09, 2026, 05:10 PM UTC· resolved Apr 09, 2026, 05:10 PM UTC
- monitoring Apr 09, 2026, 05:10 PM UTC
On April 8th, 2026 an update to the Patch application caused Advisory notifications to be sent excessively and without any advisories listed. Within two hours of notification we were able to resolve the issue in production. Emails may be still be delivered due to delays in email delivery, but new erroneous emails are no longer being generated.
- resolved Apr 09, 2026, 05:10 PM UTC
This incident has been resolved.
Notice April 3, 2026 Subscription threshold exceeded notifications for non-Pay as you go products are showing misleading values 13d Subscription Watch
Started Apr 03, 2026, 02:04 PM UTC· resolved Apr 16, 2026, 02:33 PM UTC
- identified Apr 03, 2026, 02:04 PM UTC
Backend service responsible of checking over usage condition is processing the wrong data for non-PAYGO products. This is leading to unexpected subscription threshold exceeded notifications with misleading values.
- identified Apr 03, 2026, 02:34 PM UTC
We want customers to know that the notifications capability within Subscription Watch is currently turned off due to over usage notifications being sent out in error. Jira issue is https://redhat.atlassian.net/browse/SWATCH-4870
- resolved Apr 16, 2026, 02:33 PM UTC
The notifications for non-payg should work correctly.
Major March 30, 2026 quay.io API failures 3h 4m Registry Account Management, API, registry.redhat.io, registry.access.redhat.com and 3 more
Started Mar 30, 2026, 08:11 PM UTC· resolved Mar 30, 2026, 11:15 PM UTC
- identified Mar 30, 2026, 08:11 PM UTC
We are seeing 502s with quay.io pushes & pulls
- identified Mar 30, 2026, 08:58 PM UTC
The team has identified the issue and is investigating. We've shifted Quay to be read-only now so pulls should gradually begin restoring but pushes will still fail.
- monitoring Mar 30, 2026, 11:03 PM UTC
We've implemented a fix for the issue, pushes have been restored now.
- resolved Mar 30, 2026, 11:15 PM UTC
Quay.io functionality has been restored.
- postmortem Apr 20, 2026, 02:42 PM UTC
On March 30, 2026, Quay.io experienced a service disruption affecting image pulls and pushes, caused by an unexpected burst of resource-intensive operations that temporarily overloaded our primary database. Our engineering team mitigated the issue by failing over read traffic, restoring image pull capabilities within 45 minutes, and subsequently restored full push functionality once the database stabilized. We have since implemented enhanced traffic filtering and are actively optimizing our systems to prevent this from happening in the future.
Minor March 12, 2026 access.redhat.com - SSO Timeouts 22m SSO Authentication
Started Mar 12, 2026, 08:16 PM UTC· resolved Mar 12, 2026, 08:39 PM UTC
- identified Mar 12, 2026, 08:16 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Mar 12, 2026, 08:39 PM UTC
This incident has been resolved.
Major March 10, 2026 Intermittent issues with RHEL 9 and RHUI downloads 7d 21h cdn.redhat.com
Started Mar 10, 2026, 05:03 PM UTC· resolved Mar 18, 2026, 02:36 PM UTC
- identified Mar 10, 2026, 05:03 PM UTC
Update: Incident Reopened We are seeing a recurrence of the intermittent failures previously reported at https://status.redhat.com/incidents/6yxp7syh0z9v. Red Hat has confirmed intermittent failures when users attempt to download specific packages in Red Hat Enterprise Linux 9. The RHEL team is investigating. This was originally reported as "RHEL 9 AppStream repository synchronization on Red Hat Satellite 6 fails with duplicate key value error" in this public Knowledge Base: https://access.redhat.com/solutions/7139264. Red Hat Update Infrastructure (RHUI) has also been identified as impacted by this issue.
- resolved Mar 18, 2026, 02:36 PM UTC
This incident has been resolved.
Critical March 9, 2026 Red Hat Jira (issues.redhat.com) scheduled maintenance 6d 17h
Started Mar 09, 2026, 10:16 AM UTC· resolved Mar 16, 2026, 04:00 AM UTC
- scheduled Mar 09, 2026, 10:16 AM UTC
Red Hat Jira (issues.redhat.com) will be unavailable from 5 PM EDT on March 13 to 12 AM EDT on March 16 due to the migration to Atlassian Cloud
- in progress Mar 14, 2026, 01:10 PM UTC
Scheduled maintenance is currently in progress. We will provide updates as necessary.
- completed Mar 16, 2026, 04:00 AM UTC
The scheduled maintenance has been completed.
Notice March 2, 2026 AWS Outage: me-south 192d 10h OpenShift Cluster Manager
Started Mar 02, 2026, 07:22 AM UTC· resolved Sep 10, 2026, 06:08 PM UTC
- identified Mar 02, 2026, 07:22 AM UTC
ROSA clusters degraded in me-south due to a localized power issue in mes1-az2. Customers are advised to schedule their workloads into another availability zone. AWS Status Page: https://health.aws.amazon.com/health/status
- identified Mar 02, 2026, 05:52 PM UTC
ROSA clusters deployed in me-south-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 Mar 04, 2026, 04:44 AM UTC
The outage is still ongoing on the AWS side, and recovery efforts are ongoing. AWS is recommending customers launch replacement resources in one of the unaffected Availability Zones or an alternate AWS Region
Notice March 1, 2026 AWS Outage: me-central 205d 3h OpenShift Cluster Manager
Started Mar 01, 2026, 02:02 PM UTC· resolved Sep 22, 2026, 05:55 PM UTC
- identified Mar 01, 2026, 02:02 PM UTC
ROSA clusters degraded in me-central AWS Status Page: https://health.aws.amazon.com/health/status
- identified Mar 01, 2026, 02:26 PM UTC
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 Mar 02, 2026, 01:37 PM UTC
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 Mar 02, 2026, 05:52 PM UTC
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 Mar 03, 2026, 10:21 AM UTC
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 Mar 04, 2026, 04:55 AM UTC
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
Minor February 18, 2026 quay.io intermittent API failures 49m API, Registry
Started Feb 18, 2026, 08:51 PM UTC· resolved Feb 18, 2026, 09:40 PM UTC
- identified Feb 18, 2026, 08:51 PM UTC
We are observing an increase in 500s on pulls and pushes, the team is current investigating.
- monitoring Feb 18, 2026, 09:16 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 18, 2026, 09:40 PM UTC
Incident has been resolved and service is restored
- postmortem Feb 26, 2026, 06:02 PM UTC
This incident was caused by a database change which was improperly rolled out. Quay engineers were deploying an update which dropped a no longer utilized table, however, this was deployed all at once rather than in phases. That meant that our existing deployment began crashing once the table was dropped, causing API failures since the table was being queried with every request to the API. The SRE team had to manually scale down the old deployment to allow the newer one to progress which restored API functionality. Going forward we are reviewing our process for database migrations and implementing additional checks to ensure that these migrations happen in two steps: application update first and database migrations second.
Major February 10, 2026 Hybrid Cloud Console Notifications partial outage 6h Red Hat Lightspeed - Notifications
Started Feb 10, 2026, 10:29 AM UTC· resolved Feb 10, 2026, 04:29 PM UTC
- investigating Feb 10, 2026, 10:29 AM UTC
We are investigating a partial outage with the Hybrid Cloud Console Notifications service. All notifications sent by email or to Event-Driven Ansible, Google Chat, Microsoft Teams, PagerDuty, ServiceNow, Slack, Splunk, webhooks are currently interrupted. The Notifications UI remains operational. Our team is working to resolve this and will provide updates as they become available.
- investigating Feb 10, 2026, 01:45 PM UTC
All notifications - including Email, Event-Driven Ansible, Google Chat, Microsoft Teams, PagerDuty, ServiceNow, Slack, Splunk and Webhook - have been restored to normal operation. Notifications from 09:22 UTC (03:22 ET) – 13:28 UTC (07:28 ET): These messages were delayed but have now been successfully delivered. Notifications from 09:02 UTC (03:02 ET) – 09:21 UTC (03:21 ET): Our team is still working to resolve an issue affecting delivery for this specific timeframe. We will provide a final update once the remaining gap is addressed.
- resolved Feb 10, 2026, 04:29 PM UTC
This incident has been resolved.
Critical February 9, 2026 Quay.io UI Could Not Be Loaded 41m Frontend
Started Feb 09, 2026, 09:43 PM UTC· resolved Feb 09, 2026, 10:24 PM UTC
- investigating Feb 09, 2026, 09:43 PM UTC
We are currently investigating this issue.
- identified Feb 09, 2026, 10:01 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Feb 09, 2026, 10:11 PM UTC
An issue was identified with a recent production deploy. We have reverted the change and initiated a new deploy. The changes are rolling out now and we have observed a decrease in failures.
- resolved Feb 09, 2026, 10:24 PM UTC
This incident has been resolved.
- postmortem Jun 18, 2026, 05:41 PM UTC
On February 9, 2026, a frontend routing regression caused the legacy Quay.io UI to become temporarily inaccessible for roughly 45 minutes, though all backend APIs and image pulls remained fully operational. We restored access by deploying a fix to the routing configuration. Moving forward, we are strengthening our deployment procedures by requiring staging validations and integrating automated UI tests into our release pipeline to catch similar regressions before they reach production.
Major February 5, 2026 ROSA [Classic & HCP] Y-Stream Upgrades Blocked 8h 27m OpenShift Cluster Manager
Started Feb 05, 2026, 03:41 AM UTC· resolved Feb 05, 2026, 12:08 PM UTC
- investigating Feb 05, 2026, 03:41 AM UTC
We are currently investigating an issue where ROSA Classic and HCP clusters cannot schedule Y-Stream upgrades. Our team is working to resolve this and will provide updates as they become available. Note: Any Y-Stream upgrades already scheduled will be run.
- resolved Feb 05, 2026, 12:08 PM UTC
This incident has been resolved.
Critical February 4, 2026 Customer Portal Downloads Timeouts 13h 13m Downloads
Started Feb 04, 2026, 12:13 AM UTC· resolved Feb 04, 2026, 01:26 PM UTC
- investigating Feb 04, 2026, 12:13 AM UTC
We're experiencing latency issues with a download service used by the Downloads portion of the Customer Portal. Pages may fail to load while that service is triaged.
- resolved Feb 04, 2026, 01:26 PM UTC
This incident has been resolved.
Major January 30, 2026 DNS issues with registries 40m registry.access.redhat.com, registry.connect.redhat.com
Started Jan 30, 2026, 07:12 AM UTC· resolved Jan 30, 2026, 07:53 AM UTC
- identified Jan 30, 2026, 07:12 AM UTC
We have identified an issue affecting DNS resolution for registry.access.redhat.com and registry.connect.redhat.com. We are applying remediation to resolve it.
- resolved Jan 30, 2026, 07:53 AM UTC
This incident has been resolved.
Major January 29, 2026 quay.io & registry.redhat logins failing with RHSSO 52m API, registry.redhat.io, registry.access.redhat.com, registry.connect.redhat.com
Started Jan 29, 2026, 06:59 PM UTC· resolved Jan 29, 2026, 07:51 PM UTC
- investigating Jan 29, 2026, 06:59 PM UTC
Users are facing login issues to Quay.io & registry.redhat with 403 errors.
- resolved Jan 29, 2026, 07:51 PM UTC
We identified an issue related to rate limiting and have rolled out a fix that has restored service.
- postmortem Jun 18, 2026, 05:46 PM UTC
On January 29, 2026, Quay.io and Registry Proxy experienced a partial outage that caused approximately 50% of image pulls to fail and blocked new user logins. The failure occurred during a migration to a new cluster whose egress IPs had not been added to the RHSSO allowlist, which triggered automatic rate-limiting and blocked the authentication requests. Service was quickly restored by temporarily routing traffic back to the legacy cluster, and the team is implementing better rate limiting and authentication alerting to prevent a recurrence.
Critical January 28, 2026 Entitlement Network Outage 3h 1m
Started Jan 28, 2026, 12:23 PM UTC· resolved Jan 28, 2026, 03:25 PM UTC
- investigating Jan 28, 2026, 12:23 PM UTC
We are investigating an outage with the Entitlement Network (subscription.rhsm.redhat.com).
- identified Jan 28, 2026, 12:29 PM UTC
The issue has been identified and a fix is being implemented.
- identified Jan 28, 2026, 01:21 PM UTC
We're continuing to work on an issue with a backend service we rely on.
- monitoring Jan 28, 2026, 02:48 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 28, 2026, 03:25 PM UTC
This incident has been resolved.
Major January 22, 2026 Catalog outage 54m Catalog App
Started Jan 22, 2026, 09:07 PM UTC· resolved Jan 22, 2026, 10:02 PM UTC
- investigating Jan 22, 2026, 09:07 PM UTC
Catalog outage
- investigating Jan 22, 2026, 09:09 PM UTC
We are currently investigating issues with catalog.redhat.com.
- identified Jan 22, 2026, 09:58 PM UTC
We have identified a potential fix.
- resolved Jan 22, 2026, 10:02 PM UTC
A fix has been implemented and everything is appearing functional.
Notice January 20, 2026 Ecosystem Catalog Detail Pages 15h 58m Catalog App
Started Jan 20, 2026, 10:13 PM UTC· resolved Jan 21, 2026, 02:11 PM UTC
- investigating Jan 20, 2026, 10:13 PM UTC
Certain detail pages will 404 due to API issues.
- resolved Jan 21, 2026, 02:11 PM UTC
This incident has been resolved.
Minor January 15, 2026 Subscriptions Usage Database Maintenance 7d 4h Subscription Watch
Started Jan 15, 2026, 03:40 PM UTC· resolved Jan 22, 2026, 08:00 PM UTC
- scheduled Jan 15, 2026, 03:40 PM UTC
There will be scheduled maintenance for the Subscriptions Usage service from 22 Jan 2026 from 15:00 to 20:00 UTC. During this time, the Subscriptions Usage service may be unavailable. This maintenance will not affect the processing of usage data for the Subscriptions Usage service.
- completed Jan 22, 2026, 08:00 PM UTC
The scheduled maintenance has been completed.