Alkira Outage History

Started Jul 24, 2026, 11:55 AM UTC· resolved Jul 24, 2026, 01:13 PM UTC

1. investigating Jul 24, 2026, 11:55 AM UTC

   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

2. resolved Jul 24, 2026, 01:13 PM UTC

   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.

Read the full incident report →

Started Jul 23, 2026, 04:57 PM UTC· resolved Jul 23, 2026, 08:42 PM UTC

1. 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.

2. 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.

3. 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.

Read the full incident report →

Started Jul 22, 2026, 08:12 AM UTC· resolved Jul 23, 2026, 06:30 AM UTC

1. 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.

Read the full incident report →

Started May 29, 2026, 06:02 AM UTC· resolved May 29, 2026, 10:57 PM UTC

1. 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.

2. monitoring May 29, 2026, 08:02 AM UTC

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

3. resolved May 29, 2026, 10:57 PM UTC

   This incident is resolved.

Read the full incident report →

Started May 13, 2026, 09:45 AM UTC· resolved May 13, 2026, 01:39 PM UTC

1. investigating May 13, 2026, 09:45 AM UTC

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

2. monitoring May 13, 2026, 10:01 AM UTC

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

3. 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.

Read the full incident report →

Started Apr 23, 2026, 10:59 AM UTC· resolved Apr 23, 2026, 01:38 PM UTC

1. 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.

2. 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.

Read the full incident report →

Started Apr 23, 2026, 09:32 AM UTC· resolved Apr 23, 2026, 10:31 AM UTC

1. 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

Read the full incident report →

Started Mar 04, 2026, 11:52 PM UTC· resolved Mar 05, 2026, 12:34 AM UTC

1. 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.

Read the full incident report →

Started Dec 12, 2025, 02:29 AM UTC· resolved Dec 12, 2025, 05:43 AM UTC

1. 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.

2. identified Dec 12, 2025, 02:50 AM UTC

   The issue has been identified, working on restoring the service.

3. monitoring Dec 12, 2025, 02:56 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Dec 12, 2025, 05:43 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 29, 2025, 04:53 PM UTC· resolved Oct 30, 2025, 09:48 AM UTC

1. 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

2. 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

3. 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

Read the full incident report →

Started Oct 20, 2025, 04:03 PM UTC· resolved Oct 20, 2025, 10:30 PM UTC

1. 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

2. monitoring Oct 20, 2025, 04:07 PM UTC

   We are continuing to monitor for any further issues.

3. 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.

4. 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

Read the full incident report →

Started Aug 22, 2025, 01:09 AM UTC· resolved Aug 22, 2025, 02:10 AM UTC

1. 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.

2. 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.

3. 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.

Read the full incident report →

Started Aug 18, 2025, 07:57 PM UTC· resolved Aug 18, 2025, 10:55 PM UTC

1. investigating Aug 18, 2025, 07:57 PM UTC

   We are currently observing data packet loss affecting Southeast Asia region in Azure (APSOUTHEAST-AZURE-1 - Singapore). We are actively investigating this incident and update on the status as soon as possible.

2. monitoring Aug 18, 2025, 08:08 PM UTC

   We noticed all the health status recovered for Southeast Asia region in Azure. We are still investigating the reason for the same. As of now, all the health status reports are active.

3. monitoring Aug 18, 2025, 09:14 PM UTC

   Azure confirmed about incident affecting SouthEast Asia region. The issue has been mitigated and services have recovered. We will continue to monitor the region for some more time. Details from Azure about the incident: There was an incident in our SouthEast Asia and Korea Central regions. The incident was caused by a hardware failure in a core router in Singapore, which impacted outbound connectivity and cross-region communications. The engineering team has moved the router out of rotation and have updated that most services have recovered, though minor congestion in some locations is being addressed.

