Alkira experienced a minor incident on July 24, 2026 affecting US-WEST (Oregon), lasting 1h 18m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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
- 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.