Live / Salesforce / Incident
Salesforce: Disruption: coreService (4 instances)
Salesforce · salesforce.comMajor incidentResolved2026-10-28 01:38 UTC
Public — what happened
Summary
Salesforce reported a major disruption affecting several of its instances, saying that since about 20:59 UTC on October 27 customers on those instances may have been unable to log in or use their services. The company said it ruled out a third-party service problem and began reversing a recent change, later describing it as a network configuration change, which it had rolled back in a lower environment and was still validating before applying to production. Around 01:38 UTC on October 28, Salesforce said more instances were affected than it first understood and that those customers would be contacted. As of the latest update the incident was still under investigation and not marked resolved.
Timeline
- Started — 2026-10-27 21:41 UTC
- Investigating — 2026-10-27 21:41 UTC (8 updates)
- Resolved — 2026-10-28 01:38 UTC · 3h 57m 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 45, 2026, our weekly internet health report.