Red Hat

Affected: Registry

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 18:42 UTC

   Users in Australia are observing pull issues with the Quay.io CDN.

2. monitoring 2026-10-21 02:50 UTC

   A fix has been implemented. We are monitoring to ensure no further issues.

3. resolved 2026-10-21 13:12 UTC

   No failures were reported after the fix.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Content

1. investigating 2026-10-19 16:19 UTC

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

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Content

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-14 06:02 UTC

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

2. resolved 2026-10-14 13:04 UTC

   Prod is stable now

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: API Manager

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-10-10 08:07 UTC

   Over the past several hours, the API Manager component of Red Hat 3scale API Management experienced intermittent periods of increased latency. The issue has been resolved, and the service is now stable and operating normally.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: registry.redhat.io, registry.access.redhat.com, Registry, registry.connect.redhat.com

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-05 17:13 UTC

   Quay.io is returning intermittent 500 issues on pushes as well as pulls due to high upload traffic, we are currently investigating to resolve this issue.

2. monitoring 2026-10-05 17:43 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-10-05 19:45 UTC

   A fix has been deployed and we no longer observe 5XX responses.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Red Hat Lightspeed - Notifications

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-01 15:24 UTC

   We are aware of an ongoing issue where users may receive daily digest emails, from within their organization, that they are not subscribed to. We are currently investigating. All Notifications services remain up, and continue to deliver notifications as per usual.

2. resolved 2026-10-01 19:25 UTC

   We've released a fix to the Notifications service which resolves this issue.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Partner Container Certification Workflow, Partner Acceleration Desk, Partner Account Management, Partner Portal, Partner Subscriptions

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-25 05:01 UTC

   We are currently experiencing an outage affecting the Red Hat Partner Connect. Our teams are actively investigating the issue and working to restore full functionality as soon as possible. We apologize for any inconvenience and appreciate your patience. Updates will be provided...

2. investigating 2026-09-25 05:02 UTC

   We are currently investigating this issue.

3. resolved 2026-09-25 05:22 UTC

   Issue has resolved Hydra has updated the certificates which caused our outage in the partner portal. we have updated the certificates configs in our application in alignment to it.

4. postmortem 2026-09-25 05:25 UTC

   Executive Summary A certificate update by the backend team triggered automated system alerts this morning. The Partner Certification Team investigated the alerts and identified the undocumented certificate rotation as the root cause of the incident. Detection & Investigation:...

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Catalog App

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-14 22:10 UTC

   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.

2. investigating 2026-09-14 22:10 UTC

   We are continuing to investigate this issue.

3. resolved 2026-09-15 08:49 UTC

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

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: API, Registry, Security Scanning

Failure mode: A schema or data migration caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-14 13:34 UTC

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

2. investigating 2026-09-14 14:02 UTC

   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

3. identified 2026-09-14 14:04 UTC

   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

4. identified 2026-09-14 14:08 UTC

   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

5. identified 2026-09-14 15:35 UTC

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

6. identified 2026-09-14 19:33 UTC

   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.

7. identified 2026-09-15 00:39 UTC

   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.

8. identified 2026-09-15 02:49 UTC

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

9. monitoring 2026-09-15 04:05 UTC

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

10. monitoring 2026-09-15 04:31 UTC

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

11. monitoring 2026-09-15 08:47 UTC

    Registry is operational, security scanning is under maintenance.

12. resolved 2026-09-15 09:15 UTC

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

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Ask

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-31 17:31 UTC

   We are experiencing intermittent performance issues on access.redhat.com/ask. Some users may see slow page loads or pages that fail to load. We are currently investigating the issue.

2. resolved 2026-08-31 17:47 UTC

   Resolved outage due to connection issue after database patching.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Catalog App, Search, Search, Search, Search, Search, Support Cases

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-18 22:33 UTC

   We are currently investigating intermittent search performance issues across access.redhat.com, developers.redhat.com, catalog.redhat.com, connect.redhat.com, and support cases. Users may experience slow query loads, timeouts, or search failures while using these platforms. Our...

