New Multi-region uptime checks and custom-domain status pages

Red Hat 3scale Outage History

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.

22.9% of 35 verified observed days had no reported provider issue

90-Day Trend

Jul 3Sep 30

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

Jul 2 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

September 2026
Red Hat Connect Major Outage - Investigating
major Observed active window 23m

View incident details and source

Started:

Partner Container Certification Workflow Partner Acceleration Desk Partner Account Management Partner Portal Partner Subscriptions
investigating
We are currently investigating this issue.
identified
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.
Support Cases - Post Upgrade Issues
minor

View incident details and source

Started:

Support Cases
investigating
We are aware of ongoing issues when accessing support cases after our CRM upgrade. We are actively working to resolve them. Try refreshing your browser first. If you still need help, contact us at techsupport@redhat.com or by phone with your Account and User Details, or view https://access.redhat.com/articles/7146730
catalog.redhat.com - Partial Outage
major Observed active window 10h 40m

View incident details and source

Started:

Catalog App
investigating
We are continuing to investigate this issue.
investigating
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.
Initial: Quay.io Push/Pull Degraded
minor Observed active window 19h 40m

View incident details and source

Started:

API Registry Security Scanning
monitoring
Registry is operational, security scanning is under maintenance.
monitoring
Image push and pull operations are functioning normally. We continue to monitor service health. Clair vulnerability scanning is temporarily disabled.
monitoring
The fix has been deployed. Quay.io is serving read/write requests. We are continuing to monitor the service
identified
The affected database tables have been updated. We are working to restoring full read/write traffic. Quay.io remains in read-only mode.
identified
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.
identified
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.
identified
Quay is in read-only mode. Only pulls are being served while we implement the fix.
identified
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
identified
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
investigating
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
investigating
We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.
August 2026
Ask Red Hat - Outage
major Observed active window 18m

View incident details and source

Started:

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

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
major Source 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
critical Source 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
major Source 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
major Source 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
minor Source 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
major Source 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.
identified
We are seeing 502s with quay.io pushes & pulls
Get alerts for Red Hat 3scale Subscribe to the provider incident feed Browse all services