Daily provider-status observations and published incident history for Red Hat 3scale.
Unknown
Current status for Red Hat 3scale cannot be verified right now. Verified .
Official provider source.
Looking for an update now? Check the current status, or follow Red Hat 3scale for future changes.
15.8%of 76 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
October 2026
12.9%
31
27
September 2026
21.4%
28
22
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Aug 17Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
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.
Pull performance from registry.redhat is degraded. The issue has been traced to a dependency service. We are awaiting the dependency team's investigation and next steps.
A fix has been implemented and we are monitoring the results.
investigating
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.
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.
Red Hat 3scale API Management SaaS APIs are currently experiencing a service disruption
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.
Red Hat 3scale API Management SaaS APIs are currently experiencing a service disruption
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.
Red Hat 3scale API Management SaaS APIs are currently experiencing a service disruption
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.
Red Hat 3scale API Management SaaS APIs are currently experiencing a service disruption
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.
Red Hat 3scale API Management SaaS APIs are currently experiencing a service disruption
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.
Legacy Incident Archive
26 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
June 2026
Quay.io Push/Pull Degraded
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Image pushes have been restored. We are monitoring for recurrence. Security scanning will temporarily be unavailable.
identified
Push functionality has been restored for most quay.io traffic. Some traffic remains in read-only mode as recovery efforts continue
investigating
Pushes have been disabled while we work to identify a root cause. Pulls are available.
investigating
We are investigating this issue.
monitoring
A fix has been implemented and we are currently monitoring the service
identified
We've issued a fix and working on restoring writes on Quay.io
monitoring
We have restored manifest pushes and are monitoring the environment for stability.
identified
We have identified the issue and are actively working to resolve it.
investigating
We are currently investigating this issue.
identified
registry.redhat.io and registry.access.redhat.com are also affected by this outage
identified
We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.
May 2026
Quay.io HTTP 502 on Pull/Push
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
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.
investigating
Pulls have been restored. Pushes are unavailable while we continue to investigate.
investigating
We are currently investigating this issue.
cert-api.access.redhat.com outage
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
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.
April 2026
Quay.io Push/Pull Degraded
majorSource not attested
Last archived state: resolved
View archived record details
identified
Pull API is working again. We are actively working on bringing push API back online.
investigating
We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.
Subscription threshold exceeded notifications for non-Pay as you go products are showing misleading values
minorSource not attested
Last archived state: resolved
View archived record details
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
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.
March 2026
quay.io API failures
majorSource not attested
Last archived state: resolved
View archived record details
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.
