Regions

Platform.sh offers several regions for hosting project data. You can choose a region based on criteria such as its closeness to your users and its environmental impact.

Environmental impact

At Platform.sh, we are committed to reducing our environmental impact. Whenever you create a project with us, we provide information about the electricity grid provider for that region. You can view the average carbon intensity of the energy grid in grams of CO2 equivalent per kilowatt-hour. These data are sourced from an annual average, which we update as new information becomes available. If you want to see real-time emissions generated by each power grid, we recommend checking out Electricity Maps. You can also access a public GitHub page of Electricity Maps data sources.

Summary of data being used in Platform.sh’s Region Picker when creating a new Project:

Information on carbon intensity is also available in the Platform.sh API. For example, to get a list of the regions and their carbon intensities, run the following command:

platform api:curl regions | jq -r '.regions[] | select(.available) | .label + ": " + .environmental_impact.carbon_intensity'

See all available information in the API documentation.

Region availability

The regions listed here may be different from those available to you when you create a new project. Each organization can have its own rules for what regions to allow. When adding a new project, you only see regions allowed by your organization.

Region location

To find out where a given region is hosted, use the following command:

platform api:curl regions | jq '.regions[] | select(.available)  | .id + ": " + .provider.name + " - " + .zone + " - " + .timezone' | sort

The returned list contains, for each available region, its name, provider, geographic zone and its timezone.

Public IP addresses

The public IP addresses for regions are stable, but not guaranteed to never change. Before any change, you are notified well in advance regarding affected projects. Planned and upcoming changes to IPs will be documented in the Upcoming changes section below.

They’re useful for cases such as when you have a corporate firewall that blocks outgoing SSH connections. In such cases, add the inbound IP addresses for your region to your allow list.

Regions

Europe

United States

Canada

Australia

Upcoming changes

GCP and Azure regions outbound IPs

On the 17th of March 2025, Outbound IPs on all GCP and Azure regions will change. Customer projects that refer to outbound IPs explicitly in their code and/or configuration must intervene and update to the New outbound IPs as soon as is possible.

Before the 17th of March, no traffic go through the New outbound IPs. After the 17th of March, the Old outbound IPs will no longer be available. Allowing both new and old IP addresses in any configuration during the transition period is recommended.

How to audit the potential impact on an organization

You can determine which of your project are potentially impacted by this change via the CLI or the Console.

platform project:list -o ORG_NAME --region=REGION

curl -s https://raw.githubusercontent.com/platformsh/snippets/region-audit/src/region-audit.sh | bash -s -- ORG_NAME ch-1,uk-1,de-2,us-4,fr-4,us-3,au-2 platform

Not every project listed in this audit will necessarily be impacted by the change, only those that are explicitly using the outbound IPs in some way.