rewindex

ChangesSalesforceService Disruption: Core Service

Salesforce: Major incident: Service Disruption: Core Service

Major incidentoutage (model (Jev), 100%)Changed Detected 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.

AddedTitle#1
Before: not present
After: Service Disruption: Core Service
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-10-23 01:25 UTC
AddedResolved time#5
Before: not present
After: 2026-10-23 06:18 UTC
AddedAffected components#6
Before: not present
After: 8 instances, Core Service
AddedUpdateupdate#7
Before: not present
After: We resolved an issue that prevented users from logging in. We identified an issue with a recent release that prevented login sessions from being created. We deployed a fix forward, and access is now restored. Users can log in and open their orgs again. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

First version of this incident archived by Rewindex. 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 this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

YesterdayFriday, October 23Fri, Oct 23

1 incident change

All Salesforce changesSalesforce profileMarkdownJSON