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 -
At 3:52 PM PST, Notification service started reporting API timeouts. On further analysis, the underlying node went out of service. This node was brought out of the cluster and service was restored at 4:34 PM PST. Users might have noticed API timeouts during this interval. Service is now responding and no further errors are reported.
Mar 5, 00:42 UTC
Mar 4, 2026
No incidents reported.
Mar 3, 2026
No incidents reported.
Mar 2, 2026
Unresolved incident: Issues with AWS services in the ME-CENTRAL-1 Region.