2. resolved 2026-08-19 03:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Search, Search, Search, Search

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-18 15:45 UTC

   All search functionality is currently degraded. Searches may take longer to run or fail.

2. investigating 2026-08-18 15:51 UTC

   We are currently investigating intermittent search performance issues across access.redhat.com, developers.redhat.com, catalog.redhat.com, connect.redhat.com, and support cases. Users may experience slow query loads, timeouts, or search failures while using these platforms. Our...

3. resolved 2026-08-18 18:32 UTC

   All search functionality has been restored.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: SSO Authentication, OpenShift Cluster Manager, SSO Authentication, Subscription Management API

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-12 13:12 UTC

   We are aware of an issue with Offline Tokens on sso.redhat.com that may impact ROSA, OCM, Ansible Automation Hub, and RHSM API.

2. resolved 2026-08-12 16:11 UTC

   The incident has been mitigated . Our the team will continue working on the root cause analysis (RCA).

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: API Manager

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-28 12:47 UTC

   The Red Hat 3scale Site Reliability Engineering team is conducting a root cause analysis and taking corrective actions. Updates and additional information will be provided as soon as they become available, and efforts will continue until full resolution is achieved.

2. resolved 2026-07-29 08:20 UTC

   Scheduled database maintenance from 12:47:40 UTC to 12:50:59 UTC.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: API Manager

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-28 12:47 UTC

   The Red Hat 3scale Site Reliability Engineering team is conducting a root cause analysis and taking corrective actions. Updates and additional information will be provided as soon as they become available, and efforts will continue until full resolution is achieved.

2. resolved 2026-07-29 08:20 UTC

   Scheduled database maintenance from 12:47:40 UTC to 12:50:59 UTC.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Search

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-22 03:55 UTC

   We are currently investigating this issue.

2. resolved 2026-07-22 04:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Catalog App, Homepage, Homepage, Partner Portal, Homepage

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-18 00:17 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-18 00:46 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-07-18 03:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: registry.redhat.io, registry.connect.redhat.com

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-17 17:47 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-17 18:43 UTC

   We have identified a small disruption to registry pull operations (< 0.014%) during a cluster upgrade. Cluster upgrade is expected to finish within the next 2 hours. We will continue to monitor the issue during this time.

3. resolved 2026-07-21 00:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-17 13:29 UTC

   We are experiencing an outage of Ask Red Hat at access.redhat.com/ask and integration points across the Red Hat digital experiences. We are currently investigating the issue.

2. resolved 2026-07-17 13:55 UTC

   The incident is now resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Catalog App, Homepage, Partner Portal, Homepage

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-17 12:44 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-17 13:08 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2026-07-17 13:14 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-07-17 13:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Product Hub

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-07-16 19:26 UTC

   We have identified the cause of the intermittent performance issues affecting docs.redhat.com and are implementing changes. Web pages may continue to load slowly or fail intermittently while we work to restore performance.

2. resolved 2026-07-16 22:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Catalog App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-10 23:22 UTC

   Partner achievement and areas of expertise data may not display correctly on partner pages. The team is working on a fix.

2. identified 2026-07-11 11:28 UTC

   Partner achievement and areas of expertise data may not display correctly on partner pages. The team is working on a fix.

3. resolved 2026-07-11 14:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Catalog App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-10 14:18 UTC

   Partner achievement and areas of expertise data may not display correctly on partner pages. The team is working on a fix.

2. resolved 2026-07-10 17:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Partner Portal

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-07-09 22:18 UTC

   We have identified the root cause of the issue and are actively working on implementing a fix. We will provide further updates as progress is made.

2. resolved 2026-07-10 02:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: OpenShift Update Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-07 15:18 UTC

   api.openshift.com is down. This is under investigation.

2. investigating 2026-07-07 15:21 UTC

   api.openshift.com is degraded. We are investigating.

