We have resolved the underlying cause of this issue.

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

We apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.

The issue has been resolved. Terraform & Kubernetes operator users should no longer experience 400 errors when using aiven_pg_database. We apologize for any inconvenience caused.

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.

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

The monitoring period has passed without further evidence of the issue occurring. Incident has been declared resolved.

We have resolved the underlying cause of the issue affection service operations in our Azure regions.

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

We apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.

This issue is now resolved.

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

We apologise for the inconvenience caused by this issue.

We have resolved the underlying cause of the kafka service disruption.

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

We apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.