Salesforce: Feature Perf Degradation: Customer360 Audiences
Affected components: Customer360 Audiences8 instances
Timeline of updates
- update
We’ve validated that all search index rebuilds that were triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 which were stuck in a ‘submitted’ status have been correctly processed. A code fix was successfully deployed and customers are no longer impacted as of 18:50 UTC on July 2.
Customers were previously notified of this issue via Trust messaging here: https://status.salesforce.com/incidents/20004177 (opens in new tab)
We apologize for how this incident may have affected you and your business.
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 this record existed by then and has 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-18 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
f743adff904299be…
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-06-30 22:20 UTC, resolved after 45 h, 1 update(s).
- Title
- Feature Perf Degradation: Customer360 Audiences
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20004207
Salesforce profileRecent Salesforce incidentsAll outages on June 30, 2026Salesforce in June 2026MarkdownJSON