Changes / Salesforce / Agentforce Service Disruption: Agentforce
Salesforce: Major incident: Agentforce Service Disruption: Agentforce
Summary
Summary pending. The diff below shows exactly what changed.
Major incidentLabel: outage (model (Jev), 100%)Changed Detected Source: status.salesforce.com (opens in new tab)
Incident page: full timeline of updates →
What changed
Before: not present
After: Agentforce Service Disruption: Agentforce
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2025-10-20 06:50 UTC
Before: not present
After: 2025-10-20 09:22 UTC
Before: not present
After: 76 instances, Agentforce
Before: not present
After: On October 20, 2025, at 06:50 UTC, multiple Salesforce clouds, including Agentforce, experienced a widespread service disruption caused by a Domain Name System (DNS) issue at a third-party cloud infrastructure vendor. Incoming traffic to the planner/service Application Programming Interface (API) was failing, which affected task execution for impacted customers. Agentforce services were fully restored, and the issue was resolved at 09:22 UTC. The vendor implemented a fix forward, and we closely monitored recovery, scaling resources where needed to stabilize performance.
This incident is part of a multi-cloud Service Disruption. Further investigation and details can be found here: https://status.salesforce.com/generalmessages/20000226
We apologize for how you and your business may have been affected by this incident. Salesforce is fully committed to minimizing downtime when incidents do occur. We also continually assess and improve our tools, processes, and architecture to provide you with the best service possible.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Agentforce Service Disruption: Agentforce (this change) | Major incident |
All Salesforce changes → · Salesforce profile · Markdown · JSON