Salesforce: Performance Degradation: Core Service
Affected components: Core Service37 instances
Timeline of updates
- update
At 03:30 UTC on April 14, 2026, we became aware of a performance degradation that impacted Triggered Flows for a subset of customers. Affected customers may have experienced significantly slower response times when creating or updating records via the User Interface or integration tools, and when using various services such as live chat, flows, order intake, or case creation.
As of 04:15 UTC on April 15, 2026, all impacted Hyperforce instances have been successfully restored and the issue stands resolved.
We apologize for how this incident affected you and 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
0009e8ca61de8619…
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-14 03:30 UTC, resolved after 25 h, 1 update(s).
- Title
- Performance Degradation: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003933
Salesforce profileRecent Salesforce incidentsAll outages on April 14, 2026Salesforce in April 2026MarkdownJSON