Salesforce: Feature Perf Degradation: Core Service
Affected components: Core Service3 instances
Timeline of updates
- update
We investigated an issue affecting Private Connect services that caused degraded connectivity to Salesforce services for some customers. We identified a recent change as the likely trigger. We implemented the required fix, and connectivity through Private Connect returned to normal as of 02:58 UTC on the affected instances.
We apologize for the impact. We will complete a full investigation to determine the root cause and identify measures to prevent a recurrence.
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
c8a24576206f953d…
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-08-19 07:38 UTC, resolved after 43 h, 1 update(s).
- Title
- Feature Perf Degradation: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20004369
Salesforce profileRecent Salesforce incidentsAll outages on August 19, 2026Salesforce in August 2026MarkdownJSON