New services or replacement nodes can not be created in AWS us-east-1 (United States, Virginia) due to an AWS outage.
Resolved·Partial outage

AWS has recovered and declared their incident as resolved. See the AWS status page for a timeline on the issue: https://health.aws.amazon.com/health/status Should any further issues be encountered, please reach out to support via the Aiven console.

Mon, Oct 20, 2025, 11:57 PM
(1 week ago)
·
Affected components
Aiven
Updates

Resolved

AWS has recovered and declared their incident as resolved. See the AWS status page for a timeline on the issue: https://health.aws.amazon.com/health/status Should any further issues be encountered, please reach out to support via the Aiven console.

Mon, Oct 20, 2025, 11:57 PM

Monitoring

AWS is recovering and EC2 instance rate limiting is back to pre incident levels. Service and node creation times are back to normal and there's no impact to customers at this time. We're continuing to monitor the AWS incident and will update again if any change to the incident affects customers.

Mon, Oct 20, 2025, 10:48 PM(1 hour earlier)

Monitoring

We continue to observe recovery across the majority of affected AWS services. While creating a new service may take slightly longer than usual, all services are functioning as expected. There are no remaining issues; however, we will continue to monitor the environment closely and provide updates as additional information becomes available.

Mon, Oct 20, 2025, 10:38 AM(12 hours earlier)

Investigating

Due to an ongoing disruption at the AWS us-east-1 (Virginia) region new services or nodes can not be created in that region. Maintenance updates or service plan changes cannot be performed in this region. VPC or Private Link changes can not be performed. Replacement nodes for failed nodes can not be created.
Services which are currently running are not affected. Backups are not affected.

Mon, Oct 20, 2025, 09:30 AM(1 hour earlier)