Live / Salesforce / Incident
Salesforce: Disruption: coreService
Salesforce · salesforce.comMajor incidentResolved2026-10-23 08:38 UTC
Public — what happened
Summary
Salesforce reported a major disruption affecting its coreService on 3 instances, beginning at 02:35 UTC on 2026-10-23. The company said it confirmed that some users were unable to log in to their org and were shown an error message. Salesforce said it had started restarting its servers in stages to bring access back and was still looking into the cause. As of its last update at 02:51 UTC, the incident was not resolved, and the company said it would post another update within 30 minutes.
Timeline
- Started — 2026-10-23 02:35 UTC
- Investigating — 2026-10-23 02:51 UTC (18 updates)
- Resolved — 2026-10-23 08:38 UTC · 6h 03m 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 44, 2026, our weekly internet health report.