Skip to content

Incident detail

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

Resolved incidentMajor

Timeline window

to

Outage alerts

Get alerted the next time Aiven breaks

Free email alerts for up to 5 providers — no card, live in about a minute. Paid plans add Slack, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

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

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

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

  4. 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](https://health.aws.amazon.com/health/status "https://health.aws.amazon.com/health/status")

    Should any further issues be encountered, please reach out to support via the Aiven console.