Salesforce: Performance Degradation: Core Service
Intercom outage, Jan 9, 2026 · 6 vendors, 6 incidents
Salesforce’s incident started in the same window without naming Intercom (timing only, not evidence of a link). (timing only, posted +45 min vs the first vendor naming Intercom)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Intercom<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>3 vendors, 3 blamed Intercom<br/>Lattice, Sigma Computing, Segment"]:::blames
root --> h1
me["Salesforce (this incident)<br/>posted +45 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
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.
Affected components: Core Service1 instance
Timeline of updates
The vendor published no update text for this incident.
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.
First version captured 05:26 UTC
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on Oct 19, 23:18 UTC. Record hash
de402e8a4d518111…
Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab).