- Level
- confirmed
- Worst impact
- Degraded
- Components
- coreService
- Regions
- ita30
- Down Index
- 18of 100
What to do
Check whether you use Salesforce coreService in ita30. 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 0m it lasted.
Anything that failed between 2026-10-24 10:53 UTC and 2026-10-24 10:53 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 1
- correctionfalsepositive
The Salesforce Technology team has completed its investigation and determined that the listed instances and services remained healthy and did not experience impact during the times outlined. We apologize for any inconvenience caused by the false positive notification, and we will undertake a full investigation as we look to improve our impact alerting and assessment configurations.
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-8556787a05
Is Salesforce still down?
No, this incident was resolved 2026-10-24 10:53 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
0m, from 2026-10-24 10:53 UTC to 2026-10-24 10:53 UTC, by the times Salesforce posted.
What was affected?
Salesforce named coreService in ita30.
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.