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: major (vendor)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 18:06 UTC
Before: not present
After: 2025-11-01 20:23 UTC
Before: not present
After: 1 instance, Core Service
Before: not present
After: At 18:06 UTC on November 1, 2025, we observed a service disruption impacting IND76, IND82, IND126, and IND134 instances. Users are unable to access their services. We identified a potential issue at the database level caused by a recent configuration change. To resolve this, we are redeploying the release.
We will provide an update once the redeployment is completed or sooner if we have more information.
Before: not present
After: IND134 is out of impact as of 19:30 UTC.
We have updated the posting to reflect the currently impacted instances.
We are redeploying the release on the remaining instances and will provide an update once the redeployment is completed or sooner if we have more information.
Before: not present
After: IND76, IND82 and IND126 are out of impact as of 19:45 UTC, 20:22 UTC and 20:23 UTC, respectively.
We successfully redeployed the release, resolving the issue. Customers can now access their services
We apologize for any inconvenience this incident may have caused you and your business.
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