rewindex

ChangesSalesforceService Disruption: Core Service

Salesforce: Incident updated: Service Disruption: Core Service

Incident updateNormal progress (typesafe/jev-1.13-20260917, 71%)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.

AddedAffected components#1
Before: not present
After: 88 instances
RemovedAffected components#2
Before: 89 instances
After: removed
AddedUpdateupdate#3
Before: not present
After: We confirmed that a fix forward has restored access on the second impacted instance USA1072 at 04:11 UTC. We're now preparing to deploy this fix forward to the remaining impacted instances. Users on the remaining impacted instances may continue to experience login failures or be unable to access their orgs. We'll post a separate Trust update for each instance that receives the fix, so each shows an accurate end time 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.

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:03 UTC (change 5 of 13).

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

All Salesforce changesSalesforce profileMarkdownJSON