AWS Operational issue- Multiple services (UAE)

Update timeline

1. identified Mar 01, 2026, 01:17 PM UTC

   Hi Team, We have observed intermittent access issues affecting some of our services. Upon investigation, we’ve identified that this behavior is related to an ongoing incident reported by AWS UAE region. According to AWS's latest status update (https://health.aws.amazon.com/health/status), there is an active issue impacting multiple AWS services (Glue, Resource Groups, Service Catalog, EC2, and RDS) Our team is closely monitoring the situation and coordinating with AWS to track the resolution progress. We will continue to provide updates as new information becomes available or once normal service is fully restored.

2. identified Mar 01, 2026, 02:00 PM UTC

   Hi Team , As of Mar 01, 5:19 AM PST, AWS is investigating connectivity and power issues impacting APIs and instances in a single Availability Zone (mec1-az2) within the ME-CENTRAL-1 region. The issue is due to a localized power disruption. Existing instances within mec1-az2 are affected. Other AWS services may also experience increased error rates and latency for workflows operating in this Availability Zone. AWS is actively working to reroute traffic away from the impacted AZ. Instances running in other Availability Zones remain unaffected. Customers are advised to utilize alternate AZs for new launches, as RunInstances operations in the remaining AZs are expected to succeed. We are continuing to monitor the situation and will provide further updates as available.

3. identified Mar 01, 2026, 03:04 PM UTC

   We are continuing to work on a fix for this issue.

4. identified Mar 01, 2026, 03:14 PM UTC

   Hi All, We are actively working internally in coordination with AWS on the ongoing recovery efforts. The next update is expected in approximately 30 minutes. We will continue to share further updates as progress is made.

5. identified Mar 01, 2026, 04:10 PM UTC

   Hi Team, AWS is currently working on recovery as per the latest update on the AWS Health Dashboard (https://health.aws.amazon.com/health/status) . While we have redundancy across Availability Zones, a few services are experiencing cross-zone impact from the AWS side. We are closely coordinating with AWS to monitor the situation and minimize impact. Further updates will be shared as they become available.

6. identified Mar 01, 2026, 05:11 PM UTC

   Hi Team, As per the latest update from AWS, the primary impact remains on mec1-az2. However, networking and API-related errors from AWS are affecting functionality across multiple Availability Zones within the region, impacting our major services. We have attempted to migrate services across multiple Availability Zones in the UAE region as an alternative approach suggested by AWS however, API errors are still being observed. Our team is currently on a live call with the AWS team to explore alternative mitigation approaches and closely monitor error rates. We will share another update shortly if any improvement is observed.

7. identified Mar 01, 2026, 07:03 PM UTC

   Hi Team, This is to inform you that the services impacted earlier are now partially restored, and we are observing improved stability across the environment. Error rates have reduced significantly, and most functionalities are recovering. However, we continue to monitor the platform closely as recovery activities are still in progress to ensure complete stability. Our team remains engaged with the cloud provider and will share further updates once full restoration is confirmed. Thank you for your continued patience and support.

8. resolved Mar 01, 2026, 07:44 PM UTC

   Hi Team, The issue has been resolved and services are stable. However, one Availability Zone (AZ) on the AWS side remains down. We are actively monitoring the situation and will share updates if any impact is observed.