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.
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:
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:
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
Europe
Israel & Middle East
Americas
000396845

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.