rewindex

ChangesSalesforceService Disruption: Core Service

Salesforce: Incident updated: Service Disruption: Core Service

Incident updateNormal progress (rule, 100%)Changed status.salesforce.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Salesforce removed; blue is what they added. Muted text is unchanged context.

AddedUpdateupdate#1
Before: not present
After: We have identified the fix-forward deployment as our path to full recovery and are expediting its rollout across all remaining impacted instances. Deployment is currently underway across multiple instances, and we do not yet have an estimated time for completion. Users on instances that have not received the updated version may continue to experience issues logging in or accessing their orgs. We will post separate updates as each impacted instance recovers and provide our next update in 30 minutes, or sooner if additional information becomes available.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Friday, October 23

13 incident changes

Cite this

Incident updated: Service Disruption: Core Service on Salesforce’s status page, changed 2026-10-23 05:33 UTC (change 6 of 13).

Title
Incident updated: Service Disruption: Core Service
Vendor
Salesforce
Date
URL
https://rewindex.com/change/r60d815bd091348

All Salesforce changesSalesforce profileMarkdownJSON