Instance
An Instance in Salesforce is the physical pod (a cluster of servers and a shared database) where a Salesforce organization runs.
Definition
An Instance in Salesforce is the physical pod (a cluster of servers and a shared database) where a Salesforce organization runs. Historically, instances had identifiers like NA1, NA12, EU3, AP2 (continent + sequence number), and the URL of a Salesforce org reflected its instance (na1.salesforce.com, eu3.salesforce.com). Multiple customer orgs share a single instance, with logical separation enforced at the application layer. Salesforce maintenance windows, release schedules, and outage notifications are scoped to an instance.
With Hyperforce, the instance concept has shifted. Hyperforce orgs run on public-cloud regions (AWS US-East, AWS EU-West, AWS Asia-Pacific) instead of named pods. The URL switches to the org''s My Domain (companyname.my.salesforce.com), and the legacy NAxx hostnames become redirects. Despite the shift, the instance term still appears in admin contexts: status.salesforce.com tracks instance-level uptime; release-preview decisions still reference instance pods for pre-Hyperforce orgs; and the User Interface API exposes an Instance Name field for diagnostic and integration purposes.
The instance concept from legacy pods to Hyperforce
Legacy instance naming
Pre-Hyperforce Salesforce orgs lived on named pods: NA1, NA12, NA45 for North America; EU3, EU45 for Europe; AP1, AP12 for Asia-Pacific; CS1, CS45 for sandboxes. Each pod was a cluster of servers and a shared database hosting thousands of customer orgs. The URL identified the pod (na1.salesforce.com), as did the User.UserPreferencesShowSalesforceLogin host header.
Hyperforce regions vs. legacy pods
Hyperforce replaces named pods with public-cloud regions (AWS USE1, EUW1, APAC1). Orgs provisioned on Hyperforce do not have a NAxx-style identifier; their hostname is purely the My Domain. Pre-2023 orgs still on legacy pods are being migrated to Hyperforce on a multi-year schedule managed by the Hyperforce Assistant.
status.salesforce.com
Salesforce Trust (status.salesforce.com) is the public status page that tracks uptime, incidents, and maintenance windows per instance. Admins bookmark the page filtered to their org''s instance for fast incident lookup. The page also publishes release dates and sandbox-preview windows, both scoped to instance.
Release timing per instance
Salesforce ships three major releases per year (Spring, Summer, Winter). Each release rolls out to instances on a staggered schedule over several weeks. Some instances get the new release on the first weekend (Sandbox Preview Week 1), others get it weeks later (Production Week 4-5). The schedule is published in advance on the release notes site so customers can plan testing.
Instance-aware integration design
Integrations that hardcoded the instance hostname (na1.salesforce.com) break when an org migrates to a new pod or to Hyperforce. The fix is to use My Domain or the Salesforce-supplied dynamic instance URL APIs. The integration code should resolve the current instance at runtime, not assume a fixed hostname.
Sandbox instance assignment
Sandboxes historically lived on dedicated CS pods (CS1, CS22). A sandbox could be on a different pod from its production parent, which sometimes affected refresh and connectivity. Hyperforce changes this; sandboxes and production now live in the same region by default.
The Instance Name field
Organization.InstanceName is the SOQL-queryable field that returns the current instance identifier. Use it for diagnostic logging, support escalations, and conditional logic in code that needs to know which pod (or Hyperforce region) the org is on. Hyperforce orgs return a region-style identifier like USA2S in this field.
Identify and work with your org instance
Knowing your org''s instance is essential for incident lookup, release timing, and integration troubleshooting.
- Check Setup, Company Information
The Instance Name field shows the current pod or Hyperforce region.
- Bookmark status.salesforce.com for your instance
Open status.salesforce.com, search for your instance, bookmark the page. Use it as the first stop during any suspected outage.
- Subscribe to instance maintenance notifications
Create a Trust account and subscribe to maintenance-window emails for your instance.
- Audit hardcoded URLs in integrations
Search integration code for any references to NAxx.salesforce.com or similar hardcoded hostnames. Replace with My Domain references.
- Watch the release schedule
Each Salesforce release publishes per-instance dates. Use the dates to plan sandbox testing windows and production cutover.
- Hardcoded NAxx hostnames in integration code break on pod moves and Hyperforce migration. Always use My Domain or dynamic instance resolution.
- The Hyperforce migration changes the underlying region but typically preserves My Domain. Integrations that use My Domain survive the migration cleanly.
- Maintenance windows are per-instance; one customer can be in a release weekend while another customer on a different instance is not. Don''t assume coordinated downtime across the whole platform.
- Sandboxes on different pods from production can have different refresh windows. Coordinate with the Salesforce account team during a refresh planning.
Trust & references
Cross-checked against the following references.
- Salesforce TrustSalesforce
- Hyperforce OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Instance.
- Organization ObjectSalesforce Developers
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Salesforce Instance?
Q2. Where can you check instance status?
Q3. What's gradually replacing the traditional instance model?
Discussion
Loading discussion…