Salesforce: Disruption: Platform

Salesforce · salesforce.comImpact: majorResolved2026-09-25 18:53 UTC

Public — what happened

Summary

Recurrence of the earlier US2 incident — same root cause. The US2 Redis cache is again at its memory limit and rejecting writes. Impact:logins disruption

Timeline

Started — 2026-09-25 18:51 UTC
Last update — 2026-09-25 18:53 UTC
Resolved — 2026-09-25 18:53 UTC

Source of record: provider status page. Mirrored as reported; 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.