Highway experienced a major incident on October 20, 2025 affecting External API, lasting 10h 31m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 20, 2025, 11:13 AM UTC
We are currently seeing issues on our east coast region servers relating to AWS outage https://health.aws.amazon.com/health/status.
- identified Oct 20, 2025, 11:27 AM UTC
AWS services are recovering. All of our systems are fully functional, though some downstream APIs we rely on continue to experience issues.
- identified Oct 20, 2025, 12:56 PM UTC
We are actively monitoring the AWS outage and its impact on our partners. Our systems remain fully operational. However, missing data from our partners' services may result in degraded performance for some clients.
- identified Oct 20, 2025, 04:21 PM UTC
We continue to actively monitor the ongoing AWS outage and its cascading effects on our partners and services. Our core systems remain fully operational, but the disruption in data feeds from partners persists, potentially leading to degraded performance for select clients. AWS is experiencing continued elevated error rates and latencies across multiple services in the US-EAST-1 region (Northern Virginia), stemming from a DNS resolution issue with the DynamoDB API endpoint that began around 3:11 a.m. ET today. This has impacted over 70 services, including EC2 launches, Lambda, SQS, and global features like IAM updates, with partial mitigations in place but full recovery still underway. In response, we are evaluating activation of our Disaster Recovery (DR) plan per our established policies. If these regional issues persist beyond the next hour, we will initiate a controlled failover to our secondary region to minimize any further client impact and restore optimal data synchronization. We appreciate your patience and will provide our next update by 1:30 PM CST today, or sooner if conditions change significantly.
- identified Oct 20, 2025, 06:28 PM UTC
AWS services in the US-EAST-1 region are showing strong signs of recovery following the DNS resolution issue with the DynamoDB API endpoint that began early this morning. Core mitigations have been implemented, with over 33 services—including DynamoDB, SQS, and IAM—now fully operational. While elevated error rates persist for new EC2 instance launches and related services like Lambda and RDS, successful operations are increasing across Availability Zones, and backlog processing (e.g., for EventBridge and CloudTrail) is progressing steadily. Our systems have stabilized in tandem, with data latency improving significantly. We no longer anticipate activating our Disaster Recovery plan at this time, as conditions continue to mend. Some residual latency in partner data feeds and system synchronization may still affect a subset of clients intermittently. Our engineering team is actively addressing these to ensure seamless performance. Thank you for your patience—we're nearly through this. The next update will follow by 9:00 AM PDT today, or earlier if full normalization is confirmed. For immediate concerns, contact our support team
- monitoring Oct 20, 2025, 07:53 PM UTC
We are pleased to report that our systems have recovered from the recent AWS outage in the US-EAST-1 region. All data synchronization processes with our partners are now complete, and latency issues have been fully resolved, restoring seamless performance for all clients. AWS has confirmed that the DNS resolution issue impacting DynamoDB and related services has been mitigated, with all affected services—over 70, including EC2, Lambda, and SQS—now operating normally across all Availability Zones. Our team will continue to monitor the situation closely to ensure ongoing stability. No further disruptions are anticipated. Thank you for your patience and support throughout this event. We will provide a final update by 5:00 PM EDT today, or sooner if any new developments arise.
- resolved Oct 20, 2025, 09:44 PM UTC
Our team has completed monitoring and validated system stability. No additional updates are planned, and normal operations have resumed for all clients. For any further assistance, please contact our support team