Kafka upgrades to 3.9 are paused

What to do

• Check whether your product depends on Aiven. 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 19h it lasted.

  Anything that failed between 2026-06-11 15:25 UTC and 2026-06-16 11:05 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.

Updates from Aiven 3

1. investigatingJun 11, 2026, 3:25 PM UTC

   We have identified an issue affecting KRaft migrations during Kafka upgrades to version 3.9, and have temporarily paused those upgrades while we investigate. If you try to upgrade now, your request will be rejected with an error asking you to contact support. We will re-enable upgrades once the issue is resolved. **Impact:** Running Kafka services are not affected and continue to operate normally. Customers who attempt to upgrade a Kafka service to version 3.9 or later will receive an `HTTP 403` error and the upgrade will not proceed. No data or service availability is impacted.

   provider

2. monitoringJun 15, 2026, 2:01 PM UTC

   We have a fix prepared, which is currently undergoing final verification. If validation is successful, we will proceed with deployment shortly. As a result, the incident is now moving into a monitoring phase while we observe system stability after the changes. We will re-enable Kafka upgrades to version 3.9 once we confirm the issue is fully resolved.

   provider

3. resolvedJun 16, 2026, 11:05 AM UTC

   The issue has been resolved. All affected functionality is operating normally.

   provider

Corrections

None so far.

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