Skip to content

Outage tracker / Salesforce

Is Salesforce down?

I'm having a problem

Operationalchecked 6 minutes ago

We reached Salesforce from all 10 regions we check.

As of Oct 5, 2026, 8:11 PM UTC, Salesforce answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Salesforce (since Aug 20, 2026).

our independent probeslive · checked Oct 5, 2026, 8:11 PM UTC
US-East218 msOperational
US-West319 msOperational
Europe102 msOperational
Asia-Pacific1022 msOperational
US-Central214 msOperational
Canada436 msOperational
UK380 msOperational
Southeast Asia408 msOperational
Australia1574 msOperational
South America711 msOperational
their status pagetheir claim, not our reading

Salesforce publishes no status feed we can read, so the only independent reading here is ours on the left.

Salesforce response time, by region

US-East
706msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 468ms2026-09-07 UTC: p95 390ms2026-09-08 UTC: p95 312ms2026-09-09 UTC: p95 392ms2026-09-10 UTC: p95 495ms2026-09-11 UTC: p95 408ms2026-09-12 UTC: p95 437ms2026-09-13 UTC: p95 446ms2026-09-14 UTC: p95 405ms2026-09-15 UTC: p95 492ms2026-09-16 UTC: p95 648ms2026-09-17 UTC: p95 530ms2026-09-18 UTC: p95 493ms2026-09-19 UTC: p95 482ms2026-09-20 UTC: p95 466ms2026-09-21 UTC: p95 424ms2026-09-22 UTC: p95 450ms2026-09-23 UTC: p95 717ms2026-09-24 UTC: p95 760ms2026-09-25 UTC: p95 894ms2026-09-26 UTC: p95 776ms2026-09-27 UTC: p95 680ms2026-09-28 UTC: p95 635ms2026-09-29 UTC: p95 692ms2026-09-30 UTC: p95 710ms2026-10-01 UTC: p95 514ms2026-10-02 UTC: p95 385ms2026-10-03 UTC: p95 411ms2026-10-04 UTC: p95 537ms2026-10-05 UTC: p95 706ms
Sep 6Sep 20Oct 5
US-West
867msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 633ms2026-09-07 UTC: p95 649ms2026-09-08 UTC: p95 466ms2026-09-09 UTC: p95 473ms2026-09-10 UTC: p95 434ms2026-09-11 UTC: p95 391ms2026-09-12 UTC: p95 371ms2026-09-13 UTC: p95 424ms2026-09-14 UTC: p95 410ms2026-09-15 UTC: p95 640ms2026-09-16 UTC: p95 938ms2026-09-17 UTC: p95 938ms2026-09-18 UTC: p95 893ms2026-09-19 UTC: p95 965ms2026-09-20 UTC: p95 896ms2026-09-21 UTC: p95 987ms2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 878ms2026-09-24 UTC: p95 793ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 922ms2026-09-27 UTC: p95 661ms2026-09-28 UTC: p95 882ms2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 948ms2026-10-02 UTC: p95 884ms2026-10-03 UTC: p95 982ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 867ms
Sep 6Sep 20Oct 5
Europe
534msp95 · latest
5s2.5s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.7s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 2.1s2026-09-10 UTC: p95 1.8s2026-09-11 UTC: p95 1.9s2026-09-12 UTC: p95 1.7s2026-09-13 UTC: p95 1.8s2026-09-14 UTC: p95 1.8s2026-09-15 UTC: p95 1.8s2026-09-16 UTC: p95 2.1s2026-09-17 UTC: p95 2.2s2026-09-18 UTC: p95 2.2s2026-09-19 UTC: p95 2.4s2026-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 2.3s2026-09-22 UTC: p95 2.2s2026-09-23 UTC: p95 2.3s2026-09-24 UTC: p95 2.5s2026-09-25 UTC: p95 2.4s2026-09-26 UTC: p95 2.1s2026-09-27 UTC: p95 1.9s2026-09-28 UTC: p95 2.4s2026-09-29 UTC: p95 4.3s2026-09-30 UTC: p95 2.0s2026-10-01 UTC: p95 422ms2026-10-02 UTC: p95 448ms2026-10-03 UTC: p95 476ms2026-10-04 UTC: p95 517ms2026-10-05 UTC: p95 534ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.5sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 2.7s2026-09-07 UTC: p95 3.1s2026-09-08 UTC: p95 3.0s2026-09-09 UTC: p95 2.5s2026-09-10 UTC: p95 3.1s2026-09-11 UTC: p95 3.5s2026-09-12 UTC: p95 3.0s2026-09-13 UTC: p95 2.4s2026-09-14 UTC: p95 2.5s2026-09-15 UTC: p95 2.4s2026-09-16 UTC: p95 2.4s2026-09-17 UTC: p95 2.6s2026-09-18 UTC: p95 2.5s2026-09-19 UTC: p95 3.9s2026-09-20 UTC: p95 2.6s2026-09-21 UTC: p95 3.0s2026-09-22 UTC: p95 2.4s2026-09-23 UTC: p95 2.0s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 2.1s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 2.0s2026-09-29 UTC: p95 2.7s2026-09-30 UTC: p95 2.3s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.5s
Sep 6Sep 20Oct 5
US-Central
353msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 693ms2026-09-07 UTC: p95 696ms2026-09-08 UTC: p95 718ms2026-09-09 UTC: p95 733ms2026-09-10 UTC: p95 533ms2026-09-11 UTC: p95 443ms2026-09-12 UTC: p95 299ms2026-09-13 UTC: p95 370ms2026-09-14 UTC: p95 359ms2026-09-15 UTC: p95 471ms2026-09-16 UTC: p95 367ms2026-09-17 UTC: p95 348ms2026-09-18 UTC: p95 379ms2026-09-19 UTC: p95 472ms2026-09-20 UTC: p95 400ms2026-09-21 UTC: p95 486ms2026-09-22 UTC: p95 593ms2026-09-23 UTC: p95 599ms2026-09-24 UTC: p95 709ms2026-09-25 UTC: p95 601ms2026-09-26 UTC: p95 691ms2026-09-27 UTC: p95 558ms2026-09-28 UTC: p95 680ms2026-09-29 UTC: p95 786ms2026-09-30 UTC: p95 641ms2026-10-01 UTC: p95 361ms2026-10-02 UTC: p95 284ms2026-10-03 UTC: p95 320ms2026-10-04 UTC: p95 360ms2026-10-05 UTC: p95 353ms
Sep 6Sep 20Oct 5
Canada
687msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 974ms2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.0s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 808ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 950ms2026-09-19 UTC: p95 700ms2026-09-20 UTC: p95 730ms2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 933ms2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 971ms2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 421ms2026-10-02 UTC: p95 431ms2026-10-03 UTC: p95 475ms2026-10-04 UTC: p95 535ms2026-10-05 UTC: p95 687ms
Sep 6Sep 20Oct 5
UK
366msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 661ms2026-09-07 UTC: p95 736ms2026-09-08 UTC: p95 526ms2026-09-09 UTC: p95 761ms2026-09-10 UTC: p95 923ms2026-09-11 UTC: p95 780ms2026-09-12 UTC: p95 750ms2026-09-13 UTC: p95 845ms2026-09-14 UTC: p95 829ms2026-09-15 UTC: p95 789ms2026-09-16 UTC: p95 996ms2026-09-17 UTC: p95 943ms2026-09-18 UTC: p95 932ms2026-09-19 UTC: p95 927ms2026-09-20 UTC: p95 973ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 950ms2026-09-23 UTC: p95 897ms2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 938ms2026-09-26 UTC: p95 940ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 968ms2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 804ms2026-10-01 UTC: p95 721ms2026-10-02 UTC: p95 484ms2026-10-03 UTC: p95 409ms2026-10-04 UTC: p95 338ms2026-10-05 UTC: p95 366ms
Sep 6Sep 20Oct 5
Southeast Asia
1.2sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 2.6s2026-09-07 UTC: p95 2.2s2026-09-08 UTC: p95 3.3s2026-09-09 UTC: p95 2.2s2026-09-10 UTC: p95 1.9s2026-09-11 UTC: p95 4.5s2026-09-12 UTC: p95 1.9s2026-09-13 UTC: p95 945ms2026-09-14 UTC: p95 2.1s2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 2.1s2026-09-17 UTC: p95 1.9s2026-09-18 UTC: p95 1.9s2026-09-19 UTC: p95 2.0s2026-09-20 UTC: p95 2.1s2026-09-21 UTC: p95 2.7s2026-09-22 UTC: p95 3.9s2026-09-23 UTC: p95 4.3s2026-09-24 UTC: p95 3.6s2026-09-25 UTC: p95 3.4s2026-09-26 UTC: p95 4.4s2026-09-27 UTC: p95 3.9s2026-09-28 UTC: p95 3.3s2026-09-29 UTC: p95 3.2s2026-09-30 UTC: p95 2.7s2026-10-01 UTC: p95 2.1s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 955ms2026-10-04 UTC: p95 995ms2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
Australia
2.0sp95 · latest
10s5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 3.1s2026-09-07 UTC: p95 3.6s2026-09-08 UTC: p95 7.6s2026-09-09 UTC: p95 3.6s2026-09-10 UTC: p95 4.2s2026-09-11 UTC: p95 3.6s2026-09-12 UTC: p95 3.8s2026-09-13 UTC: p95 7.4s2026-09-14 UTC: p95 3.6s2026-09-15 UTC: p95 3.5s2026-09-16 UTC: p95 3.3s2026-09-17 UTC: p95 3.5s2026-09-18 UTC: p95 3.5s2026-09-19 UTC: p95 3.1s2026-09-20 UTC: p95 3.2s2026-09-21 UTC: p95 3.5s2026-09-22 UTC: p95 3.6s2026-09-23 UTC: p95 3.6s2026-09-24 UTC: p95 5.5s2026-09-25 UTC: p95 4.0s2026-09-26 UTC: p95 3.7s2026-09-27 UTC: p95 7.7s2026-09-28 UTC: p95 5.6s2026-09-29 UTC: p95 6.1s2026-09-30 UTC: p95 4.0s2026-10-01 UTC: p95 2.0s2026-10-02 UTC: p95 2.2s2026-10-03 UTC: p95 2.4s2026-10-04 UTC: p95 2.2s2026-10-05 UTC: p95 2.0s
Sep 6Sep 20Oct 5
South America
1.4sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 2.7s2026-09-07 UTC: p95 3.3s2026-09-08 UTC: p95 2.6s2026-09-09 UTC: p95 2.7s2026-09-10 UTC: p95 2.5s2026-09-11 UTC: p95 2.3s2026-09-12 UTC: p95 2.3s2026-09-13 UTC: p95 2.4s2026-09-14 UTC: p95 6.2s2026-09-15 UTC: p95 2.6s2026-09-16 UTC: p95 4.8s2026-09-17 UTC: p95 2.6s2026-09-18 UTC: p95 5.5s2026-09-19 UTC: p95 2.7s2026-09-20 UTC: p95 2.6s2026-09-21 UTC: p95 2.8s2026-09-22 UTC: p95 4.3s2026-09-23 UTC: p95 3.1s2026-09-24 UTC: p95 2.8s2026-09-25 UTC: p95 2.6s2026-09-26 UTC: p95 3.2s2026-09-27 UTC: p95 6.3s2026-09-28 UTC: p95 2.6s2026-09-29 UTC: p95 2.3s2026-09-30 UTC: p95 2.5s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.4s
Sep 6Sep 20Oct 5

