rewindex

ChangesSalesforceService Disruption: Core Service

Salesforce: Incident updated: Service Disruption: Core Service

Incident updateNot classified yetChanged 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.

ChangedStatus#1
Before: investigating
After: resolved
AddedResolved time#2
Before: not present
After: 2026-10-28 02:02 UTC
AddedUpdateupdate#3
Before: not present
After: Once we successfully completed the validation steps in the lower environment, and confirmed connectivity was restored. We applied the same fix to the production environment and confirmed customers on affected instances can now log in and access their services. This issue is now resolved. We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

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.

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

Rewindex captured this after the last checkpoint; the next run () commits it.

History of this incident

TodayWednesday, October 28Wed, Oct 28

3 incident changes

YesterdayTuesday, October 27Tue, Oct 27

3 incident changes

All Salesforce changesSalesforce profileMarkdownJSON