Live / Salesforce / Incident
Salesforce: Degradation: coreService (179 instances)
Salesforce · salesforce.comMinor incidentResolved2026-11-11 20:13 UTC
Public — what happened
Summary
Salesforce said some customers on instances that received a recent release were hit by a disruption starting around 18:23 UTC on 2026-11-11. They reported intermittent failures when compiling or deploying Apex code, and in some cases trouble logging in or completing related processes. Salesforce said it believes a change to a supporting runtime library in that release was the likely trigger, halted further rollout, and began returning affected instances to the previous version. By 20:13 UTC it said the rollback was nearly finished, with a few instances still completing it, and the incident was still listed as under investigation.
Timeline
- Started — 2026-11-11 18:23 UTC
- Investigating — 2026-11-11 18:34 UTC (5 updates)
- Resolved — 2026-11-11 20:13 UTC · 1h 50m 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 47, 2026, our weekly internet health report.