Salesforce: Performance Degradation: Search
Affected components: Search2 instances
Timeline of updates
- 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.
Changes Rewindex caught on this incident
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-31 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
37dcca39ad40e0b3…Version 2 captured
In the 2026-10-31 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
dd8d2b05b5702c84…
Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Salesforce, started 2026-10-31 07:13 UTC, resolved after 2.9 h, 1 update(s); edited after publishing.
- Title
- Performance Degradation: Search
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20004551
Salesforce profileRecent Salesforce incidentsAll outages on October 31, 2026Salesforce in October 2026MarkdownJSON