Salesforce incident

We’ve successfully validated the fix and are preparing to deploy it to all impacted environments.

Minor Resolved View vendor source →

Salesforce experienced a minor incident on May 6, 2026 affecting IND100 and IND102 and 1 more component, lasting 7h 52m. The incident has been resolved; the full update timeline is below.

Started
May 06, 2026, 04:40 PM UTC
Resolved
May 07, 2026, 12:32 AM UTC
Duration
7h 52m
Detected by Pingoru
May 06, 2026, 04:40 PM UTC

Affected components

IND100IND102IND104IND108IND10SIND110IND112IND114IND116IND118

Update timeline

  1. identified May 06, 2026, 04:40 PM UTC

    Degradation Started: featureServiceDisruption

  2. monitoring May 06, 2026, 04:40 PM UTC

    We are aware of an issue affecting Einstein Voice for Agentforce (AFV). As a result, customers are unable to create new voice sessions. We've identified a configuration issue and are working to deploy a fix on an expedited basis. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  3. monitoring May 06, 2026, 05:30 PM UTC

    We continue to investigate an issue affecting Agentforce Voice where a subset of customers may be unable to initiate new voice sessions. We've identified an issue with ‌metadata configuration and are working to deploy a fix which is expected to take several hours. We'll provide an update in 120 minutes or sooner if additional information becomes available.

  4. monitoring May 06, 2026, 06:04 PM UTC

    Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that have not experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused.

  5. monitoring May 06, 2026, 06:10 PM UTC

    As we have confirmed this issue to only be impacting sandbox environments, all production instances have been removed from this post. We are continuing to work on the fix for this issue and will provide an update when additional information becomes available.

  6. monitoring May 06, 2026, 09:20 PM UTC

    We’ve successfully validated the fix and are preparing to deploy it to all impacted environments. We’ll provide the next update as additional information becomes available.