- Level
- confirmed
- Worst impact
- Degraded
- Components
- search
- Regions
- che16, che30
- Down Index
- 30of 100
What to do
Check whether you use Salesforce search in che16, che30. 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 2h 55m it lasted.
Anything that failed between 2026-10-31 07:13 UTC and 2026-10-31 10:08 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
- update
We have identified a delay in search indexing for customers on the CHE16 and CHE30 instances. Customers may notice that recently created or updated records do not yet appear in search results. Search itself continues to work. We identified the technical trigger and started a corrective deployment. We’ll provide another update upon the completion of the deployment or sooner if additional information becomes available.
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-1515caa360
Is Salesforce still down?
No, this incident was resolved 2026-10-31 10:08 UTC. For Salesforce's live state, see https://down.guide/salesforce.
How long did it last?
2h 55m, from 2026-10-31 07:13 UTC to 2026-10-31 10:08 UTC, by the times Salesforce posted.
What was affected?
Salesforce named search in che16, che30.
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.