Salesforce: Performance Degradation: Core Service
Affected components: Core Service4 instances
Timeline of updates
- update
At 00:43 UTC on February 16, 2026, we became aware of an APT performance degradation. The issue is now resolved as of 01:05 UTC. Our teams remain engaged on the issue to identify the root cause and mitigate any recurrences.
We apologize for any inconvenience this may have caused.
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
d27fb557a4cbc3cf…
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-16 00:43 UTC, resolved after 22 min, 1 update(s).
- Title
- Performance Degradation: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003704
Salesforce profileRecent Salesforce incidentsAll outages on February 16, 2026Salesforce in February 2026MarkdownJSON