Documentation

InfluxDB Cloud regions

InfluxDB Cloud is available on multiple cloud providers and in multiple regions. Each region has a unique InfluxDB Cloud URL and API endpoint. Use the URLs below to interact with your InfluxDB Cloud instances with the InfluxDB API, InfluxDB client libraries, influx CLI, or Telegraf.

Request a cloud region

Regions with multiple clusters

Some InfluxDB Cloud regions have multiple Cloud clusters, each with a unique URL. To find your cluster URL, log in to your InfluxDB Cloud organization and review your organization URL. The first subdomain identifies your InfluxDB Cloud cluster. For example:

https://us-west-2-1.aws.cloud2.influxdata.com/orgs/03a2bbf46249a000/...

Amazon Web Services (AWS)

RegionLocationURL(s)
US West (Oregon)Oregon, USA

us-west-2-1: https://us-west-2-1.aws.cloud2.influxdata.com

us-west-2-2: https://us-west-2-2.aws.cloud2.influxdata.com

US East (Virginia)Virginia, USAhttps://us-east-1-1.aws.cloud2.influxdata.com
EU FrankfurtFrankfurt, Germanyhttps://eu-central-1-1.aws.cloud2.influxdata.com

Google Cloud Platform (GCP)

RegionLocationURL(s)
US Central (Iowa)Iowa, USAhttps://us-central1-1.gcp.cloud2.influxdata.com

Microsoft Azure

RegionLocationURL(s)
West Europe (Amsterdam)Amsterdam, Netherlandshttps://westeurope-1.azure.cloud2.influxdata.com
East US (Virginia)Virginia, USAhttps://eastus-1.azure.cloud2.influxdata.com

Was this page helpful?

Thank you for your feedback!


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

InfluxDB Cloud powered by TSM