Salesforce: Degradation: Agentforce (36 instances)

Salesforce · salesforce.comImpact: minorResolved2026-09-08 22:41 UTC

Public — what happened

Summary

We have identified a potential fix and are preparing to apply it to affected customer environments. We’ll monitor session tagging performance following the change to determine whether functionality recovers while our investigation into the underlying issue continues. We’ll provide another update as significant progress is made.

Timeline

Started — 2026-09-08 20:19 UTC
Last update — 2026-09-08 22:41 UTC
Resolved — 2026-09-08 23:23 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.