# IONOS shuts down In-Memory DB v1, forcing a manual move to Valkey-based v2 IONOS has fully decommissioned In-Memory DB API v1. Customers that did not move must provision a new v2 instance, migrate persistent data and update endpoints manually; the replacement is Valkey-based and new snapshot pricing starts September 1. This is a hard managed-database migration rather than a soft deprecation. IONOS says automatic migration is impossible, v1 instances are switched off, and applications need new v2 endpoints even though Valkey remains compatible with standard Redis clients. - Status: Active - Published: 2026-09-01T20:38:59+12:00 - Updated: 2026-09-01T20:38:59+12:00 - Categories: Cloud & Infrastructure, Cloud Platforms, Databases & Storage - Tags: API deprecation, database migration, IONOS, Redis compatibility, Valkey - Canonical HTML: https://beyondthe.news/dossiers/ionos-in-memory-db-v1-shutdown-valkey-v2-migration ## What changed 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. ## Why it matters 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. ## The old service is no longer just deprecated 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. ## The migration cannot happen in place 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. ## Valkey reduces application-code disruption 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. ## The economics change after migration too 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. ## Key details - IONOS disabled creation of new v1 clusters on August 4, 2026. - In-Memory DB v1 reached full end of life on August 31, 2026. - IONOS says remaining v1 instances are permanently switched off. - Automatic migration from v1 to v2 is not available. - Customers must provision v2, migrate persisted data if required and update application endpoints. - The v2 platform is based on Valkey and remains compatible with standard Redis clients and tools. - New pricing for v2 snapshot features takes effect September 1, 2026. ## Builder takeaways - If any IONOS In-Memory DB v1 dependency remains, treat it as an outage-risk incident rather than a future migration task. - Provision v2 and update connection endpoints even if your application uses ordinary Redis-compatible clients. - Move persisted data explicitly; do not assume IONOS copied it automatically. - Re-test TLS, authentication, persistence and failover behavior after endpoint changes. - Review v2 snapshot and observability pricing so the migration does not create an unnoticed cost increase. ## What to watch - Post-cutoff incident reports from customers that missed the migration. - Updated v2 documentation replacing remaining legacy In-Memory DB pages. - The practical cost of new snapshot retention and optional observability at scale. ## Uncertainties - IONOS documentation surfaces are transitioning and some pages still describe legacy Redis-compatible v1 details, so operators should rely on the current v2 migration/status guidance for the cutoff. - Exact snapshot charges vary by IONOS pricing context and are not fully enumerated in the status notice. ## Sources - [Action Required: IONOS In-Memory DB API v1 Full Deprecation](https://status.ionos.cloud/) — IONOS CLOUD Status · primary status notice · 2026-08-13T00:00:00+12:00. Primary source for the August 31 shutdown, mandatory migration steps, Valkey v2 architecture and September snapshot pricing. - [In-Memory DB](https://docs.ionos.com/cloud/databases/in-memory-db) — IONOS Cloud Docs · primary documentation. Current product documentation for In-Memory DB access and operational model.