Skip to content

Outage tracker / Salesforce

Is Salesforce down?

I'm having a problem

Vendor reports no incidentWhat Salesforce reports

Salesforce reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:24 UTC.

Salesforce's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 2 minutes ago

Our checks of Salesforce pass from all 10 regions we check.

As of Nov 5, 2026, 2:31 PM UTC, RealUptime's checks of Salesforce passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:31 PM UTC
US-East1049 msChecks passing
US-West1501 msChecks passing
Europe677 msChecks passing
Asia-Pacific2430 msChecks passing
US-Central522 msChecks passing
Canada911 msChecks passing
UK1026 msChecks passing
Southeast Asia2248 msChecks passing
Australia1444 msChecks passing
South America3950 msChecks passing
their status pagetheir claim, not our reading

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

Salesforce response time, by region

US-East
1.3sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 337ms2026-10-08 UTC: p95 374ms2026-10-09 UTC: p95 488ms2026-10-10 UTC: p95 416ms2026-10-11 UTC: p95 438ms2026-10-12 UTC: p95 404ms2026-10-13 UTC: p95 454ms2026-10-14 UTC: p95 449ms2026-10-15 UTC: p95 441ms2026-10-16 UTC: p95 382ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 992ms2026-10-23 UTC: p95 912ms2026-10-24 UTC: p95 762ms2026-10-25 UTC: p95 759ms2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 784ms2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 612ms2026-10-30 UTC: p95 602ms2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
US-West
2.0sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 920ms2026-10-08 UTC: p95 644ms2026-10-09 UTC: p95 852ms2026-10-10 UTC: p95 893ms2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 887ms2026-10-13 UTC: p95 907ms2026-10-14 UTC: p95 896ms2026-10-15 UTC: p95 889ms2026-10-16 UTC: p95 877ms2026-10-17 UTC: p95 864ms2026-10-18 UTC: p95 889ms2026-10-19 UTC: p95 988ms2026-10-20 UTC: p95 978ms2026-10-21 UTC: p95 959ms2026-10-22 UTC: p95 1.9s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.6s2026-10-26 UTC: p95 2.1s2026-10-27 UTC: p95 2.1s2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 2.2s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
Europe
1.2sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 426ms2026-10-08 UTC: p95 455ms2026-10-09 UTC: p95 447ms2026-10-10 UTC: p95 362ms2026-10-11 UTC: p95 455ms2026-10-12 UTC: p95 301ms2026-10-13 UTC: p95 317ms2026-10-14 UTC: p95 425ms2026-10-15 UTC: p95 365ms2026-10-16 UTC: p95 325ms2026-10-17 UTC: p95 801ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 866ms2026-10-22 UTC: p95 947ms2026-10-23 UTC: p95 795ms2026-10-24 UTC: p95 422ms2026-10-25 UTC: p95 428ms2026-10-26 UTC: p95 402ms2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 888ms2026-10-29 UTC: p95 526ms2026-10-30 UTC: p95 669ms2026-10-31 UTC: p95 559ms2026-11-01 UTC: p95 680ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Asia-Pacific
3.3sp95 · 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-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.6s2026-10-19 UTC: p95 2.6s2026-10-20 UTC: p95 2.6s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.0s2026-10-23 UTC: p95 2.1s2026-10-24 UTC: p95 2.8s2026-10-25 UTC: p95 2.8s2026-10-26 UTC: p95 3.4s2026-10-27 UTC: p95 2.6s2026-10-28 UTC: p95 2.6s2026-10-29 UTC: p95 2.8s2026-10-30 UTC: p95 2.8s2026-10-31 UTC: p95 2.7s2026-11-01 UTC: p95 2.7s2026-11-02 UTC: p95 3.2s2026-11-03 UTC: p95 3.5s2026-11-04 UTC: p95 3.3s2026-11-05 UTC: p95 3.3s
Oct 7Oct 21Nov 5
US-Central
785msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 410ms2026-10-08 UTC: p95 563ms2026-10-09 UTC: p95 498ms2026-10-10 UTC: p95 502ms2026-10-11 UTC: p95 428ms2026-10-12 UTC: p95 379ms2026-10-13 UTC: p95 476ms2026-10-14 UTC: p95 513ms2026-10-15 UTC: p95 340ms2026-10-16 UTC: p95 470ms2026-10-17 UTC: p95 837ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 875ms2026-10-22 UTC: p95 645ms2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 918ms2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 987ms2026-10-30 UTC: p95 952ms2026-10-31 UTC: p95 1s2026-11-01 UTC: p95 843ms2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 894ms2026-11-04 UTC: p95 989ms2026-11-05 UTC: p95 785ms
Oct 7Oct 21Nov 5
Canada
1.4sp95 · 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-10-07 UTC: p95 394ms2026-10-08 UTC: p95 378ms2026-10-09 UTC: p95 409ms2026-10-10 UTC: p95 334ms2026-10-11 UTC: p95 414ms2026-10-12 UTC: p95 452ms2026-10-13 UTC: p95 559ms2026-10-14 UTC: p95 413ms2026-10-15 UTC: p95 523ms2026-10-16 UTC: p95 556ms2026-10-17 UTC: p95 956ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 944ms2026-10-22 UTC: p95 707ms2026-10-23 UTC: p95 759ms2026-10-24 UTC: p95 476ms2026-10-25 UTC: p95 372ms2026-10-26 UTC: p95 278ms2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
UK
1.4sp95 · 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-10-07 UTC: p95 285ms2026-10-08 UTC: p95 377ms2026-10-09 UTC: p95 376ms2026-10-10 UTC: p95 355ms2026-10-11 UTC: p95 453ms2026-10-12 UTC: p95 427ms2026-10-13 UTC: p95 380ms2026-10-14 UTC: p95 327ms2026-10-15 UTC: p95 282ms2026-10-16 UTC: p95 295ms2026-10-17 UTC: p95 456ms2026-10-18 UTC: p95 825ms2026-10-19 UTC: p95 982ms2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 810ms2026-10-22 UTC: p95 296ms2026-10-23 UTC: p95 712ms2026-10-24 UTC: p95 412ms2026-10-25 UTC: p95 502ms2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 903ms2026-11-01 UTC: p95 935ms2026-11-02 UTC: p95 936ms2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Southeast Asia
3.1sp95 · 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-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 999ms2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 913ms2026-10-11 UTC: p95 960ms2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 968ms2026-10-14 UTC: p95 662ms2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 2.8s2026-10-24 UTC: p95 2.7s2026-10-25 UTC: p95 2.7s2026-10-26 UTC: p95 2.5s2026-10-27 UTC: p95 2.3s2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 2.4s2026-10-31 UTC: p95 2.4s2026-11-01 UTC: p95 2.7s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 3.1s
Oct 7Oct 21Nov 5
Australia
3.2sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 2.1s2026-10-08 UTC: p95 2.0s2026-10-09 UTC: p95 2.4s2026-10-10 UTC: p95 2.0s2026-10-11 UTC: p95 1.8s2026-10-12 UTC: p95 1.9s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 2.2s2026-10-16 UTC: p95 1.8s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 3.1s2026-10-19 UTC: p95 3.2s2026-10-20 UTC: p95 3.1s2026-10-21 UTC: p95 3.0s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 3.3s2026-10-24 UTC: p95 3.6s2026-10-25 UTC: p95 2.5s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 2.3s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 2.7s2026-10-30 UTC: p95 2.8s2026-10-31 UTC: p95 2.5s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 2.7s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 3.4s2026-11-05 UTC: p95 3.2s
Oct 7Oct 21Nov 5
South America
3.8sp95 · 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-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.8s2026-10-11 UTC: p95 1.9s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 973ms2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.8s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 8.3s2026-10-24 UTC: p95 2.6s2026-10-25 UTC: p95 2.4s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 2.3s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.6s2026-10-30 UTC: p95 2.5s2026-10-31 UTC: p95 2.6s2026-11-01 UTC: p95 2.9s2026-11-02 UTC: p95 3.0s2026-11-03 UTC: p95 2.8s2026-11-04 UTC: p95 3.3s2026-11-05 UTC: p95 3.8s
Oct 7Oct 21Nov 5

