Is Alkira down?

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

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.

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.

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.

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.

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.

Starting at 04:16 UTC on 29 May 2026, a subset of customers using Azure services (including Virtual Machines) in West US 2 region may be experiencing connectivity issues. Azure has reported that a network device it manages has experienced a fault, resulting in the loss of network connectivity to some downstream resources. The unhealthy network device is being isolated from the network by Azure, and traffic is being rerouted to healthy infrastructure. Alkira's services are not impacted during this time due to active redundancy.

The issue seems to be resolved. We are awaiting updates from Azure.

This incident is resolved.

We are currently investigating an issue with the portal being inaccessible.

The management portal is now accessible. We are monitoring it.

Access to the management portal remains fully operational. Our internal investigation confirmed that all system components are healthy, and the issue was resolved automatically without intervention. We suspect a transient network or provider-level disruption and will continue to monitor performance closely. No customer traffic was impacted during this issue.