Is Salesforce Down: Status Checks | SalesforceTutorial

Written by Prasanth Kumar Published on Updated on

SalesforceTutorial > Salesforce > Is Salesforce Down

Is Salesforce Down? How to Check Salesforce Status

Is Salesforce down can mean a Salesforce platform incident, scheduled maintenance, an identity provider failure, a corporate network block, profile login restrictions, or one slow Lightning page. Start with the official Salesforce status for your org, then test My Domain, SSO, network access, login policy, and API response before you call it an outage.

In enterprise orgs, the best answer to “is Salesforce down” is evidence-based, and an is Salesforce down runbook should be short enough to use during a live incident. You need to know whether the impact is platform-wide, instance-specific, product-specific, network-specific, or limited to one user group.

Is Salesforce Down? First Checks for Admins

Use this is Salesforce down checklist before you send an incident update. It keeps the team from blaming Salesforce when the issue is really SSO, VPN, browser state, or profile access.

Symptom Likely cause First check
Users in several locations cannot open Salesforce, and integrations fail Instance or service incident Check Salesforce Trust by My Domain or instance
Only office or VPN users fail Proxy, DNS, firewall, ISP, or SSL inspection Test My Domain from another network
Only one profile or team fails Login hours, login IP ranges, SSO policy, or user state Review profile login settings and identity logs
Only one record page is slow Lightning page design or client-side component load Run Lightning App Builder page analysis
UI works but API jobs fail OAuth, connected app, API limits, endpoint, or integration user Run an authenticated REST API check

How to Check Salesforce Status on Trust

The official source for Salesforce status is the Salesforce Trust Status experience. Search by My Domain or instance, then review the exact service affected. A Sales Cloud issue, Service Cloud issue, Marketing Cloud tenant issue, Experience Cloud site issue, or Data Cloud service issue can have different impact.

Use the official Salesforce Trust Status overview when you need Salesforce guidance for reading incidents, service messages, maintenance, and history. When users ask is Salesforce down, Trust should be the first external source you check.

Find Salesforce status by My Domain

  1. Open the Trust Status site and search for the org My Domain, such as acme.my.salesforce.com. Do not paste usernames, session IDs, or full record URLs into public pages.
  2. Confirm the instance, product, and service. A sandbox and production org can sit on different instances.
  3. Review current incidents, performance degradation, service disruption, scheduled maintenance, and recent history.
  4. Subscribe to Trust notifications for critical instances so the team does not rely on manual checks.

Use trust.salesforce.com when your instance is unclear

trust.salesforce.com is a common search query, but admins should search for the exact org. Salesforce Help defines My Domain as the org-specific subdomain used for login and application URLs. Keep production and sandbox My Domain values in your incident runbook so the is Salesforce down investigation starts with the right target.

For official URL behavior, review My Domain login and application URL formats. This matters for bookmarks, SSO redirects, integrations, and user instructions.

How to Decide If Salesforce Is Down for Only One User

If Salesforce status is green, the is Salesforce down report may still be real for one user, one office, or one business unit. Start with the controls closest to the affected user.

Check login hours and profile IP ranges

Salesforce admins can set login hours and login IP ranges on profiles. If the user cannot log in after a shift change, check profile login hours. If the user moved to hotel Wi-Fi, home broadband, or mobile tethering, compare the public IP address with the allowed profile ranges.

Use the official Salesforce Help article for restricting login IP addresses in profiles when you need to confirm behavior. Also check user status, permission set assignments, and identity provider logs before changing org-wide security settings.

Check SSO, MFA, browser, and network path

When only SSO users fail, Salesforce may be reachable while the identity provider is not. Test a permitted admin login path, review SSO logs, and determine whether the error happens before or after Salesforce receives the authentication response. If one browser fails, try another browser profile, an incognito session, and the Salesforce mobile app if policy permits it.

How Developers Can Test Is Salesforce Down Safely

Developers should not build aggressive polling jobs to answer is Salesforce down. Use low-frequency checks that verify reachability, authentication, and a lightweight API response without adding load during an incident.

Run a My Domain reachability check

MY_DOMAIN='https://acme.my.salesforce.com'
curl --head --location --max-time 10 $MY_DOMAIN

An HTTP 200 or 302 means the login route responded. It does not prove every Salesforce service is healthy. A timeout, DNS error, or TLS error points to the client network, proxy, DNS, firewall, or a wider routing problem.

Run an authenticated REST API check

The Salesforce REST API versions resource lists API versions available to the org, and the limits resource lists current org limits. The example uses the REST URL pattern; replace v61.0 with a version returned by /services/data/ for your org.

