Salesforce incident

We're continuing to monitor the remaining backlog as it processes, and expect it to fully populate over the next several hours.

Minor Resolved View vendor source →

Salesforce experienced a minor incident on September 25, 2026 affecting POD217 and POD240 and 1 more component, lasting 12h 1m. The incident has been resolved; the full update timeline is below.

Started
Sep 25, 2026, 11:29 AM UTC
Resolved
Sep 25, 2026, 11:31 PM UTC
Duration
12h 1m
Detected by Pingoru
Sep 25, 2026, 11:29 AM UTC

Affected components

POD217POD240POD244POD248POD253POD256POD258POD267POD270POD284

Update timeline

  1. identified Sep 25, 2026, 11:29 AM UTC

    Degradation Started: featurePerfDegradation

  2. monitoring Sep 25, 2026, 11:35 AM UTC

    We're investigating an issue affecting Commerce Cloud users' ability to view site visit traffic data. Some customers are seeing zero values when accessing their traffic dashboard. Site visits are occurring, but the dashboard isn't displaying them. We've engaged our engineering teams to restore full visibility into traffic data. We've also determined 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.

  3. monitoring Sep 25, 2026, 12:00 PM UTC

    We're continuing to investigate the issue and are working to fully understand the scope of the impact. We have confirmed that the traffic data is being recorded correctly it's just not displaying in dashboards. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  4. monitoring Sep 25, 2026, 12:28 PM UTC

    We're working to understand why the data isn't being processed correctly. We're in the process of analyzing error logs to determine the trigger of the issue and possible remediation steps needed. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  5. monitoring Sep 25, 2026, 12:50 PM UTC

    We’ve confirmed the trigger of the issue, the pipeline that processes the traffic data became blocked. We’re working to perform a configuration change to unblock the traffic data. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  6. monitoring Sep 25, 2026, 01:18 PM UTC

    We're continuing to perform the necessary configuration change to unblock the processing of the site visit traffic data. Once this is complete, we’ll validate that the processing of the backlog is has begun. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  7. monitoring Sep 25, 2026, 01:44 PM UTC

    We’ve completed the necessary configuration change to unblock the site visit traffic data processing issue. The traffic data is expected to take several hours to completely process and appear in customer dashboards. We'll provide an update in 5 hours, or sooner if additional information becomes available.

  8. monitoring Sep 25, 2026, 01:49 PM UTC

    We've identified additional impacted instances and updated this messaging to reflect them. These customers will now receive communications about this incident going forward. These customers are also seeing zero values when accessing their site view traffic dashboard. We've completed the remediation step. The processing of the data backlog is now underway and will take several hours to complete. We'll provide an update in 5 hours, or sooner if additional information becomes available.

  9. monitoring Sep 25, 2026, 07:55 PM UTC

    We're continuing to monitor the remaining backlog as it processes, and expect it to fully populate over the next several hours. We'll provide another update as additional information becomes available.