Status: MonitoringWe have completed our mitigating actions and the creation of new nodes for services on the Aiven platform has returned to normal. Customers can now proceed with any operations that were delayed during this issue, including service creation, scaling, upgrades, maintenance updates and configuration changes. Operations that were left pending should continue automatically. Our engine…
Status: ResolvedNew VM creation has returned to normal across all cloud providers, including DigitalOcean. * VM provisioning is operating normally across all regions. * The upstream DigitalOcean incident has been resolved. * We are continuing to monitor the infrastructure to ensure stable provisioning. The incident is now resolved. Thank you for your patience.Affected components Aiven (Operational…
Status: ResolvedOur team has successfully applied the appropriate mitigation to all impacted nodes, and the fix has been deployed to prevent future occurrences.Affected components Aiven (Operational)
Status: ResolvedWe 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.Affected components Aiven (Operational)
Status: ResolvedThe 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.
Status: ResolvedThe 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.
Status: ResolvedThe issue has been resolved. All affected functionality is operating normally.
Status: ResolvedThe monitoring period has passed without further evidence of the issue occurring. Incident has been declared resolved.Affected components Aiven (Operational)
Status: ResolvedWe 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.Affected components Aiven (Operatio…
Status: ResolvedThis 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.Affected components Aiven (Operational)
Status: ResolvedWe 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.
Status: ResolvedThe underlying issues with Amazon Web Services (AWS) in the ME-CENTRAL-1 and ME-SOUTH-1 regions are ongoing, and AWS continues to work on recovery. We have disabled the creation of new services and nodes in the affected regions to prevent further impact. We recommend our customers to migrate their services to a stable region as part of their disaster recovery plan. As there are no…