Skip to content

Is Salesforce down?

Salesforce publishes no status we can read

Right now

Unknown. No machine-readable official status; see their status page.

No official machine-readable status

For agents

proceed

Proceed.

GET upbutler.com/status/salesforce/status.agent.json

MCP: upstream_status {"service":"salesforce"}

Salesforce instances and platform APIs. Status is per instance on its own Trust site.

What Salesforce says

api.status.salesforce.com has no public JSON API or feed we may read, and there is no keyless endpoint that says anything useful.

Their site: api.status.salesforce.com

What UpButler measured

There is no keyless endpoint of Salesforce that says anything useful, so UpButler does not probe it. To check your own Salesforce account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Salesforce incidents, last 90 days

Without a machine-readable source there is no incident history to show. Salesforce keeps its own at api.status.salesforce.com.

Get alerted when Salesforce goes down

Salesforce publishes no incidents we can read, so there is nothing to send an alert about. If you depend on it, monitor your own use of it: add a monitor with your key or URL.

Status badge

Show Salesforce's current status in a README or an internal wiki. It updates by itself.

Salesforce status badge

[![Salesforce status](https://upbutler.com/status/salesforce/badge.svg)](https://upbutler.com/status/salesforce)

Tell your outage from Salesforce's

Declare that your project depends on Salesforce. When one of your monitors fails while Salesforce has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

upbutler.yaml
# upbutler.yaml
dependencies:
  - salesforce
Ask before you retry
curl -s https://upbutler.com/status/salesforce/status.agent.json
status.agent.json (live)
{
  "schema": "upbutler.upstream-status/v1",
  "service": "salesforce",
  "verdict": "proceed",
  "status": "unknown",
  "reason": "No machine-readable official status; see their status page",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Salesforce down right now?
We cannot tell. api.status.salesforce.com has no public JSON API or feed we may read, and there is no keyless endpoint that says anything useful. Their own status page is at https://api.status.salesforce.com/v1/incidents/active.
Where does this status come from?
api.status.salesforce.com has no public JSON API or feed we may read, and there is no keyless endpoint that says anything useful.
How can my agent or app check Salesforce status?
Fetch https://upbutler.com/status/salesforce/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"salesforce"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Salesforce's?
Add "salesforce" to the dependencies of your UpButler workspace. When one of your monitors fails while Salesforce has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with Salesforce. Status and incident text belong to Salesforce and are read from their public status source; the probe result is UpButler's own measurement.