Loading

Where is my Salesforce instance located?

Publiceringsdatum: Jul 31, 2026
Beskrivning

To determine your org’s instance, see View Instance Information for Your Salesforce Organization. To view details about your instance such as location and maintenance windows, visit my.trust.salesforce.com.

This article is applicable to services listed in Salesforce Services SPARC and Hyperforce SPARC. For information on security, privacy, and architecture for these and other services, see the Trust and Compliance Documentation.

Lösning

At Salesforce, our data center strategy supports the company's commitment to running the most trusted, secure, reliable, and available cloud computing service. Customer success drives our data center strategy, and delivering the highest standard in availability, performance, and security is our top priority. To avoid single points of failure, our infrastructure is built to serve each Salesforce instance from multiple geographically-diverse data centers. This design supports the continuous availability our customers expect from us.
 

Any stock-keeping unit (SKU) that includes functionality from the services listed in Salesforce Services SPARC and Hyperforce SPARC relies on a common collection of data and metadata (code and configurations for customizing Salesforce) called your “org” (short for “organization”). Each org belongs to a single “instance,” which is either one of the following: 

  • First-party infrastructure (owned and operated by Salesforce)
  • Hyperforce infrastructure (Salesforce-managed infrastructure hosted on public cloud providers AWS and GCP)

A customer’s org is hosted on a single infrastructure type. 

On Salesforce’s first-party infrastructure, your instance is actively served from one data center location, with transactions replicated asynchronously to a paired ready instance in a separate location. Salesforce regularly conducts site switches between these active and ready locations for maintenance, compliance, and disaster recovery.

On Hyperforce infrastructure, your instance uses an active/active model across three availability zones (AZs). A load balancer distributes incoming user requests across active application servers in all three AZs, while database replication maintains data consistency across zones. Salesforce regularly conducts proactive Game Day exercises and Chaos Engineering simulations—such as testing simulated availability zone failures—to validate system resilience and automatic failover. 

Across both infrastructure models, certain services can run on separate infrastructure while integrating directly with your org.

As we continue to expand and improve our global infrastructure presence, we recommend that customers build their applications free from specific data center requirements to support a seamless Salesforce experience.

We have Salesforce-managed data centers in the following metropolitan areas:

  • Amsterdam, Netherlands (NL)
  • Stockholm, Sweden (SE)
  • Tokyo, Japan (JPN)
  • Osaka, Japan (JPN)
  • Virginia, United States (USA):
    • Virginia North
    • Virginia South
       

In addition, we have Hyperforce instances served from public cloud infrastructure in the following regions. These instances are located in three separate availability zones within each respective country.

Salesforce Advanced Cross-Region Continuity is available for instances marked with an asterisk.

[Instance Prefix] - Country - Public Cloud Provider - Region Designation - Region Name (Location)

Asia Pacific

  • [AUSx] - Australia - AWS - ap-southeast-2 - Asia Pacific (Sydney)
  • [INDx] - India
    • AWS - ap-south-1 - Asia Pacific (Mumbai)*
    • AWS - ap-south-2 - Asia Pacific (Hyderabad)
  • [IDNx] - Indonesia - AWS - ap-southeast-3 - Asia Pacific (Jakarta)
  • [JPNx] - Japan
    • AWS - ap-northeast-1 - Asia Pacific (Tokyo)*
    • AWS - ap-northeast-3 - Asia Pacific (Osaka)
  • [SGPx] - Singapore - AWS - ap-southeast-1 - Asia Pacific (Singapore)
  • [KORx] - South Korea - AWS - ap-northeast-2 - Asia Pacific (Seoul)

Europe

  • [FRAx] - France - AWS - eu-west-3 - Europe (Paris)
  • [DEUx] - Germany
    • AWS - eu-central-1 - Europe (Frankfurt)*
    • GCP - europe-west10 - Europe (Berlin) - (Q1 2027, subject to our Safe Harbor disclosures)
  • [ITAx] - Italy - AWS - eu-south-1 - Europe (Milan)
  • [SWEx] - Sweden - AWS - eu-north-1 - Europe (Stockholm)
  • [CHEx] - Switzerland - AWS - eu-central-2 - Europe (Zurich)
  • [GBRx] - United Kingdom - AWS - eu-west-2 - Europe (London)

Israel & Middle East

  • [ISRx] - Israel - AWS - il-central-1 - Israel (Tel Aviv)*
  • [AREx] - United Arab Emirates - AWS - me-central-1 - Middle East (UAE)

Americas

  • [BRAx] - Brazil - AWS - sa-east-1 - South America (São Paulo)
  • [CANx] - Canada - AWS - ca-central-1 - Canada (Central)
  • [USAx] - United States of America
    • AWS - us-east-1 - US East (N. Virginia)*
    • AWS - us-east-2 - US East (Ohio)
    • AWS - us-west-2 - US West (Oregon)
    • GCP - us-central1 - US Central (Iowa) - (November 2026, subject to our Safe Harbor disclosures)
  • [USAx] - United States of America, Government Cloud
    • AWS - us-gov-east-1 (Ohio)
Knowledge-artikelnummer

000396845

 
Laddar
Salesforce Help | Article