# Salesforce: Service Disruption: Core Service

- Impact (vendor’s label): major
- Status: resolved
- Started: 2025-11-01 14:51 UTC · Resolved: 2025-11-01 17:05 UTC · Duration: 2.2 h
- Updates: 6 · Affected components: Core Service, 1 instance
- [Vendor status page: https://status.salesforce.com/incidents/20003421](https://status.salesforce.com/incidents/20003421)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **update** 2025-11-01 15: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** 2025-11-01 15:57 UTC: We noted a service disruption impacting JPN138, JPN140, JPN144 and JPN146 instances. Users are unable to access their services. Initial investigations suggest a potential issue at the database tier. We’re further investigating the cause of the issue.  We will provide an update in 30 minutes or sooner if we have more information.
- **update** 2025-11-01 16:11 UTC: JPN138, JPN140 and JPN146 are out of impact as of 15:22 UTC, 15:21 UTC and 15:41 UTC, respectively. We have updated the posting to reflect the currently impacted instances. We identified that the issue was caused due to a configuration change that was part of a recent release. Once the release was completed, the instances were back online and accessible. We continue to investigate JPN144 and will provide an update in 30 minutes or sooner if we have more information.
- **update** 2025-11-01 16:26 UTC: Upon further investigation, the Salesforce Technology team has determined that the start time of impact is different than initially understood. We have now revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.
- **update** 2025-11-01 16:39 UTC: We are working on redeploying a recent Release to fix the issue. We will provide an update once the deployment is completed or sooner if we have more information.
- **update** 2025-11-01 17:06 UTC: We successfully redeployed the release, resolving the issue. Customers can now access their services as of 17:05 UTC. We apologize for any inconvenience this incident may have caused you and your business. Salesforce is fully committed to minimizing downtime during such events. We also continuously evaluate and improve our tools, processes, and architecture to deliver the best service possible.

## Rewindex changes for this incident

- 2025-11-01 14:51 UTC: [Major incident: Service Disruption: Core Service](https://rewindex.com/change/icf104bdf33f9f3.md)


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