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
a8b1a508b101186b…After captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a678a22f19adc4b8…
History of this incident
Friday, October 23
2 incident changes
- Normal progressIncident
Incident updateService Disruption: Core Servicethis change
- OutageMajor incident
Service Disruption: Core Service
Salesforce reported a major Core Service disruption affecting 4 instances from 2026-10-23 01:25 UTC to 2026-10-23 06:00 UTC, lasting 4 h 35 min. A recent release prevented login sessions from being created, blocking users from logging in; Salesforce deployed a fix forward and restored access.
Cite this
Incident updated: Service Disruption: Core Service on Salesforce’s status page, changed 2026-10-23 08:03 UTC (change 2 of 2).
- Title
- Incident updated: Service Disruption: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/change/r7d711fc2845ec1