mobile de
Documentation

De - Mobile

Every morning, before his first espresso, Lukas would open mobile.de , Germany’s largest online vehicle marketplace. It was more than a website to him; it was a digital treasure map. With over 1.6 million listings , the platform was a vast sea of steel and chrome, connecting him to thousands of dealers across Europe.

He used the platform’s integrated messaging system to contact the seller immediately. While he waited for a response, he checked the car's valuation and compared it to similar models using the site’s Automotive Intelligence tools . Everything checked out. mobile de

Standing in the dealership’s garage, the smell of old leather and oil was exactly as he’d imagined. The car was even better in person. He finalized the deal, thanks in part to the financing solutions he’d explored on the site earlier. Every morning, before his first espresso, Lukas would

By noon, the dealer called back. "You're the third person to ask," the man said, "but you were the first to message." Lukas didn't hesitate. He booked a train to Munich for the next morning. He used the platform’s integrated messaging system to

As Lukas drove the red Mercedes back toward Berlin, the rain cleared, and the sun began to set over the Autobahn. He wasn't just a man with a spreadsheet anymore; he was the lead in his own story, all thanks to a perfectly timed search on mobile.de.

New in InfluxDB 3.7

Key enhancements in InfluxDB 3.7 and the InfluxDB 3 Explorer 1.5.

See the Blog Post

InfluxDB 3.7 is now available for both Core and Enterprise, landing alongside version 1.5 of the InfluxDB 3 Explorer UI. This release focuses on giving developers faster visibility into what their system is doing with one-click monitoring, a streamlined installation pathway, and broader updates that simplify day-to-day operations.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2