Support Cases Access.redhat.com Outage
Resolved
This incident has been resolved.
Jun 12, 8:56 AMResolved Jun 12, 8:57 AMCriticalSupport Cases
Status Provider
Home
/
Status
/
Service
Home
/
Status
/
Service
Container registry for building, storing, and distributing containers.
Source
auto
Category
Cloud
Adapter
API V1 STATUS
Verified
Pending review
Current state
Operational
Checked 58m ago
141
Components
0
Active incidents
0
Maintenance
3.57%
90d uptime
Support Cases Access.redhat.com Outage
Jun 12, 8:56 AM
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
Showing 1 to 25 of 141 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
API | Operational | Component | Not recorded |
API | Operational | Component | Not recorded |
API Manager Red Hat 3scale API Management SaaS APIs you can use to configure and admin your API Management. This includes: - Account Management API, Analytics API and Billing API - Admin Portal UI - AutoSSL - Developer Portal UI | Operational | Component | Not recorded |
Ansible Automation Platform - Automation Analytics | Operational | Component | Not recorded |
Ansible Lightspeed | Operational | Component | Not recorded |
Atlassian Cloud | Operational | Component | Not recorded |
Catalog App | Operational | Component | Not recorded |
Content | Operational | Component | Not recorded |
Downloads | Operational | Component | Not recorded |
Homepage | Operational | Component | Not recorded |
Homepage | Operational | Component | Not recorded |
Homepage | Operational | Component | Not recorded |
Homepage | Operational | Component | Not recorded |
OpenShift Update Service OpenShift Update Service (OSUS) is a service accessible at: https://api.openshift.com/api/upgrades_info/ | Operational | Component | Not recorded |
Partner Container Certification Workflow | Operational | Component | Not recorded |
Registry Account Management | Operational | Component | Not recorded |
Security MCP | Operational | Component | Not recorded |
maven.repository.redhat.com | Operational | Component | Not recorded |
subscription.rhsm.redhat.com | Operational | Component | Not recorded |
Ansible Automation Platform - Automation Hub | Operational | Component | Not recorded |
Ask | Operational | Component | 6/16/2026 |
Assisted Installer Service | Operational | Component | Not recorded |
Build System | Operational | Component | Not recorded |
CDN and Entitlement Network | Operational | Component | Not recorded |
Container API | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Related status pages based on category, adapter type, and operational history.
Quay is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
Normalized official status-page data for incidents, maintenance, components, and history.
3.57%
Known uptime
28 known history days
141
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
50
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
console.redhat.com
Operational
Inventory
Operational
access.redhat.com
Operational
Red Hat Lightspeed - Patch
Operational
docs.redhat.com
Operational
1
operational days
0
degraded days
18
outage days
9
maintenance days
62
unknown days
Latest outages and degradations detected from the official status page.
This incident has been resolved.
Service is fully restored. The root cause was identified as an intermittent issue with a backend API serving hardware information.
This incident has been resolved.
This incident has been resolved.
The service has been restored and is operating normally.
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.
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.
This incident has been resolved.
On April 21, a routine production deployment included a dependency upgrade that exposed a latent incompatibility, causing Quay.io application pods to crash on startup. Image pulls and pushes were fully unavailable for approximately 12 minutes before the team failed over to a secondary region, restoring pulls. Pushes remained unavailable for approximately 70 additional minutes while the deployment was reverted and traffic was incrementally shifted back to the primary region. We are enabling staging parity for all runtime features, improving automated rollback mechanisms, and isolating observability subsystems from the critical request path to prevent recurrence.
This incident has been resolved.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
Maintenance is complete.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Quay status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.redhat.com
Adapter
API V1 STATUS
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
