Salesforce incident

Investigations indicate that rolling restarts following a recent release triggered the caching issue. We're manually clearing the cache to resolve the issue and customers are seeing signs of recovery.

Minor Resolved View vendor source →

Salesforce experienced a minor incident on August 27, 2026 affecting POD256 and POD276 and 1 more component, lasting 1h 26m. The incident has been resolved; the full update timeline is below.

Started
Aug 27, 2026, 09:43 AM UTC
Resolved
Aug 27, 2026, 11:09 AM UTC
Duration
1h 26m
Detected by Pingoru
Aug 27, 2026, 09:43 AM UTC

Affected components

POD256POD276POD281POD368

Update timeline

  1. identified Aug 27, 2026, 09:43 AM UTC

    Degradation Started: featureServiceDisruption

  2. monitoring Aug 27, 2026, 09:57 AM UTC

    We're investigating an issue where a subset of Commerce Cloud customers are unable to access Business Manager and are seeing a blank page due to a caching issue. This is causing a delay in invoicing and deadlines. Multiple teams have been engaged and are working to restore services. 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. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  3. monitoring Aug 27, 2026, 10:23 AM UTC

    Investigations indicate that rolling restarts following a recent release triggered the caching issue. We're manually clearing the cache to resolve the issue and customers are seeing signs of recovery. We'll continue clearing the cache for the remaining impacted PODs. Storefronts aren't impacted. We'll provide an update in 30 minutes or sooner if additional information becomes available.