Daily provider-status observations and published incident history for Red Hat 3scale.
Component incident
Red Hat 3scale has an active component incident; no global outage is indicated. 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
Unable to generate an access token for the Partner User Loop API following the secret rotation. As a result, partner eligibility checks are failing for users attempting to log in.
We are updating our system certificates and keys. Expect brief service interruptions—you may need to re-authenticate, re-certify or check your permissions once complete.
A fix has been implemented and we are monitoring the results.
identified
Update - Due to a high volume of automated spam, posting new discussions and comments is temporarily suspended. Our team is actively implementing enhanced security measures and will restore full functionality as soon as possible.
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.
Due to a high volume of automated spam, posting new discussions and comments is temporarily suspended. Our team is implementing enhanced security measures and will restore full functionality as soon as possible.
Red Hat Lightspeed Compliance Degraded Performance
The lag in processing of messages is lowered from several hours to 5-20 minutes. The team is working on further improvements.
identified
Change in the code caused degraded performance of processing new inventory events in compliance component. Events can sit for a while in the queue.
Started at 2026-10-28 02:00:00 UTC and ongoing. Problematic parts were identified, first batch of remedy was deployed and the team had identified areas to improve and is addressing them in the meantime.
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 as more information becomes available.
Quayio Is Facing Intermittent 500s Due to a Service Maintenance
The CWE site is under maintenance which was causing the outage for the CVE pages. A banner has been added for the failing CWE data while allowing the CVE pages to load with the remaining content. We are currently monitoring the applied fix.
investigating
An outage has been detected for some CVEs in access.redhat.com - Security Pages. This outage currently impacts CVE information and suggested remediations on access.redhat.com. We are currently working to restore functionality.
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.
