Live / Incidents / Salesforce
Salesforce: Disruption: coreService
Salesforce · salesforce.comImpact: majorResolved2026-09-18 23:30 UTC
Public — what happened
Summary
We're aware of an issue that impacted multiple instances across all regions. Customers experienced severe delays, intermittent errors, or an inability to access some services. Some customers were also unable to submit new support cases through the Help portal.
One of our core system components experienced increased load, which limited its capacity to process requests. We also checked with our third-party infrastructure provider, who confirmed there were no issues on their end.
We rolled out a fix that resolved the issue and fully restored services.
For more detailed updates about this incident, please follow the updates here in the main Trust post: https://status.salesforce.com/incidents
Timeline
- Started — 2026-09-18 23:30 UTC
- Last update — 2026-09-18 23:30 UTC
- Resolved — 2026-09-18 23:30 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 →