Salesforce: Feature Perf Degradation: Core Service
Affected components: Core Service7 instances
Timeline of updates
- update
Between 04:36 UTC and 10:52 UTC, on 06 April 2026, we noted a feature degradation impacting a backend storage service leveraged by the application tier to support data integration for features including Custom Big Objects, Apex, Salesforce Connect External IDs, Login Forensics, Event Monitoring, Field Audit Trail, and Chatter. During this time, some customers may have experienced extended response times and timeouts or be unable to access certain aspects of the features.
Following the automatic recovery of the service, our engineering teams performed manual restoration efforts to ensure full stability. The issue is now resolved.
We apologise 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 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
8d026d5ce47026a0…
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-06 04:36 UTC, resolved after 6.3 h, 1 update(s).
- Title
- Feature Perf Degradation: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003915
Salesforce profileRecent Salesforce incidentsAll outages on April 6, 2026Salesforce in April 2026MarkdownJSON