Red Hat 3scale Outage History
Uptime record, past incidents, and downtime history for Red Hat 3scale.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 0% | 15 | 15 |
| July 2026 | 0% | 31 | 31 |
| June 2026 | 0% | 30 | 30 |
| May 2026 | 0% | 15 | 15 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
May 17
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
August 2026
sso.redhat.com Offline Token Issue
Started: Aug 12, 1:12 PM
investigating
We are aware of an issue with Offline Tokens on sso.redhat.com that may impact ROSA, OCM, Ansible Automation Hub, and RHSM API.
Aug 12, 1:12 PM
July 2026
Red Hat 3scale API Management SaaS APIs are currently experiencing a service disruption
Started: Jul 28, 12:47 PM
investigating
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.
Jul 28, 12:47 PM
Red Hat 3scale API Management SaaS APIs are currently experiencing a service disruption
Started: Jul 28, 12:47 PM
investigating
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.
Jul 28, 12:47 PM
Search Outage - Developers.redhat.com and www.redhat.com
Started: Jul 22, 3:55 AM
investigating
We are currently investigating this issue.
Jul 22, 3:55 AM
Multiple Site Partial Outage
Started: Jul 18, 12:17 AM
monitoring
A fix has been implemented and we are monitoring the results.
Jul 18, 12:46 AM
investigating
We are currently investigating this issue.
Jul 18, 12:17 AM
Intermittent HTTP 504 for registry.redhat.io and registry.connect.redhat.com
Started: Jul 17, 5:47 PM
monitoring
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.
Jul 17, 6:43 PM
investigating
We are currently investigating this issue.
Jul 17, 5:47 PM
Ask Red Hat - Outage
Started: Jul 17, 1:29 PM
investigating
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.
Jul 17, 1:29 PM
Multiple Site Outage
Started: Jul 17, 12:44 PM
monitoring
We are continuing to monitor for any further issues.
Jul 17, 1:14 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jul 17, 1:08 PM
investigating
We are currently investigating this issue.
Jul 17, 12:44 PM
Docs.redhat.com - Outage Identified
Started: Jul 16, 7:26 PM
identified
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.
Jul 16, 7:26 PM
Ecosystem Catalog Partial Outage
Started: Jul 10, 11:22 PM
identified
Partner achievement and areas of expertise data may not display correctly on partner pages. The team is working on a fix.
Jul 11, 11:28 AM
identified
Partner achievement and areas of expertise data may not display correctly on partner pages. The team is working on a fix.
Jul 10, 11:22 PM
Ecosystem Catalog Partial Outage
Started: Jul 10, 2:18 PM
investigating
Partner achievement and areas of expertise data may not display correctly on partner pages. The team is working on a fix.
Jul 10, 2:18 PM
Partner Portal Outage
Started: Jul 9, 10:18 PM
identified
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.
Jul 9, 10:18 PM
api.openshift.com is down
Started: Jul 7, 3:18 PM
investigating
api.openshift.com is degraded. We are investigating.
Jul 7, 3:21 PM
investigating
api.openshift.com is down. This is under investigation.
Jul 7, 3:18 PM
Notification Service Disruption
Started: Jul 6, 5:07 PM
investigating
We are currently investigating issues with the notification service. At this time, notifications for Red Hat Lightspeed and OpenShift Cluster Manager are delayed.
Jul 6, 5:07 PM
June 2026
catalog.redhat.com - Outage
Started: Jun 9, 2:32 PM
monitoring
A fix has been implemented and the service is recovering. We are continuing to monitor for stability.
Jun 9, 2:42 PM
investigating
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.
Jun 9, 2:32 PM
Support Cases - Access.redhat.com Outage
Started: Jun 9, 10:22 AM
investigating
An outage has been detected on access.redhat.com for the Support Cases. We are currently working to restore functionality.
Jun 9, 10:22 AM
connect.redhat.com - Outage
Started: Jun 8, 1:32 PM
investigating
We are investigating the incident
Jun 8, 1:33 PM
repository.jboss.org - Outage
Started: Jun 3, 12:28 AM
identified
The issue has been identified and a fix is being implemented.
Jun 3, 12:28 AM
Quay.io Push/Pull Degraded
Started: Jun 1, 8:34 AM
monitoring
Image pushes have been restored. We are monitoring for recurrence. Security scanning will temporarily be unavailable.
Jun 1, 9:39 PM
identified
Push functionality has been restored for most quay.io traffic. Some traffic remains in read-only mode as recovery efforts continue
Jun 1, 8:23 PM
investigating
Pushes have been disabled while we work to identify a root cause. Pulls are available.
Jun 1, 3:54 PM
investigating
We are investigating this issue.
Jun 1, 2:24 PM
monitoring
A fix has been implemented and we are currently monitoring the service
Jun 1, 1:24 PM
identified
We've issued a fix and working on restoring writes on Quay.io
Jun 1, 12:55 PM
monitoring
We have restored manifest pushes and are monitoring the environment for stability.
Jun 1, 10:25 AM
identified
We have identified the issue and are actively working to resolve it.
Jun 1, 10:22 AM
investigating
We are currently investigating this issue.
Jun 1, 9:13 AM
identified
registry.redhat.io and registry.access.redhat.com are also affected by this outage
Jun 1, 8:51 AM
identified
We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.
Jun 1, 8:34 AM
May 2026
Quay.io HTTP 502 on Pull/Push
Started: May 7, 6:05 PM
monitoring
We are continuing to monitor for any further issues.
May 7, 8:44 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 7, 8:34 PM
identified
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.
May 7, 8:06 PM
investigating
Pulls have been restored. Pushes are unavailable while we continue to investigate.
May 7, 6:20 PM
investigating
We are currently investigating this issue.
May 7, 6:05 PM
cert-api.access.redhat.com outage
Started: May 5, 12:28 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 5, 1:55 PM
investigating
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.
May 5, 12:28 PM
April 2026
Quay.io Push/Pull Degraded
Started: Apr 21, 10:50 PM
identified
Pull API is working again. We are actively working on bringing push API back online.
Apr 21, 10:55 PM
investigating
We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.
Apr 21, 10:50 PM
Subscription threshold exceeded notifications for non-Pay as you go products are showing misleading values
Started: Apr 3, 2:04 PM
identified
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
Apr 3, 2:34 PM
identified
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.
Apr 3, 2:04 PM
March 2026
quay.io API failures
Started: Mar 30, 8:11 PM
identified
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.
Mar 30, 8:58 PM
identified
We are seeing 502s with quay.io pushes & pulls
Mar 30, 8:11 PM
AWS Outage: me-south
Started: Mar 2, 7:22 AM
OpenShift Cluster Manager
identified
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
Mar 4, 4:44 AM
identified
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.
Mar 2, 5:52 PM
identified
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
Mar 2, 7:22 AM
AWS Outage: me-central
Started: Mar 1, 2:02 PM
OpenShift Cluster Manager
identified
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
Mar 4, 4:55 AM
identified
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.
Mar 3, 10:21 AM
identified
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.
Mar 2, 5:52 PM
identified
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.
Mar 2, 1:37 PM
identified
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.
Mar 1, 2:26 PM
identified
ROSA clusters degraded in me-central
AWS Status Page: https://health.aws.amazon.com/health/status
Mar 1, 2:02 PM