ORG_ALIAS='prod'
API_VERSION='v61.0'
ACCESS_TOKEN=$(sf org display --target-org $ORG_ALIAS --json | jq -r '.result.accessToken')
INSTANCE_URL=$(sf org display --target-org $ORG_ALIAS --json | jq -r '.result.instanceUrl')
curl --silent --show-error --fail --header 'Authorization: Bearer '$ACCESS_TOKEN $INSTANCE_URL/services/data/$API_VERSION/limits

Do not hardcode tokens in scripts. Store secrets in an approved vault, use connected app policy correctly, and monitor API consumption. If UI login works but this request fails, check OAuth, connected app settings, the integration user, API limits, and endpoint routing before concluding that Salesforce is down.

How to Use Downdetector Salesforce Reports

Downdetector Salesforce reports can help you see whether many users are reporting trouble, but they are not the official record of Salesforce availability. Use them as a secondary signal after Salesforce Trust and your own org checks.

Downdetector salesforce is not the source of truth

A spike in downdetector salesforce reports cannot prove that your Sales Cloud instance, sandbox, Marketing Cloud tenant, Experience Cloud site, Data Cloud service, or API endpoint is affected. Confirm the product and instance on Salesforce status before you send a business update.

Best Practices for Salesforce Status Monitoring

  • Document org identifiers. Keep production and sandbox My Domain names, instance names, critical services, and support contacts in one runbook.
  • Subscribe to Trust notifications. Salesforce documents subscriptions for service disruption, performance degradation, and maintenance activity.
  • Separate UI, API, and SSO checks. A login page check, REST API check, and identity provider check answer different questions.
  • Limit automated checks. Run checks at a reasonable interval such as every 5 to 15 minutes unless your monitoring policy requires something else.
  • Pause risky work during confirmed incidents. Stop nonessential deployments, bulk imports, and scheduled integrations when Salesforce status shows disruption for your instance.

For related operational work, see Salesforce outage response, Salesforce Data Loader job control, Salesforce reports for admin monitoring, and Salesforce Chrome extension troubleshooting.

Common Errors When Salesforce Is Not Actually Down

  • Profile restrictions: Login hours or login IP ranges block users outside the allowed time or network.
  • SSO misconfiguration: Certificate expiry, IdP outage, wrong ACS URL, or attribute mapping issues block authentication.
  • Browser state: Cookies, extensions, blocked storage, or stale redirects can break one browser profile.
  • VPN and proxy inspection: SSL inspection can interrupt Lightning resources even when basic login works.
  • Integration user problems: Revoked refresh tokens, connected app policy changes, password expiry, or API limits can stop jobs while the UI works.
  • Slow Lightning page: Custom components, too many related lists, or unmanaged client-side work can make one page feel unavailable.

Incident Response Checklist

  1. Define scope: users, profiles, locations, browsers, mobile users, API clients, and Experience Cloud users.
  2. Capture evidence: error text, URL, timestamp, screenshot, failed job ID, and affected service.
  3. Check Salesforce status by My Domain or instance.
  4. Test SSO, MFA, VPN, DNS, proxy, profile login hours, and profile IP ranges.
  5. Pause avoidable deployments, metadata changes, data loads, and scheduled jobs.
  6. Tell users whether the issue is platform-wide, instance-specific, network-specific, or user-specific.

The safest answer to “is Salesforce down” is simple, and the is Salesforce down decision should not depend on one screenshot: check Salesforce Trust, test the org path, confirm access controls, compare UI and API results, and communicate only what the evidence supports.

Frequently Asked Questions

Is Salesforce down right now?

Check Salesforce status for your My Domain or instance. That is the first step when you need to answer is Salesforce down right now. If Trust shows no matching issue, test login hours, IP ranges, SSO, browser state, and network access.

What is the official Salesforce status page?

The official source is Salesforce Trust Status. Users often search for trust.salesforce.com, but admins should search by the exact My Domain or instance to confirm service impact, maintenance, and history.

Should I use downdetector salesforce reports?

Use downdetector salesforce reports only as a secondary signal. They can show report volume, but they do not confirm whether your Salesforce instance or product service has an official incident.

Why can one user not log in when Salesforce status is green?

The user may be blocked by profile login hours, profile IP ranges, SSO policy, MFA failure, browser state, VPN routing, or user account status. A green Salesforce status result does not prove every user path works.

Can Salesforce API jobs fail while the UI works?

Yes. API jobs can fail because of OAuth token issues, connected app policies, API limits, integration user status, endpoint changes, or network rules. Run an authenticated REST check before concluding that Salesforce is down.