IONOS shuts down In-Memory DB v1, forcing a manual move to Valkey-based v2

IONOS completed the end-of-life of its In-Memory DB API v1 on August 31, 2026. The company says all remaining v1 instances are permanently switched off. Because the v2 architecture is different, there is no automatic migration. Customers must create a v2 instance, move persistent data where needed, and update application connection strings. The new service is based on Valkey and supports Valkey 8, 8.1 and 9 according to the migration notice. Snapshot pricing for v2 begins September 1.

A managed cache/database service can look like a drop-in component until the provider changes its control plane and underlying engine generation. IONOS is making that dependency explicit: Redis-compatible clients may continue working, but the infrastructure itself must be reprovisioned and endpoints changed. Any team that missed the deadline risks immediate service interruption, while teams already migrated should still account for the new snapshot-pricing model.

IONOS describes August 31 as full decommissioning of In-Memory DB v1, not merely an API write cutoff. Remaining v1 instances are switched off, turning an ignored migration notice into an availability problem.

IONOS says the architecture changed enough that automatic migration is not possible. Customers need to provision a new v2 instance, transfer data when persistence matters and then repoint applications to the new endpoint.

The replacement service is built on Valkey, the Linux Foundation-backed Redis-compatible datastore. IONOS says standard Redis clients and tools continue to work, so the main migration burden is infrastructure and data movement rather than wholesale application rewrites.

IONOS says enhanced v2 snapshot capabilities were included before the cutoff but standard snapshot pricing begins September 1. Teams should therefore validate both successful migration and the new recurring cost profile.