Salesforce: Feature Perf Degradation: Core Service
Affected components: Core Service16 instances
Timeline of updates
- update
We're investigating a feature degradation related to a recent release, impacting multiple cells in the Japan region.
We've developed a fix, which will be deployed outside business hours to minimize further disruption to your business.
Deployment is scheduled to start at approximately 13:00 UTC, February 6, 2026.
We'll provide an update once the fix has been deployed, sooner if we have more information. - update
The fix finished deploying across all instances by 14:05 UTC. All customers are now out of impact.
We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
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
8fee26e1392f3d75…
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-02-06 02:27 UTC, resolved after 12 h, 2 update(s).
- Title
- Feature Perf Degradation: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003668
Salesforce profileRecent Salesforce incidentsAll outages on February 6, 2026Salesforce in February 2026MarkdownJSON