Salesforce: Performance Degradation: Core Service
No longer in Salesforce’s live feed; still on their status history.
Salesforce outage, Sep 16, 2026 · 6 vendors, 11 incidents
Salesforce’s incident is the root of the event (the provider’s own post). (root, posted +0 min vs Salesforce’s own post)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Salesforce<br/>posted 07:19 UTC"]:::root
h4["1 to 4 hours later<br/>4 vendors, 4 blamed Salesforce<br/>Braze, Gong, ClickHouse Cloud, Smartsheet"]:::blames
root --> h4
later["Later<br/>1 vendor, 1 blamed Salesforce<br/>Salesloft"]:::blames
root --> later
class root 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
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
aed67182637bdb45…
Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Salesforce, started 2026-09-16 07:19 UTC, resolved after 6 min, 0 update(s).
- Title
- Performance Degradation: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20004432
Salesforce profileRecent Salesforce incidentsAll outages on September 16, 2026Salesforce in September 2026MarkdownJSON