Check your own site while you wait on Salesforce

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • AuthprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • AppExchangeUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Sandbox sign-inUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • TrailheadUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Salesforce reports an incident on its status page, and again when it reports it resolved.

Get an email when Salesforce reports an incident

Email me when Salesforce reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Salesforce's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1049msstatus code: 200checked: Nov 5, 2026, 2:24 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
      Checks passinglatency: 1501msstatus code: 200checked: Nov 5, 2026, 2:28 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
      Checks passinglatency: 522msstatus code: 200checked: Nov 5, 2026, 2:23 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
      Checks passinglatency: 911msstatus code: 200checked: Nov 5, 2026, 2:31 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
    Checks passinglatency: 3950msstatus code: 200checked: Nov 5, 2026, 2:20 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 677msstatus code: 200checked: Nov 5, 2026, 2:25 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
      Checks passinglatency: 1026msstatus code: 200checked: Nov 5, 2026, 2:17 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2430msstatus code: 200checked: Nov 5, 2026, 2: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
      Checks passinglatency: 2248msstatus code: 200checked: Nov 5, 2026, 2:18 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
      Checks passinglatency: 1444msstatus code: 200checked: Nov 5, 2026, 2:19 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 probe events

Service disruption on 16 instances, 4h 8mdeclared on their status page2026-10-23
Service disruption on 12 instancesdeclared on their status page2026-10-23
Service disruption on 15 instances, 5h 5mdeclared on their status page2026-10-23
Service disruption on 35 instances, 4h 45mdeclared on their status page2026-10-23
Feature perf degradation on 21 instances, 1h 42mdeclared on their status page2026-10-21
Feature perf degradation on 21 instances, 6h 41mdeclared on their status page2026-10-20
Performance degradation on 84 instances, 37mdeclared on their status page2026-10-09
Performance degradation on 96 instances, 4h 26mdeclared on their status page2026-10-08

check 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 check readings and Salesforce's own claim at the time, side by side.

Full check history for Salesforce: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Salesforce uptime by RealUptime's checksLive, from this page's own readings.
[![Salesforce uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Salesforce down?", https://realuptime.io/outages/salesforce. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: auth surface
https://login.salesforce.com/.well-known/openid-configuration
secondary
https://login.salesforce.com/
secondary
https://status.salesforce.com/
secondary
https://trailhead.salesforce.com/
secondary
https://appexchange.salesforce.com/
secondary
https://test.salesforce.com/.well-known/openid-configuration

What our check can and cannot see

A pass means the configuration document the service publishes, such as an API or sign-in description, loaded. That document is usually static or cached, so it does not show that the endpoints it describes are answering.

Host checked: login.salesforce.com

RealUptime is not affiliated with Salesforce; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.