# Salesforce: Feature Perf Degradation: Core Service

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2025-11-20 00:06 UTC · Resolved: 2025-11-20 18:02 UTC · Duration: 18 h
- Updates: 7 · Affected components: Core Service, 1 instance
- [Vendor status page: https://status.salesforce.com/incidents/20003475](https://status.salesforce.com/incidents/20003475)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **update** 2025-11-20 16:12 UTC: The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.
- **update** 2025-11-20 16:36 UTC: We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information. We are seeing slight improvement from the initial solution. The team is implementing a different fix to potentially eliminate the issue, entirely.
- **update** 2025-11-20 17:06 UTC: The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update in 30 minutes or sooner if we have more information.
- **update** 2025-11-20 17:29 UTC: We have implemented a solution and are monitoring the instance performance levels.
- **resolved** 2025-11-20 18:20 UTC: We’ve confirmed that the solution implemented to mitigate the issue causing the feature degradation was successful. Engineers have observed that the service is now stable and have declared the incident resolved. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident.
- **update** 2025-11-20 18:43 UTC: We remain out of impact and continuing monitoring to ensure we stay that way.
- **resolved** 2025-11-20 19:19 UTC: We’ve confirmed that the solution implemented to mitigate the issue causing the feature degradation was successful. Engineers have observed that the service is now stable and have declared the incident resolved. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident.


---
Canonical: https://rewindex.com/company/salesforce/incidents/20003475 · Markdown: https://rewindex.com/company/salesforce/incidents/20003475.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20003475 · Generated 2026-10-18T11:26:58.557Z