End of life for Aiven services
Learn about the upcoming end of life (EOL) for select Aiven services, including timelines, actions after end of life, recommended migration options, and next steps.
Aiven for M3DB
EOL date: April 30, 2025
After April 30, 2025, all running Aiven for M3DB services are powered off and deleted, making data from these services inaccessible.
The recommended alternative for your metrics management and analysis is Aiven for Metrics.
Aiven for InfluxDB
EOL date: April 30, 2025
After April 30, 2025, all active Aiven for InfluxDB services are powered off and deleted, making data from these services inaccessible.
The recommended alternative for monitoring and observability of your applications and infrastructure is Aiven for Metrics.
Aiven for Caching
EOL date: March 31, 2025
After March 31, 2025, Aiven for Caching services are automatically upgraded to Aiven for Valkey™ to maintain Redis compatibility.
The recommended alternative that offers high performance, scalability, and security is the managed, in-memory NoSQL database service: Aiven for Valkey™.
Aiven for Apache Cassandra®
EOL date: January 7, 2026
Since January 7, 2026, Aiven for Apache Cassandra services are no longer available, and data they hosted is inaccessible.
Aiven for AlloyDB Omni
EOL date: December 5, 2025
Service impact
-
End of availability (EOA): September 5, 2025
After this date, you can no longer create new Aiven for AlloyDB Omni services. Existing services continue to operate until the end of life (EOL) date but you cannot change plans for these services.
-
End of life (EOL): December 5, 2025
On this date, all active Aiven for AlloyDB Omni services are powered off and deleted, making data from these services inaccessible.
Migration options
The recommended alternatives to Aiven for AlloyDB Omni are:
To ensure uninterrupted service, complete your migration before December 5, 2025. For further assistance, contact the Aiven support team or your account team.