Live / Salesforce / Incident
Salesforce: Degradation: coreService (12 instances)
Salesforce · salesforce.comMinor incidentResolved2026-11-10 16:35 UTC
Public — what happened
Summary
Salesforce said customers on 12 Core instances have been seeing slower-than-normal page loads across most operations since about 15:12 UTC on 2026-11-10, and it rated the incident minor. The company said it is looking at a possible link to many customer orgs moving between instances over the weekend, and is also reviewing two recent changes common to some of the affected instances. By 16:18 UTC it said more instances were affected than it first understood, and by 16:21 UTC it said load times were stable but still slow, with recovery not yet confirmed. Salesforce said it was preparing a change to shift the affected instances to a different part of its caching system, and the incident is still being investigated.
Timeline
- Started — 2026-11-10 15:12 UTC
- Investigating — 2026-11-10 15:40 UTC (4 updates)
- Resolved — 2026-11-10 16:35 UTC · 1h 23m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Salesforce against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Salesforce: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Salesforce report →
More from Salesforce
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.