Kafka Startup-2 clusters unstable

The issue causing instability for Kafka startup-2 plans is resolved. All services are now back to full operation. Please feel free to report any further problems to Aiven support through the Aiven console. We apologise for the inconvenience this incident has caused and commit to analysing and improving our platform to avoid future incidents similar to this one.

All impacted customer Kafka services are now stable. No further instability is expected. Our teams are monitoring this situation internally. If you continue to experience issues with your Kafka service, please reach out to Aiven Support.

All Nodes have been replaced and we are monitoring the situation.

All Nodes have been replaced and we are monitoring the situation.

All Nodes have been replaced and we are monitoring the situation.

No components were marked as affected by this incident.

We are moving potentially impacted startup-2 clusters to different node types.

No components were marked as affected by this incident.

Our team continue working towards rolling out a mitigation for startup-2 Kafka clusters.

Our team continue working towards rolling out a mitigation for startup-2 Kafka clusters.

Our team continue working towards rolling out a mitigation for startup-2 Kafka clusters.

We made the changes to prevent any new startup-2 clusters from using ARM. Currently, Our team is working on rolling out mitigation which will move the existing Kafka startup-2 nodes from ARM to x86.

Our team is working on rolling out mitigation which will move the Kafka startup-2 nodes from ARM to x86.

Our team is working on rolling out mitigation which will move the Kafka startup-2 nodes from ARM to x86.

We have identified some of the startup-2 Kafka clusters are facing service unavailability/instability. We are currently investigating the affected services to fix them. And, also working on a temporary mitigation to stop new services being affected on the issue.