Red Hat had 60 outages in the last 2 years totaling 985h 43m of downtime — averaging 2.5 incidents per month.
There were 60 Red Hat outages since August 19, 2025 totaling 985h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.
Ask Red Hat will undergo scheduled maintenance on Tuesday, 16 June 2026 between 06:30 - 09:30 UTC. During this time you may experience intermittent errors or slow response times. We appreciate your patience as we work to improve our platform.
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.
This incident has been resolved.
repository.jboss.org will go under maintenance to make storage improvements. During this time the repository will be unavailable.
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.
A fix has been implemented and the service is recovering. We are continuing to monitor for stability.
Service is fully restored. The root cause was identified as an intermittent issue with a backend API serving hardware information.
An outage has been detected on access.redhat.com for the Support Cases. We are currently working to restore functionality.
We are investigating the incident
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
There is a planned SFDC outage on DATE. SFDC will be completely inaccessible for 5 minutes. PLANNED START TIME 06:00 am CEST, June 06 | 12:00 am EDT | 04:00 am UTC PLANNED END TIME 06:05 am CET, June 06 | 12:05 am EDT | 4:05 am 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
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.
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.
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.
We are currently investigating this issue.
Pulls have been restored. Pushes are unavailable while we continue to investigate.
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.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
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.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
This incident has been resolved.
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.
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
The notifications for non-payg should work correctly.
We are seeing 502s with quay.io pushes & pulls
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.
We've implemented a fix for the issue, pushes have been restored now.
Quay.io functionality has been restored.
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.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
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.
This incident has been resolved.
We are observing an increase in 500s on pulls and pushes, the team is current investigating.
A fix has been implemented and we are monitoring the results.
Incident has been resolved and service is restored
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.
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.
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.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
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.
This incident has been resolved.
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.
This incident has been resolved.
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.
This incident has been resolved.