Salesforce: Feature Perf Degradation: Core Service
Affected components: Core Service24 instances
Timeline of updates
- update
This issue has been determined to be a continuation of a previous incident (https://status.salesforce.com/incidents/20003889 (opens in new tab)), which began on March 25 at 01:31 UTC. We’ve identified the trigger as a recent deployment, and have performed rollbacks to resolve the issue. We’re monitoring health metrics to ensure stability and prevent further recurrence of this issue. During impact, customers may have observed various validation errors while deploying to their environments.
We’ll provide an update once this incident is resolved or as substantial information becomes available.
- update
After a period of monitoring system health metrics, the incident has been declared resolved as of March 31, 2026 at 22:18 UTC. We apologize for any inconvenience this issue may have caused 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
d570448d1ecd784f…
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-03-25 01:31 UTC, resolved after 7 d, 2 update(s).
- Title
- Feature Perf Degradation: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003890
Salesforce profileRecent Salesforce incidentsAll outages on March 25, 2026Salesforce in March 2026MarkdownJSON