AWS Operational Issues in US-WEST-2
Affected: US-WEST (Oregon)
Alkira Outage History
Alkira degraded · 1 active incident View live status →Alkira had 19 outages in the last 2 years totaling 121h 51m of downtime — averaging 0.8 incidents per month.
There were 19 Alkira outages since October 15, 2024 totaling 121h 51m of downtime. Each is summarised below — incident details, duration, and resolution information.
Networking issues impacting Azure Services in West US
Affected: USWEST-AZURE-1 (California)
Timeline · 3 updates
- identified Jul 23, 2026, 04:57 PM UTC
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.
- monitoring Jul 23, 2026, 07:40 PM UTC
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.
- resolved Jul 23, 2026, 08:42 PM UTC
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.
Issues with login to Management Portal
Timeline · 1 update
- resolved Jul 22, 2026, 08:12 AM UTC
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.
Degraded Performance in USWEST-AZURE-2
Affected: USWEST-AZURE-2 (Washington)
Timeline · 3 updates
- identified May 29, 2026, 06:02 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.
- monitoring May 29, 2026, 08:02 AM UTC
The issue seems to be resolved. We are awaiting updates from Azure.
- resolved May 29, 2026, 10:57 PM UTC
This incident is resolved.
Portal is Inaccessible
Affected: Management Portal
Timeline · 3 updates
- investigating May 13, 2026, 09:45 AM UTC
We are currently investigating an issue with the portal being inaccessible.
- monitoring May 13, 2026, 10:01 AM UTC
The management portal is now accessible. We are monitoring it.
- resolved May 13, 2026, 01:39 PM UTC
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.
Degraded Performance in USWEST-AZURE-3 - CXP
Affected: USWEST-AZURE-3 (Arizona)
Timeline · 2 updates
- monitoring Apr 23, 2026, 10:59 AM UTC
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.
- resolved Apr 23, 2026, 01:38 PM UTC
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.
Degraded Performance in UAENORTH-AZURE-1 - CXP
Timeline · 1 update
- resolved Apr 23, 2026, 10:52 AM UTC
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. Updates from Service Provider: AZURE https://azure.status.microsoft/en-us/status
Notification Service Degradation
Affected: Notification Service
Timeline · 1 update
- resolved Mar 05, 2026, 12:42 AM UTC
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.
Route Visualization Service degraded
Affected: Route Visualization Service
Timeline · 4 updates
- investigating Dec 12, 2025, 02:29 AM UTC
We are currently investigating issue related to Route Visualization Service. Datapath is not affected due to this.
- identified Dec 12, 2025, 02:50 AM UTC
The issue has been identified, working on restoring the service.
- monitoring Dec 12, 2025, 02:56 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 12, 2025, 05:43 AM UTC
This incident has been resolved.
Azure Portal Access Incident
Affected: Management Portal
Timeline · 3 updates
- monitoring Oct 29, 2025, 04:53 PM UTC
We are currently monitoring an ongoing incident with Microsoft Azure, where their portal access appears to be intermittent. At this time, there is no impact to any Alkira services or data plane operations. All Alkira systems continue to function normally. You can follow updates on the Azure status page here: https://azure.status.microsoft/en-us/status
- monitoring Oct 29, 2025, 06:16 PM UTC
We have observed that some API calls to create resources in Microsoft Azure are timing out. In most cases, retrying the operation resolves the issue. Our systems are configured to automatically retry these API calls as needed, and we continue to closely monitor the situation. For the latest updates from Azure, please visit: https://azure.status.microsoft/en-us/status
- resolved Oct 30, 2025, 09:48 AM UTC
We no longer see any issues with API calls to Azure. Resolving this incident. For the latest updates from Azure, please visit: https://azure.status.microsoft/en-us/status
AWS Operational Issues in US-EAST-1
Affected: Network Provisioning Service
Timeline · 4 updates
- monitoring Oct 20, 2025, 04:03 PM UTC
We are aware of ongoing AWS operational issues in the us-east-1 region and are continuously monitoring for any potential impact on Alkira services. So far, all Alkira services are operating normally, and our data plane remains fully functional. However, we advise caution when provisioning new resources in AWS us-east-1, 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
- monitoring Oct 20, 2025, 04:07 PM UTC
We are continuing to monitor for any further issues.
- monitoring Oct 20, 2025, 05:56 PM UTC
We are continuing to monitor the situation and assessing if there is any impact to Alkira services. From our monitoring we have noticed errors on AWS load balancers which might show up as errors on Alkira portal. These are intermittent and a subsequent retry or refresh should resolve it.
- resolved Oct 20, 2025, 10:30 PM UTC
We no longer see any issues. Resolving this incident. Continue to follow AWS status page for further update. https://health.aws.amazon.com/health/status
Network Provisioning Service Impaired
Affected: Network Provisioning Service
Timeline · 3 updates
- investigating Aug 22, 2025, 01:09 AM UTC
We are investigating an issue with the networking provisioning service taking longer than anticipated to complete tasks. We will post updates here as we make progress with the issue.
- monitoring Aug 22, 2025, 01:13 AM UTC
The networking provisioning service is now restored. We have mitigated the issue and service is functional now.
- resolved Aug 22, 2025, 02:10 AM UTC
On August 21, 2025, at 11:23 PM UTC, the network provisioning service was buffering requests and unable to process them. Upon further investigation, the issue was traced to a backend database lock caused by another persistent operation. This operation was forcefully cleared at August 22, 2025, at 01:00 AM UTC, after which the network provisioning service became operational again. While the network provisioning service was affected during this time, customer access to the portal and data traffic remained unaffected.
Data packet loss affecting Southeast Asia region in Azure (APSOUTHEAST-AZURE-1 - Singapore)
Affected: APSOUTHEAST-AZURE-1 (Singapore)
Timeline · 4 updates
Customer portal timeouts
Timeline · 1 update
- resolved May 22, 2025, 10:49 PM UTC
On May 22nd, between 09:00 PM UTC and 9:30 PM UTC, some customers may have experienced timeouts while accessing the portal. The issue was caused by a database lock resulting from a configuration process that took longer than expected. The issue has since been mitigated, and all portal services have been fully restored. We sincerely apologize for any inconvenience this may have caused and appreciate your understanding as we work to prevent such occurrences in the future. Contact Alkira support if you have any questions or need further assistance.
Portal is inaccessible
Affected: Management Portal
Timeline · 9 updates
Customer portal timeouts and Provisioning Service unavailable
Affected: Management PortalNetwork Provisioning Service
Timeline · 2 updates
- monitoring Feb 07, 2025, 05:20 PM UTC
Please refer to this incident. https://status.alkira.com/incidents/g0fb4rv0j0r7
- resolved Feb 07, 2025, 05:21 PM UTC
This incident has been resolved.
Networking issues impacting Azure Services in East US2
Affected: USEAST-AZURE-2 (Virginia)
Timeline · 3 updates
- investigating Jan 09, 2025, 03:33 PM UTC
Azure has reported having networking infrastructure issues in East US2. While the issue does not impact existing network status, we are posting this here so that our customers are aware of this. New provision might have failures related to East US2. https://azure.status.microsoft/en-gb/status Summary of Impact from Azure: As early as 22:00 UTC on 08 Jan 2025, we noticed a partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. The configuration change caused inconsistent service state. This could have resulted in intermittent Virtual machine connectivity issues or failures in allocating resources or communicating with resources in the region.
- monitoring Jan 09, 2025, 07:01 PM UTC
Services are responding well, and the impact is minimal. We continue to monitor the status. https://azure.status.microsoft/en-gb/status
- resolved Jan 10, 2025, 10:45 PM UTC
Most of the services are fully functional in Azure East US2. Please reach out if you are still having issues. This incident is closed.
Networking provisioning is taking longer than anticipated
Affected: Network Provisioning Service
Timeline · 3 updates
- investigating Oct 21, 2024, 03:05 PM UTC
We are investigating an issue with the networking provisioning service taking longer than anticipated to complete tasks. We will post updates here as we make progress with the issue.
- monitoring Oct 21, 2024, 06:45 PM UTC
We noticed an unexpected surge in internal events published to the Network Provisioning Service. Network Provisioning Service could not consume the events at the rate they are published. We have optimized the service to handle this surge, after which the load on the service has been reduced to a normal state. We are continuing to monitor the service.
- resolved Oct 21, 2024, 10:22 PM UTC
This incident has been resolved.
Health reporting issue with few CXP regions
Affected: Connector Health Monitoring Service
Timeline · 3 updates
- investigating Oct 15, 2024, 10:55 PM UTC
We are actively investigating an issue with the health reporting service in the following CXPs. We will update as we know the root cause the problem. aws-ca-central-1 azure-northcentralus gcp-northamerica-northeast2 gcp-us-central1 gcp-us-east1
- identified Oct 15, 2024, 10:56 PM UTC
The issue has been identified, and we are working towards recovering the service in the mentioned regions.
- resolved Oct 15, 2024, 11:09 PM UTC
One of the underlying nodes serving health monitoring services had failed. While the infrastructure is auto-scalable the failover took longer than expected, resulting in the health monitoring service not reporting the tunnel health status for a few minutes. Currently, the infrastructure is stable, and no issues are observed with any of the services. Reach out to Alkira support for any queries.