# Salesforce: Performance Degradation: Core Service

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2025-09-10 16:01 UTC · Resolved: 2025-09-10 20:40 UTC · Duration: 4.7 h
- Updates: 5 · Affected components: Core Service, 191 instances
- [Vendor status page: https://status.salesforce.com/incidents/20003231](https://status.salesforce.com/incidents/20003231)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **update** 2025-09-10 17:14 UTC: We noted a Salesforce service performance degradation on multiple instances. During this time, org administrators may be experiencing HTTP login errors when attempting to use the ‘login as’ feature. We have rolled back a recent release, which did not mitigate the issue. Our teams are continuing to troubleshoot the issue. We will provide an update in 30 minutes or sooner if more information becomes available.
- **update** 2025-09-10 17:52 UTC: We are continuing to address a Salesforce service performance degradation affecting multiple sandbox instances. Org administrators are still experiencing HTTP login errors and failed redirects when attempting to use the ‘login as’ feature. We’re still actively investigating this issue, but we don’t have any new information to share at this time. We have engaged multiple additional teams to help explore multiple strategies to mitigate the issue and restore services as quickly as possible.  We will provide an update in 60 minutes or sooner if more information becomes available.
- **update** 2025-09-10 19:01 UTC: Our investigation has broadened significantly, and we are working towards identifying the full impact radius. We have paused our rollback efforts and are deeply analyzing HTTP protocol errors, as requests appear to be failing before fully reaching the core application. Specialized engineering teams are engaged, employing application-level investigations to gather more detailed insights into the request path. We will provide an update in 60 minutes or sooner if more information becomes available. Thank you for your patience as we work towards resolving this issue.
- **update** 2025-09-10 20:08 UTC: We have identified that turning off a recent Edge networking version resulted in relief, and completed a rollback to a previous version. We are monitoring our health metrics for resolution. Customers may attempt a browser refresh to retry. We have posted an Informational Message that can be found here: https://status.salesforce.com/generalmessages/20000219?locale=en-US We will provide an update in 60 minutes or sooner if more information becomes available. Thank you for your patience as we work towards resolving this issue.
- **update** 2025-09-10 21:05 UTC: As of Sep 10, 20:40 UTC, the issue is resolved, and org administrators can use the “login as” feature as intended. Upon further investigation, additional services or features that were not listed in this post may have been impacted, which have been resolved after rolling back the Edge release. Thank you for your patience as we worked to resolve this issue. We apologize for how this incident may have affected you and your business. We’ll perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventative actions to avoid a repeat in the future.


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