Salesforce Status Guide for Admins
Salesforce status tells you whether a Salesforce product, service, instance, or maintenance event is affecting your org. Start with the official Salesforce Status site, confirm your instance, and compare user reports with incident details before you change code, permissions, integrations, or network settings.
This guide gives admins, developers, architects, and support leads a repeatable way to answer the incident question: is the problem in our org, in our network, or on the Salesforce service layer?
What is Salesforce Status?
Salesforce status is the public health view for Salesforce products and infrastructure. It shows availability, instance health, planned maintenance, service messages, and incident updates. Salesforce Help describes the Trust site as the place Salesforce uses for availability, performance, security, privacy, and compliance information.
Do not treat a Salesforce status check as one green-or-red page. A product can be available while a service is slow, one instance can be affected while another is not, and scheduled maintenance can explain behavior that users report as an outage.
| Status signal | Meaning | Admin action |
|---|---|---|
| Available or OK | No current Salesforce-posted incident for the selected product or instance. | Continue org checks: SSO, permissions, deployments, browser console, API limits, and integration logs. |
| Performance Degradation | The service is reachable, but one or more functions are slower or inconsistent. | Capture affected URLs, timestamps, profiles, apps, and business processes. Avoid retry storms. |
| Service Disruption | A service or instance has an availability problem that can block work. | Move to the outage runbook, pause noncritical jobs, and send user updates. |
| Maintenance | Salesforce has scheduled work for an instance, product, or service. | Compare the window with release, batch, and integration schedules. |
How to check Salesforce Status for your org
Checking the generic home page is not enough. Your users work on a specific tenant, instance, product set, authentication path, and integration chain.
Find your Salesforce instance
Salesforce Help lists ways to identify your instance, including Company Information, DNS lookup, and Salesforce Status. In Lightning Experience, go to Setup → Company Information and record the instance name, organization ID, and My Domain URL. Keep those values in the support runbook.
Open the tenant or instance status page
Use status.salesforce.com and search with your My Domain or instance key. Salesforce documents a workflow that reports status information based on your instance and lets you use your My Domain name when you do not know the instance.
Check current status, incident details, maintenance, and history. Open the incident detail page when one exists because the detail usually shows affected services, posted updates, and timestamps.
Compare status with user evidence
A Salesforce incident and an org configuration problem can happen at the same time. Capture exact timestamps, My Domain, instance key, org ID, affected users, profile or permission set, app, object, record ID, browser, device, VPN state, and recent deployments.
What to do when salesforce is down
When users say salesforce is down, do not start with random fixes. First prove the scope. In enterprise orgs, the first 15 minutes should separate platform impact from local SSO, DNS, VPN, permission, integration, or deployment issues.
How to respond when salesforce is down
- Confirm the user path. Test direct login, SSO login, mobile access, and API access separately.
- Check the official status page. Filter by the affected instance and product.
- Run a control test. Ask one admin on another network to open the same app or record.
- Pause nonessential automation. Stop repeated data loads, manual resubmits, and scheduled integrations if they add load.
- Send a user note. State what is affected, what still works, what not to retry, and when the next update will arrive.
Do not ask every user to clear cache, reset passwords, or change browsers when the official incident shows service disruption. Those steps waste time during a confirmed platform issue.
How to diagnose Salesforce performance degradation
Salesforce performance degradation means Salesforce is reachable, but one or more actions are slow, intermittent, or timing out. It can overlap with Flow changes, Apex triggers, reports, browser extensions, integration load, API limits, and network latency.
How to confirm a salesforce performance degradation
Start with the official instance status, then test the exact transaction. Reports can time out while record pages load, and API calls can slow while the UI works. Record the affected service rather than only the application name.
- Reports and dashboards: Check filters, row counts, custom report types, joined reports, and dashboard refresh schedules. See Salesforce reports troubleshooting if the status page is green.
- API integrations: Check the
/limitsresource, API usage notifications, connected app identity, and retry behavior. Salesforce Developer guidance explains that API usage is tracked against Daily API Request Limit and monthly entitlement. - Automation: Review recent Flow, Apex trigger, validation rule, sharing recalculation, and deployment changes.
REST check for API limits during a slowdown
Use this from a controlled admin workstation or monitoring host. Replace the API version with one supported by your org; the example uses v60.0, available from Spring ’24.
MY_DOMAIN=https://example.my.salesforce.com; ACCESS_TOKEN=replace-with-oauth-access-token; curl -s $MY_DOMAIN/services/data/v60.0/limits -H 'Authorization: Bearer '$ACCESS_TOKEN -H 'Accept: application/json' | jq '.DailyApiRequests'If the remaining daily API count is near zero, the symptom can be an org limit issue rather than a Salesforce service issue.
How to handle an sfdc outage
An sfdc outage needs a runbook because users will ask through Slack, email, phone, and the service desk at the same time. The support lead should not invent the process during the incident.
Sfdc outage runbook for admins and architects
| Runbook item | Owner | Purpose |
|---|---|---|
| Instance and product map | Salesforce admin | Shows which orgs, sandboxes, products, and integrations map to each instance. |
| Business impact list | Product owner | Translates technical impact into sales, service, billing, and operations language. |
| Integration pause plan | Integration owner | Prevents duplicate orders, repeated messages, and retry storms. |
| User message template | Support lead | Keeps communication consistent and avoids root-cause guesses. |
For regulated environments, keep the official incident link, internal ticket, and exact user-facing impact statement. Do not write a root cause until Salesforce publishes one or your team proves an internal cause.
Should you use downdetector salesforce reports?
downdetector salesforce reports can help you notice a wider pattern, but they are not the source of record for service health. Use them as a signal, not as proof that your instance is affected.
Downdetector salesforce signals versus official status
User-reported outage sites can include ISP failures, identity provider outages, local network issues, or browser problems. A spike in reports should make you investigate faster. It should not replace Salesforce Status, Salesforce Support, or your own monitoring.
Use this order of trust: Salesforce Status incident detail, your synthetic tests, integration monitoring, Salesforce Support case updates, then community or third-party reports.
How developers can monitor Salesforce Status with the Trust API
Salesforce exposes a Trust API at api.status.salesforce.com/v1/docs. The API documentation lists the base path and status endpoints such as /instances/{key}/status. Run this check from an external monitoring system, not from Apex inside the org you are trying to monitor.
Basic Trust API check
INSTANCE_KEY=NA123; curl -s https://api.status.salesforce.com/v1/instances/${INSTANCE_KEY}/status -H 'Accept: application/json' | jq '{key, status, Incidents, Maintenances}'Replace NA123 with your instance key. Treat the response as an operational signal and keep a human review step for major incidents.
Best practices for Salesforce Status communication
The best incident message is short and specific. Tell users what is affected, what still works, what not to retry, and when the next update will arrive.
Subject: Salesforce service issue affecting [process] | Instance: [instance key] | First reported: [time with timezone] | Official Salesforce Status: [incident or current status link] | Business impact: [short statement] | Workaround: [workaround or none confirmed] | Next update: [time]During a confirmed platform event, keep the Salesforce status message factual. Avoid unsupported words such as data loss, breach, or root cause unless Salesforce or your internal evidence proves them.
Common errors with Salesforce Status checks
Assuming one green page means every service is healthy
Check the affected product, instance, and service. A Service Cloud user can see different behavior from a Marketing Cloud, Tableau Cloud, or MuleSoft user.
Confusing Salesforce errors with local integration errors
REST API responses such as HTTP 502 and 503 can indicate upstream or availability problems, but a single response code does not prove a broad outage. Compare timing with Salesforce Status, retry behavior, logs, and deployment history. See the Salesforce API integration guide for integration checks.
Ignoring scheduled maintenance
Subscribe to Trust notifications for production and critical sandboxes, then add those windows to release calendars.
Related SalesforceTutorial resources
- How to find your Salesforce instance
- Salesforce API integration guide
- Salesforce Data Loader troubleshooting
- Salesforce reports troubleshooting
Frequently Asked Questions
How do I check Salesforce status for my org?
Open Salesforce Status, search by your My Domain or instance, and review current incidents, maintenance, and service history. If you do not know your instance, check Setup → Company Information or use the Salesforce Help guidance for finding instance information.
What should I do if salesforce is down for users?
Confirm the scope before changing settings. Test direct login, SSO, API access, and one control user on a different network. Then check Salesforce Status for your instance, pause noncritical integrations, and send a clear user update with the affected process and next update time.
What is Salesforce performance degradation?
Salesforce performance degradation means the service is reachable but one or more features are slower, intermittent, or below normal service behavior. It can affect a product, service, or instance, so admins should compare official status with user evidence and internal monitoring.
Is downdetector salesforce data reliable for outage decisions?
downdetector salesforce reports are useful as an early signal, but they are not authoritative. Use them to decide whether to investigate faster, then rely on Salesforce Status, Salesforce Support, and your own monitoring for incident decisions.
Can I monitor Salesforce Status with an API?
Yes. Salesforce provides the Trust API at api.status.salesforce.com. Use it from an external monitoring platform and query the status endpoint for your instance key. Do not depend only on an Apex job inside the same org because org runtime problems can break the monitor.