Salesforce: Performance Degradation: Core Service
Affected components: Core Service1 instance
Timeline of updates
- update
The Salesforce Technology team has completed its investigation and determined this is related to an on-going incident. We apologize for any inconvenience caused by the false positive notification, and we will undertake a full investigation as we look to improve our impact alerting and assessment configurations.
For more information please follow Trust: https://status.salesforce.com/incidents/20003820 (opens in new tab)
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
7e46f4f957e673ba…
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-16 17:34 UTC, resolved after 2.1 h, 1 update(s).
- Title
- Performance Degradation: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003821
Salesforce profileRecent Salesforce incidentsAll outages on March 16, 2026Salesforce in March 2026MarkdownJSON