4. resolved Aug 18, 2025, 10:55 PM UTC

   At 18:50 PM UTC, we started receiving health alerts related to SouthEast Asia (APSOUTHEAST-AZURE-1 CXP) region in Azure. Upon investigation, we noticed the data tunnels that were going in and out of this region were either flapping or down. Further investigation revealed that traffic within APSOUTHEAST-AZURE-1 CXP was working fine; however any anything leaving the region was either not working or working intermittently. At 20:08 PM UTC, the issue was entirely resolved automatically without any intervention from our side. We engaged Azure support to get more details about the incident and they confirmed that there was a hardware failure in a core router in Singapore, which impacted outbound connectivity and cross-region communications. Their engineering team has moved the router out of rotation and has updated that most services have recovered, though minor congestion in some locations is being addressed. We will follow up with Azure for a detailed RCA. Please reach out to Alkira support if you have any questions.

Read the full incident report →

Started May 22, 2025, 09:00 PM UTC· resolved May 22, 2025, 09:30 PM UTC

1. 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.

Read the full incident report →

Started Apr 02, 2025, 06:15 PM UTC· resolved Apr 02, 2025, 07:56 PM UTC

1. investigating Apr 02, 2025, 06:15 PM UTC

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

2. investigating Apr 02, 2025, 06:16 PM UTC

   We are continuing to investigate this issue.

3. investigating Apr 02, 2025, 06:22 PM UTC

   As of April 2nd at 6:00 PM UTC, internal alerts were triggered, indicating an issue with the management portal service. Our team is actively investigating the incident.

4. investigating Apr 02, 2025, 06:43 PM UTC

   Management portal service has still not recovered, we are still investigating the issue.

5. identified Apr 02, 2025, 07:08 PM UTC

   We have identified the issue and are trying various ways to remediate it.

6. identified Apr 02, 2025, 07:13 PM UTC

   We have identified and fixed the issue. We are seeing signs of recovery, and the portal should be accessible. We will continue to remediate this issue and post a root cause analysis.

7. monitoring Apr 02, 2025, 07:14 PM UTC

   A fix has been implemented and we are monitoring the results.

8. resolved Apr 02, 2025, 07:56 PM UTC

   This incident is fully resolved. A detailed postmortem will follow.

9. postmortem Apr 08, 2025, 02:11 AM UTC

   ### Summary of the Problem On April 2nd, 2025, at approximately 17:50 UTC, one of the core infrastructure services supporting the Alkira Management Portal experienced significant memory pressure. This led to temporary portal unavailability, impacting customers’ ability to access and manage their network configuration. The issue was entirely resolved by 19:10 UTC the same day. ### Findings The incident was triggered by a burst of complex API requests that caused elevated memory usage within one of the services. The root cause was identified promptly, and mitigation steps were initiated quickly. However, full recovery took additional time due to ensuring sustained health before restoring access to all users. While the platform is designed to support a wide range of workloads, this scenario highlighted opportunities to speed up recovery workflows in similar scenarios. Customer access to the portal was limited during this time, but data traffic was not affected. ### Corrective Actions * Immediately applied targeted API throttling and usage restrictions for the APIs that caused the memory spike. * Restarted and stabilized the affected service once memory levels normalized. * Closely monitored system performance to ensure full recovery and continued stability. ### Next Steps To further enhance platform resilience: * Apply API rate limiting and throttling mechanisms across the platform. * Optimize existing APIs to be more lightweight and resource-efficient.

Read the full incident report →

Started Feb 07, 2025, 05:20 PM UTC· resolved Feb 07, 2025, 05:21 PM UTC

1. monitoring Feb 07, 2025, 05:20 PM UTC

   Please refer to this incident. https://status.alkira.com/incidents/g0fb4rv0j0r7

2. resolved Feb 07, 2025, 05:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 09, 2025, 03:33 PM UTC· resolved Jan 10, 2025, 10:45 PM UTC

1. 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.

2. 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

3. 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.

Read the full incident report →