Update - We started noticing issue with services from AWS ME-SOUTH-1 for AZ0 at 13:07:27 UTC. AZ1 had been out of service from Mar 01. While we work with AWS on status, AWS has strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. For more details: https://health.aws.amazon.com/health/status
Mar 24, 2026 - 02:01 UTC
Update - AWS started seeing increased API error rates in ME-SOUTH-1 Region from Mar 01 9:56 PM PST. Current issues are affecting both ME-SOUTH-1 and ME-CENTRAL-1. Recovery is expected to take at least a day due to required facility, power, and safety assessments. For more details: https://health.aws.amazon.com/health/status
Mar 02, 2026 - 17:11 UTC
Update - AWS continues to work on restoring services. Recovery is expected to take at least a day due to required facility, power, and safety assessments. For more details: https://health.aws.amazon.com/health/status
Mar 02, 2026 - 17:06 UTC
Identified - Update from AWS: A localized power outage is impacting one Availability Zone (mec1-az2) in the ME-CENTRAL-1 region. As a result, EC2 instances, databases, EBS volumes, and other resources in that zone are unavailable or experiencing connectivity issues. Some AWS services are also seeing increased errors and latency. For more details: https://health.aws.amazon.com/health/status
Mar 01, 2026 - 15:05 UTC
Update - We are continuing to investigate this issue.
Mar 01, 2026 - 14:24 UTC
Investigating - AWS is investigating issues with AWS services in the ME-CENTRAL-1 Region. Issue is related to connectivity and power affecting APIs and instances in a single Availability Zone (mec1-az2) in the ME-CENTRAL-1 Region due to a localized power issue. Issue started at Mar 01 4:51 AM PST. For more details: https://health.aws.amazon.com/health/status
Mar 01, 2026 - 14:23 UTC
This is Alkira's status page, where you can get real-time and historic updates on our system performance. If there are interruptions, we will post a note here.
As always, if you are experiencing any issues with Alkira, don't hesitate to get in touch with us at support@alkira.com and we'll get back to you as soon as we can.
Resolved -
Azure has resolved the issue. No Alkira services were impacted due to active redundancy built into the design.
Details as provided by Azure - Between 09:37 UTC and 10:39 UTC on 23 April 2026, a network-related issue affected a subset of Azure workloads whose traffic traverses the West US 3 region. Impacted customers may have experienced connectivity issues and intermittent failures, which affected the availability and operation of resources in the region. The impact was limited to customers whose resources relied on the affected regional infrastructure.
Apr 23, 13:38 UTC
Monitoring -
Starting at 09:37 UTC on 23 April 2026, a subset of customers using Azure services (including Virtual Machines) in West US 3 may experience connectivity issues and intermittent failures, which could affect the availability and operation of resources hosted in the region. Alkira services were not impacted during this time due to active redundancy.
Apr 23, 10:59 UTC
Resolved -
We observed degraded performance in UAENORTH-AZURE-1 CXP. Between 09:32 UTC on 23 Apr 2026 and 10:31 UTC on 23 Apr 2026, Virtual Machines in the UAE North region experienced connectivity issues. Alkira services were not impacted during this time.