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
f59cbebf90695181…After captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
aae020bca1e6175a…
History of this incident
Friday, October 23
13 incident changes
- Normal progressIncident
Incident updateService Disruption: Core Service
- Impact downgradedIncident
Incident updateService Disruption: Core Service
- Minor editIncident
Incident updateService Disruption: Core Servicethis change
- Impact downgradedIncident
Incident updateService Disruption: Core Service
- Impact downgradedIncident
Incident updateService Disruption: Core Service
- Impact downgradedIncident
Incident updateService Disruption: Core Service
- Root cause removedIncident
Incident updateService Disruption: Core Service
- Normal progressIncident
Incident updateService Disruption: Core Service
- Normal progressIncident
Incident updateService Disruption: Core Service
- Normal progressIncident
Incident updateService Disruption: Core Service
- Normal progressIncident
Incident updateService Disruption: Core Service
- Normal progressIncident
Incident updateService Disruption: Core Service
- OutageMajor incident
Service Disruption: Core Service
Salesforce reported a major Core Service disruption affecting 3 instances starting 2026-10-23 01:25 UTC; affected users could not log in to their org and saw an error message. It remained open when archived, 1 h 26 min at the last update; Salesforce was restarting servers in stages to restore access and investigating the cause.
Cite this
Incident updated: Service Disruption: Core Service on Salesforce’s status page, changed 2026-10-23 08:03 UTC (change 11 of 13).
- Title
- Incident updated: Service Disruption: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/change/r01a47d9d73a0ab