rewindex

ChangesSalesforceService Disruption: Core Service

Salesforce: Major incident: Service Disruption: Core Service

Major incidentmajor (vendor)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: investigating
AddedStart time#4
Before: not present
After: 2026-10-27 20:59 UTC
AddedAffected components#5
Before: not present
After: 3 instances, Core Service
AddedUpdateupdate#6
Before: not present
After: We're aware of an issue impacting multiple Salesforce instances. Since approximately 20:59 UTC, customers on affected instances may have been unable to log in or access their services. We've engaged our third-party partners to assist in the investigation. We'll provide an update in 30 minutes or sooner if additional information becomes available.
AddedUpdateupdate#7
Before: not present
After: We've determined that the issue is not due to a third-party service disruption. We're now investigating recent changes that may be related, and we're working to find the best path to resolution.

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

TodayWednesday, October 28Wed, Oct 28

3 incident changes

YesterdayTuesday, October 27Tue, Oct 27

3 incident changes

All Salesforce changesSalesforce profileMarkdownJSON