Salesforce: Degradation: analytics (84 instances)

Salesforce · salesforce.comImpact: minorinvestigating2026-10-04 15:22 UTC

Public — what happened

Summary

Salesforce reported a minor degradation affecting its analytics service across 84 instances, beginning on 2026-10-04 at 13:07 UTC. The company said the problem was linked to high memory use in a supporting service, and that its teams were examining logs and diagnostic data while trying several approaches to pinpoint the root cause. As of its latest update, Salesforce listed the incident as still under investigation and not yet resolved, and said it planned to post another update within 30 minutes.

Timeline

Started — 2026-10-04 13:07 UTC
Last update — 2026-10-04 15:22 UTC
Ongoing at last check.

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in 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 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 →

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