Issues with spin up node in google asia-southeast1 region

What to do

• Check whether you use Aiven in apac, asia-southeast1. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4d 14h it lasted.

  Anything that failed between 2026-10-12 00:04 UTC and 2026-10-16 14:38 UTC may need a replay.

• Subscribe to Aiven's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=aiven works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

This is due to an upstream cloud provider issue that we are working on.

Category: Upstream dependency

Updates from Aiven 4

1. investigatingOct 12, 2026, 12:04 AM UTC

   We have issues in the google asia-southeast1 region where we cannot spin up nodes. This is due to an upstream cloud provider issue that we are working on. We are currently investigating and will update further details in the next 30 minutes.

   provider

2. investigatingOct 12, 2026, 3:09 AM UTC

   We are investigating an issue preventing node creation in asia-southeast1. The issue is only affecting some users. Engineering is actively engaged with GCP support. Next update in 30 minutes.

   provider

3. identifiedOct 16, 2026, 5:04 AM UTC

   We have identified the root cause of the issue preventing node creation in asia-southeast1. Our team is working with GCP to implement a fix. We will provide another update as soon as more information becomes available.

   provider

4. resolvedOct 16, 2026, 2:38 PM UTC

   We have resolved the underlying cause of this issue in Google's asia-southest1 region. Should any further issues be encountered, please reach out to support via the Aiven console. We apologise for the inconvenience caused by this issue.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.