3. resolved 2026-07-07 15:46 UTC

   api.openshift.com issue is resolved and is now available.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Red Hat Lightspeed - Notifications

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-06 17:07 UTC

   We are currently investigating issues with the notification service. At this time, notifications for Red Hat Lightspeed and OpenShift Cluster Manager are delayed.

2. resolved 2026-07-06 17:32 UTC

   This issue has been resolved. Notifications are now being sent correctly.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Support Cases

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-12 08:56 UTC

   An outage has been detected on access.redhat.com the homepage. This outage currently impacts knowledge base and solutions on access.redhat.com. We are currently working to restore functionality.

2. resolved 2026-06-12 08:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Catalog App

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-09 14:32 UTC

   Some users may experience errors when accessing certain pages on catalog.redhat.com. The issue has been identified and the team is working on a resolution.

2. monitoring 2026-06-09 14:42 UTC

   A fix has been implemented and the service is recovering. We are continuing to monitor for stability.

3. resolved 2026-06-09 15:00 UTC

   Service is fully restored. The root cause was identified as an intermittent issue with a backend API serving hardware information.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Partner Container Certification Workflow, Partner Account Management, Partner Subscriptions

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-08 13:33 UTC

   We are investigating the incident

2. resolved 2026-06-08 16:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: repository.jboss.org

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-03 00:28 UTC

   The issue has been identified and a fix is being implemented.

2. resolved 2026-06-03 15:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: API, Build System, Registry, Frontend, Security Scanning

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-01 08:34 UTC

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

2. identified 2026-06-01 08:51 UTC

   registry.redhat.io and registry.access.redhat.com are also affected by this outage

3. investigating 2026-06-01 09:13 UTC

   We are currently investigating this issue.

4. identified 2026-06-01 10:22 UTC

   We have identified the issue and are actively working to resolve it.

5. monitoring 2026-06-01 10:25 UTC

   We have restored manifest pushes and are monitoring the environment for stability.

6. identified 2026-06-01 12:55 UTC

   We've issued a fix and working on restoring writes on Quay.io

7. monitoring 2026-06-01 13:24 UTC

   A fix has been implemented and we are currently monitoring the service

8. investigating 2026-06-01 14:24 UTC

   We are investigating this issue.

9. investigating 2026-06-01 15:54 UTC

   Pushes have been disabled while we work to identify a root cause. Pulls are available.

10. identified 2026-06-01 20:23 UTC

    Push functionality has been restored for most quay.io traffic. Some traffic remains in read-only mode as recovery efforts continue

11. monitoring 2026-06-01 21:39 UTC

    Image pushes have been restored. We are monitoring for recurrence. Security scanning will temporarily be unavailable.

12. resolved 2026-06-02 02:17 UTC

    The service has been restored and is operating normally.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-09 19:30 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.

2. postmortem 2026-05-15 17:11 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...

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: API, Registry

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-07 18:05 UTC

   We are currently investigating this issue.

2. investigating 2026-05-07 18:20 UTC

   Pulls have been restored. Pushes are unavailable while we continue to investigate.

3. identified 2026-05-07 20:06 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.

4. monitoring 2026-05-07 20:34 UTC

   A fix has been implemented and we are monitoring the results.

5. monitoring 2026-05-07 20:44 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-05-07 21:10 UTC

   This incident has been resolved.

7. postmortem 2026-05-15 17:12 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...

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Red Hat Lightspeed - Advisor, Red Hat Lightspeed - Compliance, Red Hat Lightspeed - Inventory, Red Hat Lightspeed - Malware Detection, Red Hat Lightspeed - Patch, Red Hat Lightspeed - Remediations, Red Hat Lightspeed - Resource Optimization, Red Hat Lightspeed - Vulnerability

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-05 12:28 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...

2. monitoring 2026-05-05 13:55 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-05-05 15:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: API

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-21 22:50 UTC

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

2. identified 2026-04-21 22:55 UTC

   Pull API is working again. We are actively working on bringing push API back online.

