> 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/release-notes/july-2026.md).

# July 2026

<a href="https://release-notes-feed.s3.eu-central-3.ionoscloud.com/feed.rss" class="button primary" data-icon="rss">Subscribe via RSS feed</a>

## What's new

### [<mark style="color:blue;">**DBaaS MariaDB v2 API in General Availability**</mark>](https://api.ionos.com/docs/mariadb/v2/)

{% hint style="success" %}
**July 6**

The <code class="expression">space.vars.ionos\_cloud</code> **DBaaS MariaDB v2 API** is now in General Availability (GA). The v2 API is available across all nine <code class="expression">space.vars.ionos\_cloud</code> regions: Berlin, Frankfurt, Paris, Logroño, London, Worcester, Las Vegas, Lenexa, and Newark.

Any <code class="expression">space.vars.ionos\_cloud</code> contract can provision MariaDB v2 clusters without prior activation. The v2 API introduces token-based authentication (Bearer JWT), dedicated `BackupLocations` and `Versions` endpoints, Point-in-Time Recovery (PITR) through `restoreFromBackup` with `sourceBackupId` and `recoveryTargetDatetime`, configurable backup retention from 1 to 365 days through `backup.retentionDays`, and observability controls (`logsEnabled`, `metricsEnabled`). For detailed information, see [<mark style="color:blue;">DBaaS MariaDB v2 Cloud API</mark>](https://api.ionos.com/docs/mariadb/v2/).

{% hint style="info" %}
**Important:** The [<mark style="color:blue;">MariaDB v1 API</mark>](/cloud/databases/mariadb/api/v1-api.md) will be deprecated in an upcoming release. All existing v1 clusters will be automatically migrated to v2 with no user action needed. We recommend creating new clusters using MariaDB v2 [<mark style="color:blue;">endpoints</mark>](https://api.ionos.com/docs/mariadb/v2/) to leverage the new capabilities.
{% endhint %}
{% endhint %}

### [<mark style="color:blue;">**Support for Kafka version 4.0.0**</mark>](/cloud/data-analytics/kafka.md)

{% hint style="success" %}
**July 1**

Event Streams for Apache Kafka service will now support Kafka version 4.0.0 starting July 1, 2026.
{% endhint %}

## Deprecations

### [<mark style="color:blue;">**Deprecation of Kafka version support 3.9.0 and 3.9.1**</mark>](/cloud/data-analytics/kafka/overview.md#supported-kafka-versions)

{% hint style="success" %}
**July 1**

Effective July 1, Event Streams for Apache Kafka versions 3.9.0 and 3.9.1 are deprecated. Existing Kafka clusters using these versions will continue to operate and are unimpacted by this change. However, we recommend using **version 4.0.0** for new Kafka clusters.
{% endhint %}

### [<mark style="color:blue;">**AI Model Studio End of Life**</mark>](#ai-model-studio-end-of-life)

{% hint style="success" %}
**July 1**

Effective July 1, <code class="expression">space.vars.ionos\_cloud</code> no longer supports AI Model Studio. The product has reached end of life and is no longer available. If you are looking for AI inference capabilities, see [<mark style="color:blue;">AI Model Hub</mark>](/cloud/ai/ai-model-hub.md).
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ionos.com/cloud/release-notes/july-2026.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.