Is it Salesforce, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Salesforce -- it cannot diagnose Salesforce's own systems.

What we measured, function by function

Salesforce answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the auth row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Salesforce go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Salesforce, and again when they can reach it again. That is our own measurement from ten regions, not Salesforce's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 218msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Salesforce normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 319msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Salesforce normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 214msstatus code: 200checked: Oct 5, 2026, 8:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Salesforce normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 436msstatus code: 200checked: Oct 5, 2026, 8:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Salesforce normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 711msstatus code: 200checked: Oct 5, 2026, 8:06 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Salesforce normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 102msstatus code: 200checked: Oct 5, 2026, 8:10 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Salesforce normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 380msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Salesforce normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 1022msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Salesforce normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 408msstatus code: 200checked: Oct 5, 2026, 7:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Salesforce normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1574msstatus code: 200checked: Oct 5, 2026, 8:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Salesforce normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Salesforce, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Salesforce yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Salesforce.

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Salesforce since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Salesforce covering any window you pick, with our measurements and Salesforce's own claim at the time, side by side.

Full availability history for Salesforce: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Salesforce uptime measured by RealUptimeLive, from this page's own readings.
[![Salesforce uptime measured by RealUptime](https://realuptime.io/outages/salesforce/badge.svg?days=30)](https://realuptime.io/outages/salesforce)
<a href="https://realuptime.io/outages/salesforce"><img src="https://realuptime.io/outages/salesforce/badge.svg?days=30" alt="Salesforce uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Salesforce's SLA implies, from our measurement

At or above your target

We measured none of downtime for Salesforce over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Salesforce's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: auth surface
https://login.salesforce.com/.well-known/openid-configuration
secondary
https://login.salesforce.com/
secondary
https://status.salesforce.com/
RealUptime is not affiliated with Salesforce; the name identifies what we measured, and nothing here speaks for Salesforce's own team. We send a single web request to Salesforce from 10 regions on our own schedule and time the response. We do not see inside Salesforce's systems, do not use an account or real transaction, and are not the same signal Salesforce's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Salesforce is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.