ChangesSalesforceService Disruption: Core Service
Salesforce: Incident updated: Service Disruption: Core Service
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.
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.
Before captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
6569827316ec5181…After captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
f13776cf8938ea97…
History of this incident
Friday, October 23
2 incident changes
- Duration shortenedIncident
Incident updateService Disruption: Core Servicethis change
- OutageMajor incident
Service Disruption: Core Service
Salesforce reported a major Core Service disruption across 16 instances starting 2026-10-23 01:25 UTC, resolved at 2026-10-25 05:33 UTC after 2 days 4 h. A recent release prevented login sessions from being created; Salesforce deployed a fix forward and stated that users could log in and open their orgs again.
Cite this
Incident updated: Service Disruption: Core Service on Salesforce’s status page, changed 2026-10-23 08:33 UTC (change 2 of 2).
- Title
- Incident updated: Service Disruption: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/change/r39efda916cd310