Alkira Outage History

Alkira degraded · 1 active incident View live status →

Alkira had 10 outages in the last 2 years totaling 54h 3m of downtime — averaging 0.4 incidents per month.

There were 10 Alkira outages since August 18, 2025 totaling 54h 3m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.alkira.com

Minor May 29, 2026

Degraded Performance in USWEST-AZURE-2

Detected by Pingoru
May 29, 2026, 06:02 AM UTC
Resolved
May 29, 2026, 10:57 PM UTC
Duration
16h 55m
Affected: USWEST-AZURE-2 (Washington)
Timeline · 3 updates
  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 →

Critical May 13, 2026

Portal is Inaccessible

Detected by Pingoru
May 13, 2026, 09:45 AM UTC
Resolved
May 13, 2026, 01:39 PM UTC
Duration
3h 54m
Affected: Management Portal
Timeline · 3 updates
  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 →

Minor April 23, 2026

Degraded Performance in USWEST-AZURE-3 - CXP

Detected by Pingoru
Apr 23, 2026, 10:59 AM UTC
Resolved
Apr 23, 2026, 01:38 PM UTC
Duration
2h 38m
Affected: USWEST-AZURE-3 (Arizona)
Timeline · 2 updates
  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 →

Notice April 23, 2026

Degraded Performance in UAENORTH-AZURE-1 - CXP

Detected by Pingoru
Apr 23, 2026, 10:52 AM UTC
Resolved
Apr 23, 2026, 09:32 AM UTC
Duration
—
Timeline · 1 update
  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 →

Notice March 5, 2026

Notification Service Degradation

Detected by Pingoru
Mar 05, 2026, 12:42 AM UTC
Resolved
Mar 05, 2026, 12:42 AM UTC
Duration
—
Affected: Notification Service
Timeline · 1 update
  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 →

Minor December 12, 2025

Route Visualization Service degraded

Detected by Pingoru
Dec 12, 2025, 02:29 AM UTC
Resolved
Dec 12, 2025, 05:43 AM UTC
Duration
3h 13m
Affected: Route Visualization Service
Timeline · 4 updates
  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 →

Notice October 29, 2025

Azure Portal Access Incident

Detected by Pingoru
Oct 29, 2025, 04:53 PM UTC
Resolved
Oct 30, 2025, 09:48 AM UTC
Duration
16h 55m
Affected: Management Portal
Timeline · 3 updates
  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 →

Notice October 20, 2025

AWS Operational Issues in US-EAST-1

Detected by Pingoru
Oct 20, 2025, 04:03 PM UTC
Resolved
Oct 20, 2025, 10:30 PM UTC
Duration
6h 27m
Affected: Network Provisioning Service
Timeline · 4 updates
  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 →

Major August 22, 2025

Network Provisioning Service Impaired

Detected by Pingoru
Aug 22, 2025, 01:09 AM UTC
Resolved
Aug 22, 2025, 02:10 AM UTC
Duration
1h 1m
Affected: Network Provisioning Service
Timeline · 3 updates
  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 →