Issues with AWS services in the ME-CENTRAL-1 Region
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
Update - AWS continues to work on restoring services. For more details: https://health.aws.amazon.com/health/status
Mar 01, 2026 - 20:25 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

About This Site

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.

Uptime over the past 90 days. View historical uptime.
API Service Operational
90 days ago
100.0 % uptime
Today
Connector Health Monitoring Service Operational
90 days ago
100.0 % uptime
Today
Cloud Insights Operational
90 days ago
100.0 % uptime
Today
Dashboard Service Operational
90 days ago
100.0 % uptime
Today
Management Portal Operational
90 days ago
99.98 % uptime
Today
Network Provisioning Service Operational
90 days ago
100.0 % uptime
Today
Notification Service Operational
90 days ago
100.0 % uptime
Today
Route Visualization Service Operational
90 days ago
100.0 % uptime
Today
CXP Regions - Americas Operational
90 days ago
100.0 % uptime
Today
CA-CENTRAL-1 (Montreal) Operational
90 days ago
100.0 % uptime
Today
CACENTRAL-AZURE-1 (Toronto) Operational
90 days ago
100.0 % uptime
Today
CAEAST-AZURE-1 (Quebec City) Operational
90 days ago
100.0 % uptime
Today
US-EAST (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
US-EAST-2 (Ohio) Operational
90 days ago
100.0 % uptime
Today
US-WEST (Oregon) Operational
90 days ago
100.0 % uptime
Today
US-WEST-1 (N. California) Operational
90 days ago
100.0 % uptime
Today
USCENTRAL-AZURE-1 (Texas) Operational
90 days ago
100.0 % uptime
Today
USCENTRAL-AZURE-3 (Iowa) Operational
90 days ago
100.0 % uptime
Today
USEAST-AZURE-1 (Virginia) Operational
90 days ago
100.0 % uptime
Today
USEAST-AZURE-2 (Virginia) Operational
90 days ago
100.0 % uptime
Today
USWEST-AZURE-2 (Washington) Operational
90 days ago
100.0 % uptime
Today
USWEST-AZURE-3 (Arizona) Operational
90 days ago
100.0 % uptime
Today
USCENTRAL-AZURE-2 (Illinois) Operational
90 days ago
100.0 % uptime
Today
NORTHAMERICANORTHEAST-GCP-1 (Montreal) Operational
90 days ago
100.0 % uptime
Today
NORTHAMERICANORTHEAST-GCP-2 (Toronto) Operational
90 days ago
100.0 % uptime
Today
USCENTRAL-GCP-1 (Iowa) Operational
90 days ago
100.0 % uptime
Today
USWEST-GCP-1 (Oregon) Operational
90 days ago
100.0 % uptime
Today
USEAST-GCP-1 (South Carolina) Operational
90 days ago
100.0 % uptime
Today
USWEST-GCP-4 (Las Vegas) Operational
90 days ago
100.0 % uptime
Today
USEAST-GCP-4 (Northern Virginia) Operational
90 days ago
100.0 % uptime
Today
CA-WEST-1 (Calgary) Operational
90 days ago
100.0 % uptime
Today
SA-EAST-1 (Sao Paulo) Operational
90 days ago
100.0 % uptime
Today
MEXICOCENTRAL-AZURE-1 (Querétaro State) Operational
90 days ago
100.0 % uptime
Today
USSOUTH-GCP-1 (Dallas) Operational
90 days ago
100.0 % uptime
Today
SASOUTH-AZURE-1 (Sao Paulo) Operational
90 days ago
100.0 % uptime
Today
USWEST-AZURE-1 (California) Operational
90 days ago
100.0 % uptime
Today
CXP Regions - APAC Operational
90 days ago
100.0 % uptime
Today
AP-EAST (Hong Kong) Operational
90 days ago
100.0 % uptime
Today
AP-NORTHEAST (Tokyo) Operational
90 days ago
100.0 % uptime
Today
AP-NORTHEAST-2 (Seoul) Operational
90 days ago
100.0 % uptime
Today
AP-SOUTH-1 (Mumbai) Operational
90 days ago
100.0 % uptime
Today
AP-SOUTHEAST (Sydney) Operational
90 days ago
100.0 % uptime
Today
AP-SOUTHEAST-1 (Singapore) Operational
90 days ago
100.0 % uptime
Today
APSOUTHEAST-AZURE-1 (Singapore) Operational
90 days ago
100.0 % uptime
Today
INDIACENTRAL-AZURE-1 (Pune) Operational
90 days ago
100.0 % uptime
Today
AP-SOUTH-2 (Hyderabad) Operational
90 days ago
100.0 % uptime
Today
AUSTRALIAEAST-AZURE-1 (New South Wales) Operational
90 days ago
100.0 % uptime
Today
JAPANEAST-AZURE-1 (Tokyo) Operational
90 days ago
100.0 % uptime
Today
AUSTRALIASOUTHEAST-GCP-1 (Sydney) Operational
90 days ago
100.0 % uptime
Today
AUSTRALIASOUTHEAST-GCP-2 (Melbourne) Operational
90 days ago
100.0 % uptime
Today
CHINANORTH-AWSCHINA-1 (Beijing, China) Operational
90 days ago
100.0 % uptime
Today
CHINANORTH-AZURECHINA-3 (Hebei, China) Operational
90 days ago
100.0 % uptime
Today
APEAST-AZURE-1 (Hong Kong) Operational
90 days ago
100.0 % uptime
Today
APNORTHEAST-GCP-1 (Tokyo) Operational
90 days ago
100.0 % uptime
Today
APNORTHEAST-GCP-2 (Osaka) Operational
90 days ago
100.0 % uptime
Today
AP-SOUTHEAST-3 (Jakarta) Operational
90 days ago
100.0 % uptime
Today
CXP Regions - EMEA Degraded Performance
90 days ago
100.0 % uptime
Today
EU-CENTRAL (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
EU-SOUTH-1 (Milan) Operational
90 days ago
100.0 % uptime
Today
EU-WEST-1 (Ireland) Operational
90 days ago
100.0 % uptime
Today
EU-WEST-2 (London) Operational
90 days ago
100.0 % uptime
Today
EUNORTH-AZURE-1 (Ireland) Operational
90 days ago
100.0 % uptime
Today
EUWEST-AZURE-1 (Netherlands) Operational
90 days ago
100.0 % uptime
Today
FRANCECENTRAL-AZURE-1 (Paris) Operational
90 days ago
100.0 % uptime
Today
QATARCENTRAL-AZURE-1 (Doha) Operational
90 days ago
100.0 % uptime
Today
UKSOUTH-AZURE-1 (London) Operational
90 days ago
100.0 % uptime
Today
AF-SOUTH-1 (Cape Town) Operational
90 days ago
100.0 % uptime
Today
SWITZERLANDNORTH-AZURE-1 (Zurich) Operational
90 days ago
100.0 % uptime
Today
EUWEST-GCP-8 (Milan) Operational
90 days ago
100.0 % uptime
Today
EUWEST-GCP-1 (Belgium) Operational
90 days ago
100.0 % uptime
Today
EUWEST-GCP-3 (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
MECENTRAL-GCP-2 (Dammam) Operational
90 days ago
100.0 % uptime
Today
ME-CENTRAL-1 (UAE) Degraded Performance
90 days ago
100.0 % uptime
Today
ME-SOUTH-1 (Bahrain) Degraded Performance
90 days ago
100.0 % uptime
Today
ITALYNORTH-AZURE-1 (Milan) Operational
90 days ago
100.0 % uptime
Today
UAENORTH-AZURE-1 (Dubai) Operational
90 days ago
100.0 % uptime
Today
SANORTH-AZURE-1 (Johannesburg) Operational
90 days ago
100.0 % uptime
Today
EU-CENTRAL-2 (Zurich) Operational
90 days ago
100.0 % uptime
Today
GERMANYWESTCENTRAL-AZURE-1 (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
EUWEST-GCP-4 (Netherlands) Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Aug 2, 2026

No incidents reported today.

Aug 1, 2026

Maintenance Notice - Alkira Cloud Services Exchange
Completed - The scheduled maintenance has been completed.
Aug 1, 03:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 1, 01:00 UTC
Scheduled - Please be aware that a system maintenance window is scheduled for Saturday, August 1, 2026, 1:00 AM–3:00 AM UTC.

What will be affected?
Network provisioning will be disabled during this window. However, there will be no impact on CXP Services or Network Traffic.

We will send another notification when the maintenance is about to begin. We apologize for any inconvenience this may cause.
Jul 22, 21:52 UTC

Jul 31, 2026

No incidents reported.

Jul 30, 2026

No incidents reported.

Jul 29, 2026

No incidents reported.

Jul 28, 2026

No incidents reported.

Jul 27, 2026

No incidents reported.

Jul 26, 2026

No incidents reported.

Jul 25, 2026

No incidents reported.

Jul 24, 2026

AWS Operational Issues in US-WEST-2
Resolved - AWS has resolved the incident and has provided the following details. We did not see any impact to Alkira's services during this time due to active redundancy.

Between 3:55 AM and 4:15 AM PDT, we experienced connectivity issues that impacted connectivity to the US-WEST-2 Region. This impacted multiple AWS services in the Region. Some customers may have also experienced issues accessing the AWS Management Console, with connection timeouts and unresponsive pages. Connectivity within the Region was not affected. Our engineers were automatically engaged at 4:01 AM PDT, and immediately began investigating this issue. We identified the root cause as an issue with networking devices responsible for network routing from the Region to the Seattle Metro, and began working in parallel on multiple paths to mitigate the impact. We took mitigation measures that led to initial recovery at 4:15 AM PDT. As the network continued to stabilize following our mitigation actions, a brief reconvergence event occurred between 4:47 AM and 4:59 AM PDT. During this reconvergence period, some customers may have experienced intermittent connectivity issues to the Region as network routes were re-established. By 4:59 AM PDT, all routes had been fully restored and service metrics returned to pre-event levels.

Customers using AWS Direct Connect through EqSe2, Westin Building Exchange, Seattle experienced an extended impact window from 3:55 AM to 5:12 AM PDT. These customers would have experienced connectivity issues until network routes for this specific path were fully restored at 5:12 AM PDT. Customers connected redundantly through other AWS Direct Connect locations were not impacted by this event.

The issue has been resolved and all AWS services are operating normally.
Jul 24, 13:13 UTC
Investigating - We are aware of ongoing AWS operational issues in the us-west-2 region and are continuously monitoring for any potential impact on Alkira services.

However, we advise caution when provisioning new resources in AWS us-west-2, as such operations may intermittently fail due to the ongoing AWS issue.

You can track the latest updates on the AWS status page:
https://health.aws.amazon.com/health/status
Jul 24, 11:55 UTC

Jul 23, 2026

Networking issues impacting Azure Services in West US
Resolved - Update from Azure:
Between 14:40 UTC and as early as 18:26 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure and other Microsoft cloud ( https://status.cloud.microsoft/ ) services associated with the West US region. Customers whose traffic traversed affected West US network infrastructure may also experience downstream impact. Customers leveraging affected downstream Azure services may have experienced a long tail of impact as individual services implemented and monitored service recovery measures. This issue is now resolved.
Jul 23, 20:42 UTC
Monitoring - Update from Azure:
We identified a recent change that was strongly correlated with the onset of impact and have initiated rollback actions. The rollback is currently in progress and making steady progress toward completion. Telemetry across services is beginning to show signs of recovery.

We are closely monitoring service health and traffic recovery as these actions are completed and will provide additional updates as we confirm measurable improvement.
Jul 23, 19:40 UTC
Identified - Azure has reported having networking infrastructure issues in West US. While the issue does not impact existing network status, we are posting this here so our customers are aware. New provisions might fail in the West US region. Alkira's services are not impacted during this time due to active redundancy.

https://azure.status.microsoft/en-us/status#

Summary of Impact from Azure - We are investigating a networking issue affecting connectivity to Azure services in the West US region. Impacted customers may experience intermittent connectivity failures, increased latency, or difficulty accessing Azure services. Customers with traffic traversing the West US region may also experience downstream impact.

We are exploring mitigation options on affected network devices. Early indications suggest the issue is related to network traffic flow through the impacted infrastructure; however our analysis remains ongoing. We are closely monitoring traffic while continuing our investigation.
Jul 23, 16:57 UTC
Issues with login to Management Portal
Resolved - On July 22nd, 2026, at approximately 06:40 AM UTC, logins to the management portal were failing. On further investigation, the issue was found to be related to an incorrect dependency upgrade in the login service. After correcting the version, the login service was fully restored by 08:00 AM UTC.
Jul 23, 06:30 UTC

Jul 22, 2026

No incidents reported.

Jul 21, 2026

No incidents reported.

Jul 20, 2026

No incidents reported.

Jul 19, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage