Salesforce: Feature Service Disruption: Core Service
Affected components: Core Service415 instances
Timeline of updates
- update
Between 04:46 UTC and 07:57 UTC, we identified an issue with a recent software release that prevented users from making changes to cases and case records across multiple instances. To prevent further impact, we halted the deployment of the impacted version and rolled back to the previous stable software version using a staggered approach, which resolved the issue and restored services.
We appreciate your patience as we worked to restore full functionality.
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
c89d5ac415a30b55…
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 2025-10-28 04:46 UTC, resolved after 3.2 h, 1 update(s).
- Title
- Feature Service Disruption: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003408
Salesforce profileRecent Salesforce incidentsAll outages on October 28, 2025Salesforce in October 2025MarkdownJSON