Salesforce: Performance Degradation: Core Service
Part of an outage event
AWS outage, Jul 16, 2026 · 27 vendors, 29 incidents
Salesforce’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +35 min vs AWS’s own post)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>posted 08:44 UTC"]:::root
before["Posted before AWS did<br/>2 vendors, 1 blamed AWS<br/>FusionAuth, Upstash"]:::blames
root --> before
h1["Within an hour<br/>2 vendors, 2 blamed AWS<br/>Coda, Grammarly"]:::blames
root --> h1
p0["Anthropic<br/>posted −5 min, did not name AWS"]:::timing
root -.-> p0
k0["GitHub, GitHub Copilot<br/>+12 h 21 min"]:::hop2
p0 -->|"blamed Anthropic"| k0
me["Salesforce (this incident)<br/>posted +35 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.
Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab).