rewindex

ChangesSalesforceService Disruption: Core Service

Salesforce: Incident deleted: Service Disruption: Core Service

Incident deletedDeleted by vendor (rule)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

Part of an outage event

Salesforce outage, Sep 16, 2026 · 16 vendors, 21 incidents

Salesforce’s incident is the root of the event (the provider’s own post). (root, posted +1 h 53 min vs Salesforce’s own post)

See the cascade chart and every vendor →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

What changed

Struck in red is what Salesforce removed; blue is what they added. Muted text is unchanged context.

RemovedTitle#1
Before: Service Disruption: Core Service
After: removed
RemovedImpact#2
Before: major
After: removed
RemovedStatus#3
Before: resolved
After: removed
RemovedStart time#4
Before: 2026-09-16 09:12 UTC
After: removed
RemovedResolved time#5
Before: 2026-09-16 09:24 UTC
After: removed
RemovedAffected components#6
Before: 1 instance, Core Service
After: removed
RemovedUpdateupdate#7
Before: We're aware of an issue that impacted multiple instances across all regions. Customers experienced severe delays, intermittent errors, or an inability to access some services. Some customers were also unable to submit new support cases through the Help portal. One of our core system components experienced increased load, which limited its capacity to process requests. We also checked with our third-party infrastructure provider, who confirmed there were no issues on their end. We rolled out a fix that resolved the issue and fully restored services. For more detailed updates about this incident, please follow the updates here in the main Trust post: https://status.salesforce.com/incidents/20004433. 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.
After: removed
RemovedUpdateupdate#8
Before: During our investigation we’ve identified some instances to have a different scope of impact as initially understood and communicated in the supplemental Trust post: https://status.salesforce.com/incidents/20004434. As a result, we’ve adjusted its status and created this one to facilitate this new understanding. We thank you for your patience and understanding.
After: removed

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 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

TodayTuesday, October 20Tue, Oct 20

1 rewrite

Wednesday, September 16

1 incident change

All Salesforce changesSalesforce profileMarkdownJSON