Live  /  Salesforce  /  Incident

Salesforce: Degradation: coreService (12 instances)

Salesforce · salesforce.comMinor incidentResolved2026-11-13 04:02 UTC
Public — what happened

Summary

Salesforce said a minor degradation affecting a core service on 12 instances began at 03:12 UTC on 2026-11-13. The company reported slower page loads, including Setup pages, and intermittent timeouts for some customers. By 03:51 UTC it said it had found a recent change that may be the trigger, and it was still investigating. It also said the number of affected instances turned out to be larger than first thought, and that customers on those instances will be contacted. The incident was not marked resolved.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Salesforce status & history page.

Related: Salesforce status & history. SquidGrid is not affiliated with Salesforce.