Salesforce: Performance Degradation: Core Service
Affected components: Core Service5 instances
Timeline of updates
- update
At 21:26 UTC on April 20, 2026, our technology teams identified a performance degradation impacting several instances. Our teams investigated and mitigated the issue by reverting a recent scripting change. After a period of monitoring to ensure stability, we declared the incident resolved as of 22:27 UTC. We apologize for any inconvenience this 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
f590e1f013a940d4…
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-04-20 21:26 UTC, resolved after 1.0 h, 1 update(s).
- Title
- Performance Degradation: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003948
Salesforce profileRecent Salesforce incidentsAll outages on April 20, 2026Salesforce in April 2026MarkdownJSON