Is Salesforce Down?

No — Salesforce is up

Reachable from all 8 checked regions

Average response time: 1005ms

Last checked 2 hours ago · checks run every 6 hours

Official status page: https://status.salesforce.com

Salesforce uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

634ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 56 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

56-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

cdg

364ms

DNS 0ms TCP 1ms TLS 6ms TTFB 353ms

dfw

198ms

DNS 1ms TCP 1ms TLS 8ms TTFB 183ms

ewr

325ms

DNS 0ms TCP 1ms TLS 15ms TTFB 312ms

fra

651ms

DNS 0ms TCP 1ms TLS 5ms TTFB 642ms

gru

3229ms

DNS 0ms TCP 134ms TLS 270ms TTFB 2562ms

iad

905ms

DNS 0ms TCP 7ms TLS 7ms TTFB 476ms

jnb

2105ms

DNS 0ms TCP 0ms TLS 6ms TTFB 2094ms

lax

265ms

DNS 0ms TCP 1ms TLS 6ms TTFB 250ms

What Salesforce does

Salesforce is a customer relationship management platform used to track accounts, opportunities, cases and marketing activity. Large organisations build heavily customised workflows on top of it, and internal tools frequently read from its API or authenticate against it, so an outage reaches well beyond the sales team.

What an outage looks like

When Salesforce is down, the interface fails to load or hangs on a spinner, reports and dashboards time out, and API calls from integrated systems return errors. Automated flows and scheduled jobs may not fire, and email-to-case can stop creating records. Availability is often degraded for particular instances rather than everywhere at once.

What to do about it

Check status.salesforce.com and find your specific instance, because availability is reported per instance and a global all-clear can coexist with your org being unavailable. Your instance appears in the org URL. Integrations usually retry, but records created during the incident often need reconciling once service returns.

Is it down for everyone, or just you?

If this page says Salesforce is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Salesforce outage FAQ

How do I find which Salesforce instance I am on?

The instance identifier appears in your org's URL and in Setup under company information. It matters because Salesforce reports availability per instance: the status page can show everything healthy overall while your particular instance is degraded. Checking the headline alone is the most common reason people conclude wrongly that Salesforce is fine.

Is Salesforce down or is my org misconfigured?

If your instance is reported healthy and other users on it are working normally, the problem is more likely a permission, integration or customisation issue than a platform outage. A genuine instance incident affects everyone on it at once, which is usually obvious from colleagues hitting the same failure at the same time.

Do integrations recover on their own after an outage?

Many retry automatically, but not all, and retries can be capped. Records created or updated during the incident are the ones to check, because a failed write that was never retried leaves the two systems disagreeing quietly. Reconciling recent changes is usually more reliable than assuming the integration caught up.

Does a Salesforce outage affect Slack?

Slack is operated as its own platform with its own status page, so a Salesforce instance incident does not automatically take Slack down. Integrations between the two can fail while both platforms remain individually healthy, which is worth checking separately rather than reading either status page as covering both.

How we measure this

We request Salesforce's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Salesforce publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Salesforce goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required