- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 100
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 1d 21h it lasted.
Anything that failed between 2026-06-23 14:18 UTC and 2026-06-25 11: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.
Updates from Aiven 5
- investigating
We have paused Kafka 3.8 ->3.9 upgrades as we are investigating an issue with KRaft migration during the upgrade. Aiven is actively monitoring affected services and applying mitigations where required. Impact: Existing Kafka services continue to run. Customers attempting to upgrade Kafka services from version 3.8 to 3.9 will not be able to complete the upgrade while KRaft migrations are paused. Next update: We will provide an update once more information is available.
provider
- identified
We have identified two separate problems: • An issue in migration code • An [upstream bug](https://github.com/apache/kafka/pull/19854) We are working on the fix for the migration issue and back-porting the fix for the upstream bug. If you have any issues, please contact support.
provider
- identified
We have identified issues affecting KRaft migrations (Kafka 3.8 to 3.9 upgrades). We have paused all migrations while we work on a fix. If you are experiencing any issues, please contact support.
provider
- monitoring
We have deployed fixes for the issues affecting KRaft migrations during Kafka 3.8 to 3.9 upgrades, and migrations have been re-enabled. We are continuing to monitor the situation to ensure services remain stable. If you are experiencing any issues, please contact support.
provider
- resolved
The issues affecting KRaft migrations during Kafka 3\.8 to 3\.9 upgrades have been resolved. Fixes have been deployed, migrations have been re-enabled, and services have remained stable during monitoring. If you are experiencing any issues, please contact support.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-bf4a2c443e
Is Aiven still down?
No, this incident was resolved 2026-06-25 11:38 UTC. For Aiven's live state, see https://down.guide/aiven.
How long did it last?
1d 21h, from 2026-06-23 14:18 UTC to 2026-06-25 11:38 UTC, by the times Aiven posted.
What caused it?
Aiven hasn't published a root cause. If it does, it shows here.
Where does this come from?
Aiven's official status page, https://status.aiven.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.