# Salesforce status

> Is Salesforce down? Live status, uptime history, and per-region response times measured by our own probes every 2 minutes.

Published: 2026-09-06 | Canonical: https://yoping.me/status/salesforce

## How we check Salesforce

We watch login.salesforce.com from all five of our probe regions, every 2 minutes. A region that sees a failure does not make this page say "down" on its own: a second region has to agree first, the same confirmation rule every YoPingMe monitor uses.

Salesforce is a large collection of independently deployed orgs, each on its own instance, so no single URL represents every customer's experience. We watch the shared login host that every org authenticates through regardless of instance, and pin the response an anonymous request receives rather than assuming a 2xx.

The live board - the current verdict, 24-hour, 7-day, and 30-day uptime, and per-region response times - is on the HTML page at https://yoping.me/status/salesforce. Those numbers change too fast to repeat honestly in a static mirror, so where an answer below says "the board above", it means that page.

## What is Salesforce?

Salesforce runs customer relationship management and a wide platform of
related tools across a large number of independently deployed instances,
each hosting many customer organisations with their own configuration,
custom code, and integrations. That architecture is the first thing
worth understanding, because "is Salesforce down" is rarely a single
yes-or-no answer across every customer at once.

Every org authenticates through a shared login layer regardless of which
instance actually hosts its data, which is why this page watches that
shared entry point rather than any single instance. It is a meaningful
signal for whether the platform's front door is reachable, and it is
deliberately narrower than a claim about any specific organisation's
instance, which can have its own maintenance window or incident
independent of the shared login layer entirely.

Configuration changes inside an org are a frequent cause of what looks
like an outage and is not one. A metadata deployment that went out with
an error, a permission set that was tightened during unrelated security
work, or a validation rule that now blocks a workflow that used to
succeed will all make part of an org behave as if something is broken
while Salesforce's platform answers every request normally. These are
changes made inside the org, not platform incidents, and reviewing recent
deployments is usually the fastest way to find one.

Integrations add their own layer of trouble that is easy to mistake for
downtime. API users authenticate with credentials or OAuth tokens that
can expire, be revoked during a security review, or stop working after an
IP allowlist changes, all independent of whether Salesforce itself is
healthy. An integration failing with an authentication error is worth
checking against recent changes to its credentials before it is treated
as a platform problem.

The reassuring part of depending on Salesforce is that records already
saved are not at risk from a reachability incident. What is worth
verifying afterward is whether any automation, integration sync, or
batch job that was running during an incident completed successfully,
which the platform's own audit trail and each integration's logs settle
far more reliably than assuming either the best or the worst outcome.

## Frequently asked questions

### Is Salesforce down right now?

Check the board above; it reflects our own probes against Salesforce's shared login host from all five of our regions, refreshed every couple of minutes. Your organisation's actual data and application logic run on a specific instance, so this is a reading of the shared entry point rather than of your instance specifically.

### My org is unreachable but this page shows Salesforce up. What should I check?

Check the Salesforce Trust status page for your specific instance, because Salesforce runs many independently operated instances and an incident is typically scoped to one of them rather than the whole platform. A recent metadata deployment, a permission set change, or an integration user's credentials expiring can all make an org unreachable while Salesforce broadly reports healthy.

### Does a Salesforce outage affect data already saved?

No. An outage affects the ability to reach and use the platform going forward, not the durability of records already committed. The practical question after any incident is whether an automation or integration that was mid-run completed successfully, which audit trail and integration logs settle far more reliably than assuming either outcome.

### Is the Salesforce Trust status page the same as this one?

No. Trust reports what Salesforce has confirmed internally, scoped to your specific instance and its maintenance schedule, which is more relevant to your organisation than any outside probe could be. This page reports what our own probes measured against the shared login host, from outside Salesforce's infrastructure, on a fixed schedule, whether or not Salesforce has posted an update yet.

### An integration using the Salesforce API is failing with an authentication error. Is that an outage?

Usually not. Integration users authenticate with credentials or tokens that expire or get revoked independently of the platform's health, and a security review, a password policy change, or an IP allowlist update can all invalidate an integration's access without anything on Salesforce's side going down.