Changes Salesforce Service Disruption: Core Service

Salesforce: Incident updated: Service Disruption: Core Service

Incident updateNormal progress (typesafe/jev-1.13-20260917, 100%)Changed 2026-10-23 04:03 UTCstatus.salesforce.com

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.

AddedAffected components#1

not present

81 instances

RemovedAffected components#2

~~73 instances~~

removed

AddedUpdateupdate2026-10-23 03:35 UTC#3

not present

Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.

AddedUpdateupdate2026-10-23 03:49 UTC#4

not present

We’ve identified a mismatch between a recent application update and a database change, stopping users from logging in. We’re planning to roll back the update across impacted instances. We’re also preparing to test a newer version on one of impacted instance to validate whether it restores user access. We’ll provide an 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.

Oct 23
Before captured 03:33 UTC
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on Oct 24, 00:41 UTC. Record hash 02c6fec36b52e269…
Download proof
Oct 23
After captured 04:03 UTC
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on Oct 24, 00:41 UTC. Record hash dd040acdc85c631d…
Download proof

History of this incident

Friday, October 23

13 incident changes

Normal progress
09:03Incident
Incident updateService Disruption: Core Service
Impact downgraded
08:33Incident
Incident updateService Disruption: Core Service
Minor edit
08:03Incident
Incident updateService Disruption: Core Service
Impact downgraded
07:33Incident
Incident updateService Disruption: Core Service
Impact downgraded
07:03Incident
Incident updateService Disruption: Core Service
Impact downgraded
06:33Incident
Incident updateService Disruption: Core Service
Root cause removed
06:03Incident
Incident updateService Disruption: Core Service
Normal progress
05:33Incident
Incident updateService Disruption: Core Service
Normal progress
05:03Incident
Incident updateService Disruption: Core Service
Normal progress
04:33Incident
Incident updateService Disruption: Core Service
Normal progress
04:03Incident
Incident updateService Disruption: Core Servicethis change
Normal progress
03:33Incident
Incident updateService Disruption: Core Service
Outage
01:25Major 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 04:03 UTC (change 3 of 13).

Title: Incident updated: Service Disruption: Core Service
Vendor: Salesforce
Date: 2026-10-23 04:03 UTC
URL: https://rewindex.com/change/ra5337d8db1bc32

All Salesforce changes Salesforce profile Markdown JSON