# Salesforce: Performance Degradation: Core Service

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-10-08 10:52 UTC · Resolved: 2026-10-08 15:18 UTC · Duration: 4.4 h
- Updates: 7 · Affected components: Core Service, 96 instances
- [Vendor status page: https://status.salesforce.com/incidents/20004478](https://status.salesforce.com/incidents/20004478)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **update** 2026-10-08 14:31 UTC: We've identified that new servers are failing to start because required startup files are missing. As a result, we can't add the capacity needed to handle customer traffic, and some customers may experience slow responses or errors. We're reviewing settings and testing fixes on the affected servers. We'll provide an update in 30 minutes, or sooner if we have more information.
- **update** 2026-10-08 14:48 UTC: We've tested a fix to restore a missing configuration setting on new servers and are preparing to apply it. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-10-08 14:55 UTC: Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
- **update** 2026-10-08 15:24 UTC: We've applied a fix to add a missing configuration setting to affected servers and are restarting them to restore full capacity. Customers may experience a brief increase in background system activity as servers restart. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-10-08 15:56 UTC: As of 15:21 UTC this performance degradation issue has been resolved. We apologize for how you and your business may have been affected by this. We will perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
- **update** 2026-10-08 19:32 UTC: Upon further investigation, we've determined that the start and end time of impact is different than initially understood. We've revised these times of this Trust post to more accurately reflect the time customers may have experienced impact. We apologize for any confusion caused by this.
- **update** 2026-10-08 19:32 UTC: Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.


---
Canonical: https://rewindex.com/company/salesforce/incidents/20004478 · Markdown: https://rewindex.com/company/salesforce/incidents/20004478.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20004478 · Generated 2026-10-18T10:29:38.706Z