Update - 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.
Update - 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 03, 2026 - 10:21 UTC
Update - 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 02, 2026 - 17:52 UTC
Update - 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 02, 2026 - 13:37 UTC
Update - 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 01, 2026 - 14:26 UTC
Update - 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 04, 2026 - 04:44 UTC
Update - 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 02, 2026 - 17:52 UTC
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.
Resolved -
This incident has been resolved.
May 5, 15:33 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 5, 13:55 UTC
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 UTC
Completed -
The scheduled maintenance has been completed.
Apr 27, 14:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 27, 13:00 UTC
Scheduled -
Hybrid Cloud Console Inventory is undergoing scheduled database maintenance on Monday, April 27th, from 13:00 to 14:00 UTC. During this time, Inventory systems and associated Workspaces will be in a read-only state. All write operations will be temporarily disabled. Data processing for newly-registered systems will be delayed and may take a few hours to appear in the console after the maintenance period concludes.
Apr 22, 19:35 UTC