> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/databases/in-memory-db/overview/limitations.md).

# Limitations

## In-Memory DB v2

The following are a few limitations that you can encounter while using In-Memory DB v2:

* A cluster can have between 1 and 5 instances. Adding or removing instances after cluster creation is not supported.
* A single instance can have between 1 and 62 dedicated CPU cores, depending on your quota.
* A single instance can have between 4 and 240 GB of RAM, depending on your quota.
* Block storage is derived automatically from the configured RAM and persistence mode; it cannot be set manually and cannot be downsized.
* Snapshot retention is configurable between 1 and 365 days (default: 7).
* RAM cannot be downgraded after the cluster is created.

## In-Memory DB v1

The following are a few limitations that you can encounter while using In-Memory DB v1:

* You cannot use multiple In-Memory DB instances simultaneously, but each for a particular use case.
* You have access to ten default In-Memory DB instances, which are numbered to differentiate them. However, adding or renaming the instances after creation is impossible.
* The total upper limit for CPU cores depends on your quota. A single instance cannot exceed 16 cores.
* The total upper limit for RAM depends on your quota. A single instance cannot exceed 32 GB.
* The upper limit for storage size is 2 TB.
* Storing In-Memory DB instance backups in an <code class="expression">space.vars.ionos\_cloud\_object\_storage</code> is limited to the last seven days.

## Shared limitations

The following IP addresses cannot be used with In-Memory DB services:

* `10.208.0.0/12`
* `10.233.0.0/18`
* `192.168.230.0/24`
* `10.233.64.0/18`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ionos.com/cloud/databases/in-memory-db/overview/limitations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.