Skip to main content
Salesforce

Explore Degradation on 10AYPD, 10AZPD, PDUECA, UE1PD

Degraded Lasted 3d 12h · started · Salesforce's page

Level
confirmed
Worst impact
Degraded
Components
Explore
Regions
10aypd, 10azpd, pdueca, ue1pd
Down Index
39of 100

What to do

  • Check whether you use Salesforce Explore in 10aypd, 10azpd, pdueca, ue1pd. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 3d 12h it lasted.

    Anything that failed between 2026-10-24 06:36 UTC and 2026-10-27 18:54 UTC may need a replay.
  • Subscribe to Salesforce's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=salesforce works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Salesforce 2

  1. update

    Customers will see an error opening a data source from a workbook: "That page could not be accessed. Either the data source does not exist or you do not have the necessary permissions. Engineers are working on a fix, there is a workaround to access these data sources: Don't open the data source from the workbook's Data Sources list. Go to Explore → Data Sources and select the data source by name. We have a knowledge article published: https://help.salesforce.com/s/articleView?id=005465388&type=1

    provider

  2. update

    The engineering team has identified the root cause and a fix is ready. The release process has started, and we'll confirm once the fix is live.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-7fb790e4dd

Is Salesforce still down?

No, this incident was resolved 2026-10-27 18:54 UTC. For Salesforce's live state, see https://down.guide/salesforce.

How long did it last?

3d 12h, from 2026-10-24 06:36 UTC to 2026-10-27 18:54 UTC, by the times Salesforce posted.

What was affected?

Salesforce named Explore in 10aypd, 10azpd, pdueca, ue1pd.

What caused it?

Salesforce hasn't published a root cause. If it does, it shows here.

Where does this come from?

Salesforce's official status page, https://status.salesforce.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.