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.
Gotchas
- 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.