Salesforce: Performance Degradation: Core Service
Affected components: Core Service22 instances
Timeline of updates
- update
We investigated an issue where multiple Salesforce instances were temporarily impacted. This issue resulted from necessary remediation efforts for a separate ongoing incident (Trust link: https://status.salesforce.com/incidents/20004254 (opens in new tab)), which required deployments during high-traffic periods. As the deployment process concluded, the impact ceased, and the services have returned to normal operation.
We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, the underlying cause, and preventive action to avoid a repeat in the 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
6fe8d67d53fb6030…
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-07-09 20:33 UTC, resolved after 12 min, 1 update(s).
- Title
- Performance Degradation: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20004255
Salesforce profileRecent Salesforce incidentsAll outages on July 9, 2026Salesforce in July 2026MarkdownJSON