3. resolved 2026-04-22 00:09 UTC

   Pull and Push APIs are fully up again. Service is working as expected.

4. postmortem 2026-05-15 17:18 UTC

   On April 21, a routine production deployment included a dependency upgrade that exposed a latent incompatibility, causing Quay.io application pods to crash on startup. Image pulls and pushes were fully unavailable for approximately 12 minutes before the team failed over to a...

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Red Hat Lightspeed - Patch

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-04-09 17:10 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...

2. resolved 2026-04-09 17:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Subscription Watch

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-03 14:04 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.

2. identified 2026-04-03 14:34 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

3. resolved 2026-04-16 14:33 UTC

   The notifications for non-payg should work correctly.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Registry Account Management, API, registry.redhat.io, registry.access.redhat.com, Registry, registry.connect.redhat.com, Frontend

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-30 20:11 UTC

   We are seeing 502s with quay.io pushes & pulls

2. identified 2026-03-30 20:58 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.

3. monitoring 2026-03-30 23:03 UTC

   We've implemented a fix for the issue, pushes have been restored now.

4. resolved 2026-03-30 23:15 UTC

   Quay.io functionality has been restored.

5. postmortem 2026-04-20 14:42 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,...

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: SSO Authentication

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-12 20:16 UTC

   The issue has been identified and a fix is being implemented.

2. resolved 2026-03-12 20:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: cdn.redhat.com

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-10 17:03 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....

2. resolved 2026-03-18 14:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: cdn.redhat.com

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-06 19:25 UTC

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

2. investigating 2026-03-07 00:38 UTC

   We are continuing to investigate this issue.

3. resolved 2026-03-09 15:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: API, Registry

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-02-18 20:51 UTC

   We are observing an increase in 500s on pulls and pushes, the team is current investigating.

2. monitoring 2026-02-18 21:16 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-02-18 21:40 UTC

   Incident has been resolved and service is restored

4. postmortem 2026-02-26 18:02 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...

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Red Hat Lightspeed - Notifications

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-10 10:29 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...

2. investigating 2026-02-10 13:45 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...

3. resolved 2026-02-10 16:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Frontend

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-09 21:43 UTC

   We are currently investigating this issue.

2. identified 2026-02-09 22:01 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-02-09 22:11 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.

4. resolved 2026-02-09 22:24 UTC

   This incident has been resolved.

5. postmortem 2026-06-18 17:41 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....

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: OpenShift Cluster Manager

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-05 03:41 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.

2. resolved 2026-02-05 12:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Downloads

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-04 00:13 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.

2. resolved 2026-02-04 13:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: registry.access.redhat.com, registry.connect.redhat.com

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-01-30 07:12 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.

2. resolved 2026-01-30 07:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: API, registry.redhat.io, registry.access.redhat.com, registry.connect.redhat.com

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-29 18:59 UTC

   Users are facing login issues to Quay.io & registry.redhat with 403 errors.

2. resolved 2026-01-29 19:51 UTC

   We identified an issue related to rate limiting and have rolled out a fix that has restored service.

3. postmortem 2026-06-18 17:46 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,...

Excerpts are shortened. Read the full incident on Red Hat's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-28 12:23 UTC

   We are investigating an outage with the Entitlement Network (subscription.rhsm.redhat.com).

2. identified 2026-01-28 12:29 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2026-01-28 13:21 UTC

   We're continuing to work on an issue with a backend service we rely on.

4. monitoring 2026-01-28 14:48 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2026-01-28 15:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Red Hat's status page.

Affected: Catalog App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-22 21:07 UTC

   Catalog outage

2. investigating 2026-01-22 21:09 UTC

   We are currently investigating issues with catalog.redhat.com.

3. identified 2026-01-22 21:58 UTC

   We have identified a potential fix.

4. resolved 2026-01-22 22:02 UTC

   A fix has been implemented and everything is appearing functional.

Excerpts are shortened. Read the full incident on Red Hat's status page.