Alkira Outage History

This incident is resolved.

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.

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.

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

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.

This incident has been resolved.

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

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

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.

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.

This incident has been resolved.

Most of the services are fully functional in Azure East US2. Please reach out if you are still having issues. This incident is closed.

This incident has been resolved.

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.

Its seems like Azure has mitigated the issue for large extent. Please reach out to Azure if you are still having issues. We will close this incident on our side.

All services on USCENTRAL-AZURE-3 are restored.