Salesforce incident

We're investigating an issue affecting a subset of sandbox and production environments where users may experience their sessions expiring shortly after signing in, requiring them to authenticate again

Minor Resolved View vendor source →

Salesforce experienced a minor incident on September 2, 2026 affecting ARE2S and AUS14S and 1 more component, lasting 50m. The incident has been resolved; the full update timeline is below.

Started
Sep 02, 2026, 05:47 PM UTC
Resolved
Sep 02, 2026, 06:38 PM UTC
Duration
50m
Detected by Pingoru
Sep 02, 2026, 05:47 PM UTC

Affected components

ARE2SAUS14SAUS18SAUS20SAUS22SAUS24SAUS26SAUS2SAUS36SAUS38S

Update timeline

  1. identified Sep 02, 2026, 05:47 PM UTC

    Degradation Started: featurePerfDegradation

  2. monitoring Sep 02, 2026, 05:52 PM UTC

    Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.

  3. monitoring Sep 02, 2026, 06:02 PM UTC

    We're investigating an issue affecting a subset of sandbox and production environments where users may experience their sessions expiring shortly after signing in, requiring them to authenticate again. We've identified a recent change that may be contributing to the issue and are deploying a configuration change to mitigate the impact. We're monitoring the rollout and validating recovery. We'll provide an update in 30 minutes or sooner as more information becomes available.