- Level
- confirmed
- Worst impact
- Degraded
- Components
- LoadaView
- Regions
- 10aypd, 10azpd, dub01pd, ew1a, pdanaa, pdasaa, pdasba, pdasca, pdcaaa, pdcha, pdina, pdkra, pdpuwaa, pdueaa, pdueba, pdueca, pdukaa, pduwca, tableauselfserviceportals, ue1pd, uw2bpd
- Down Index
- 43of 100
What to do
Check whether you use Salesforce LoadaView in 10aypd, 10azpd, dub01pd, ew1a. 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 14h it lasted.
Anything that failed between 2026-10-13 18:36 UTC and 2026-10-17 09:24 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 3
- update
We're aware of an issue affecting a subset of Tableau Cloud customers following a recent release. Customers using extract-based data sources may see calculated fields renamed. Workbooks and dashboards that depend on those fields may not display correctly. As a workaround, customers can switch to a live connection. A Known Issue article is available with additional details here: https://help.salesforce.com/s/issue?id=a02g700000BteHp We are actively working on a fix and redeployment to mitigate this issue. We will provide an update as soon as more information becomes available.
provider
- update
We have successfully validated and tested the fix in a lower environment. Initial reports have indicated positive results, and we are working to roll out the fix to the remaining production instances. We will provide an update as soon as more information becomes available.
provider
- resolvedfeaturedegradation
We’ve confirmed that the solution implemented to mitigate the issue causing the feature degradation was successful. Engineers have observed that the service is now stable and have declared the incident resolved. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident.
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-38ff2155bf
Is Salesforce still down?
No, this incident was resolved 2026-10-17 09:24 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
3d 14h, from 2026-10-13 18:36 UTC to 2026-10-17 09:24 UTC, by the times Salesforce posted.
What was affected?
Salesforce named LoadaView in 10aypd, 10azpd, dub01pd, ew1a.
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.