- Level
- confirmed
- Worst impact
- Major outage
- Components
- Customer360Audiences
- Regions
- bra14, bra24, bra36, bra48, bra50, usa3s, usa346, usa564, usa638, usa648, usa720, usa936s, usa1160, usa1224
- Down Index
- 62of 100
What to do
Check whether you use Salesforce Customer360Audiences in bra14, bra24, bra36, bra48. 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 3h 19m it lasted.
Anything that failed between 2026-10-30 19:00 UTC and 2026-10-30 22:19 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.
Root cause
We’re investigating the cause of the issue.Read the postmortem
Updates from Salesforce 1
- investigatingcauseofissue
We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.
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-0c96a88f58
Is Salesforce still down?
No, this incident was resolved 2026-10-30 22:19 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
3h 19m, from 2026-10-30 19:00 UTC to 2026-10-30 22:19 UTC, by the times Salesforce posted.
What was affected?
Salesforce named Customer360Audiences in bra14, bra24, bra36, bra48.
What caused it?
Salesforce wrote: "We’re investigating the cause of the issue." The postmortem: https://status.salesforce.com/incidents/20004550
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.