Changes / Salesforce / Service Disruption: Core Service
Salesforce: Major incident: Service Disruption: Core Service
Summary
Summary pending. The diff below shows exactly what changed.
Major incidentLabel: outage (model (Jev), 100%)Changed Detected Source: status.salesforce.com (opens in new tab)
Incident page: full timeline of updates →
What changed
Before: not present
After: Service Disruption: Core Service
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2025-11-01 14:51 UTC
Before: not present
After: 2025-11-01 17:05 UTC
Before: not present
After: 1 instance, Core Service
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Service Disruption: Core Service (this change) | Major incident |
All Salesforce changes → · Salesforce profile · Markdown · JSON