Live / Salesforce / Incident
Salesforce: Degradation: coreService
Salesforce · salesforce.comMinor incidentResolved2026-11-02 18:12 UTC
Public — what happened
Summary
Salesforce reported a minor degradation affecting a component it labeled coreService, beginning at 16:49 UTC on 2026-11-02. The company said it first began looking into what was wrong, and by 17:05 UTC it said it had found a potential cause and was working on a fix to reduce the effect on customers. It did not say which customers were affected or how, and as of the latest update the issue was not resolved, with Salesforce promising another update within 30 minutes.
Timeline
- Started — 2026-11-02 16:49 UTC
- Investigating — 2026-11-02 16:49 UTC (2 updates)
- Resolved — 2026-11-02 18:12 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 46, 2026, our weekly internet health report.