- Level
- confirmed
- Worst impact
- Degraded
- Components
- Customer360Audiences
- Regions
- usa9002, usa9004s, usa9006s, usa9008, usa9010s, usa9012s, usa9014, usa9016s, usa9018s, usa9020, usa9022s, usa9402, usa9404s, usa9902
- Down Index
- 43of 100
What to do
Check whether you use Salesforce Customer360Audiences in usa9002, usa9004s, usa9006s, usa9008. 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 2d 7h it lasted.
Anything that failed between 2026-10-19 15:30 UTC and 2026-10-21 22:33 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
- update
We’ve investigated and resolved an issue where Identity Resolution was not completing normally. Customers using the affected feature saw errors, and new data was not being populated in the unified profile table. Existing data remained usable. We traced the trigger to a recent release, and deployed a fix. Identity Resolution is now operating normally. We apologize for the impact this incident had on you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
provider
- impactradiusincrease
Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
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-2212d7eff4
Is Salesforce still down?
No, this incident was resolved 2026-10-21 22:33 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
2d 7h, from 2026-10-19 15:30 UTC to 2026-10-21 22:33 UTC, by the times Salesforce posted.
What was affected?
Salesforce named Customer360Audiences in usa9002, usa9004s, usa9006s, usa9008.
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.