Live / Incidents / Salesforce
Salesforce: Disruption: coreService (912 instances)
Salesforce · salesforce.comImpact: majorResolved2026-09-16 18:46 UTC
Public — what happened
Summary
Service telemetry remains healthy, and our review has not confirmed any ongoing customer impact related to this incident. Before declaring the issue resolved, we’re ensuring the existing mitigation remains active across all affected customer-facing Hyperforce environments.
We’re applying targeted updates where the automated process did not complete, helping maintain service stability and reduce the risk of impact returning. We’ll provide another update in 30 minutes or sooner if additional information becomes available.
Timeline
- Started — 2026-09-16 08:32 UTC
- Last update — 2026-09-16 18:46 UTC
- Resolved — 2026-09-16 18:58 UTC
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 →