Salesforce incident

We've completed a restart on one impacted instance, which is showing positive signs of recovery. We're monitoring this instance for stability before extending the restart to the remaining impacted ins

Resolved after 3 hours 14 minutes, affecting AUS102 and AUS14S and 1 more, on August 4, 2026.

monitoring Aug 04, 2026, 11:20 AM UTC

We've completed a restart on one impacted instance, which is showing positive signs of recovery. We're monitoring this instance for stability before extending the restart to the remaining impacted instances. We will provide an update in 30 minutes, or sooner if additional information becomes available.

Started
Aug 04, 2026, 08:55 AM UTC
Resolved
Aug 04, 2026, 12:10 PM UTC
Duration
3h 14m
Detected by Pingoru
Aug 04, 2026, 08:55 AM UTC

Affected components

AUS102AUS14SAUS16SAUS18SAUS20SAUS22SAUS24SAUS26SAUS28SAUS2S

Update timeline

  1. identified Aug 04, 2026, 08:55 AM UTC

    Degradation Started: featureServiceDisruption

  2. monitoring Aug 04, 2026, 09:23 AM UTC

    We continue to investigate an issue affecting Einstein Bots, where event log data is unavailable in Report Explorer for a subset of customers. An initial rollback attempt was unsuccessful. We’ve identified the likely trigger and are preparing a fix. We will provide an update in 30 minutes, or sooner if additional information becomes available.

  3. monitoring Aug 04, 2026, 09:47 AM UTC

    Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.

  4. monitoring Aug 04, 2026, 10:01 AM UTC

    We’ve determined that the service is failing to start correctly during the rollback process, and are working to resolve the startup failure and restore the service. We'll provide an update in 30 minutes, or sooner if additional information becomes available.

  5. monitoring Aug 04, 2026, 10:40 AM UTC

    We've identified a specific trigger blocking the rollback and we're pursuing an alternative path to restore service. We will provide an update in 30 minutes or sooner if additional information becomes available.

  6. monitoring Aug 04, 2026, 11:20 AM UTC

    We've completed a restart on one impacted instance, which is showing positive signs of recovery. We're monitoring this instance for stability before extending the restart to the remaining impacted instances. We will provide an update in 30 minutes, or sooner if additional information becomes available.

Your product runs on more than Salesforce

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →