Tableau Cloud Outage History

Started Sep 25, 2026, 06:51 PM UTC· resolved Sep 25, 2026, 08:51 PM UTC

1. identified Sep 25, 2026, 06:51 PM UTC

   Disruption Started: datoramaServiceDisruption

2. monitoring Sep 25, 2026, 06:53 PM UTC

   Recurrence of the earlier US2 incident — same root cause. The US2 Redis cache is again at its memory limit and rejecting writes. Impact:logins disruption

Read the full incident report →

Started Sep 25, 2026, 11:29 AM UTC· resolved Sep 25, 2026, 11:27 PM UTC

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.

Read the full incident report →

Started Sep 25, 2026, 08:55 AM UTC· resolved Sep 25, 2026, 10:45 AM UTC

1. identified Sep 25, 2026, 08:55 AM UTC

   Degradation Started: marketingCloudFeatureDisruption

2. monitoring Sep 25, 2026, 09:12 AM UTC

   We're investigating an issue impacting login access to Stack 401 for Marketing Cloud Engagement. Affected users are unable to log in to this Stack. We've engaged multiple engineering teams to review database and caching services. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Sep 25, 2026, 09:50 AM UTC

   As we continue to investigate the login issue impacting Stack 401 in Marketing Cloud Engagement, we identified timeout errors on login token requests and are reviewing the health of the caching and database services connected to this Stack. We’ve also identified a high volume of login requests originating from a small number of integrations. We're implementing rate limits on these requests to see if this resolves the issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Sep 25, 2026, 10:26 AM UTC

   We've identified the specific integration that's generating a high volume of login requests to Stack 401 in Marketing Cloud Engagement and have applied rate limits to those requests. We’re validating the changes and monitoring login access. We've also confirmed there are no underlying database issues on the Stack. We'll provide another update within 30 minutes, or sooner if new information becomes available.

Read the full incident report →

Started Sep 25, 2026, 02:30 AM UTC· resolved Sep 25, 2026, 06:30 AM UTC

1. identified Sep 25, 2026, 02:30 AM UTC

   Degradation Started: featureServiceDisruption

2. monitoring Sep 25, 2026, 02:50 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.

3. monitoring Sep 25, 2026, 02:58 AM UTC

   We identified a certificate expiry, disrupting requests to the Discovery service and causing search and index rebuild failures. We're validating certificate status across all impacted environments before rotating the certificate to restore service. We've also identified additional environments experiencing this issue and are expanding our scope of investigation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Sep 25, 2026, 03:21 AM UTC

   We've confirmed that certificate expiry triggered the issue and are now rotating certificates to restore service. This continues to affect search index rebuilds for a subset of B2B Commerce customers. We're generating new certificates for the affected regions. We'll first rotate the certificate in one region to validate the fix, then roll it out across the remaining affected regions in parallel. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Sep 25, 2026, 03:56 AM UTC

   We’ve generated the certificates required for rotation and are now working on the activation requests. The issue continues to affect search index rebuilds for a subset of B2B Commerce customers. We’ll provide an update in 30 minutes, or sooner if additional information becomes available.

6. monitoring Sep 25, 2026, 04:22 AM UTC

   We've rotated the certificate in the first affected region and updated the search service. We're now validating the logs to confirm the fix before rolling out the certificate rotation across the remaining affected regions in parallel. We'll provide an update in 30 minutes or sooner if additional information becomes available.

7. monitoring Sep 25, 2026, 05:21 AM UTC

   We're still validating the rotated certificate in the first affected region. We've also identified this issue affecting additional environments and are expanding our investigation to determine the full scope of impact. We'll provide an update in 30 minutes or sooner if additional information becomes available.

8. monitoring Sep 25, 2026, 05:31 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.

9. monitoring Sep 25, 2026, 06:06 AM UTC

   We completed a certificate rotation and restarted application services in the first affected region, and validation confirmed this was successful. We're now rolling out the certificate rotation across the remaining affected regions in parallel. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Sep 24, 2026, 02:55 PM UTC· resolved Sep 24, 2026, 04:32 PM UTC

1. identified Sep 24, 2026, 02:55 PM UTC

   Degradation Started: herokuFeatureDegradation

2. monitoring Sep 24, 2026, 03:09 PM UTC

   At 13:31 UTC on September 24, 2026, some Common Runtime customers began experiencing intermittent loss of application logs in the US region. Our engineers are working to resolve the issue.

3. monitoring Sep 24, 2026, 03:51 PM UTC

   Engineers are continuing to investigate this issue. The current known impact is intermittent router logs being dropped in a subset of US regions. App logs are unaffected. We will provide another update in the next 60 mins.

4. monitoring Sep 24, 2026, 04:10 PM UTC

   Engineers have fixed the issue and are monitoring. All router logs are now being successfully delivered.

Read the full incident report →

Started Sep 21, 2026, 03:47 PM UTC· resolved Sep 21, 2026, 06:00 PM UTC

1. identified Sep 21, 2026, 03:47 PM UTC

   Degradation Started: performanceDegradation

2. monitoring Sep 21, 2026, 03:47 PM UTC

   We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.

3. monitoring Sep 21, 2026, 04:32 PM 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 Sep 21, 2026, 04:44 PM UTC

   We're aware of an issue impacting performance where some customers may experience slower response times or delays when using core services on these instances. We have taken steps to increase system capacity on the impacted instances as we continue to investigate the underlying trigger. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Sep 21, 2026, 05:15 PM UTC

   Some customers may still experience slower response times or delays when using core services on the impacted instances. We've identified the trigger of this issue as increased database session activity, which is driving elevated cache response times. We're remapping the impacted instances to a newly scaled cache cluster to help restore normal performance, and we're closely monitoring the situation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Sep 21, 2026, 05:43 PM UTC

   We've started remapping to the scaled cache cluster, and the change is still deploying. We expect full propagation across all impacted instances to take up to 60 minutes, after which traffic should stabilize. Some customers may continue to experience slower response times while this rollout completes. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Sep 19, 2026, 11:13 PM UTC· resolved Sep 20, 2026, 05:54 AM UTC

1. identified Sep 19, 2026, 11:13 PM UTC

   Degradation Started: featureServiceDisruption

2. monitoring Sep 19, 2026, 11:46 PM UTC

   We're continuing to investigate the issue affecting Data Cloud activations for customers in the US-east-1 region on our Prod1-CDP1 environment. We've confirmed the issue stems from a third-party cloud storage service, and we're waiting on their team to trace the cause using system logs. Our engineers are preparing alternative options to reduce impact while this investigation continues. We'll provide an update if additional information becomes available.

3. monitoring Sep 20, 2026, 12:21 AM UTC

   We've identified that the issue affecting Data Cloud activations stems from a third-party cloud storage service used in our Prod1 CDP1 environment. We applied a configuration change to that service to help address the errors, and we're preparing an alternate storage option as an additional measure. We're continuing to work directly with the third-party provider and monitoring for improvement. We'll provide an update if additional information becomes available.

4. monitoring Sep 20, 2026, 01:45 AM UTC

   We performed further review and analysis and noted that a few other instances may also be impacted as a result of this incident. We have added those instances to the list. Meanwhile, we're continuing to work directly with the third-party provider and monitoring for improvement. We'll provide an update if additional information becomes available.

Read the full incident report →

Started Sep 18, 2026, 01:06 PM UTC· resolved Sep 18, 2026, 04:27 PM UTC

1. identified Sep 18, 2026, 01:06 PM UTC

   Disruption Started: serviceDisruption

2. monitoring Sep 18, 2026, 01:24 PM UTC

   We're investigating an issue impacting a database supporting Marketing Cloud Engagement, and customers on the impacted database are currently unable to connect. Our investigation points to a potential file lock as the trigger. We've engaged additional support and are preparing a secondary environment in case it is needed. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Sep 18, 2026, 01:49 PM UTC

   We're continuing to investigate a disruption impacting a database supporting Marketing Cloud Engagement, and affected customers remain unable to connect. We've identified that a storage-level lock is likely preventing the database from completing recovery, and our engineering teams are working to resolve it. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Sep 18, 2026, 02:15 PM UTC

   We've ruled out a storage-level file lock as a factor in the ongoing recovery issue impacting Marketing Cloud Engagement. Affected customers remain unable to connect to services on the impacted database. We've started taking the database offline and bringing it back online in an effort to complete recovery. In parallel, we're preparing a secondary database as a backup option. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Sep 18, 2026, 02:45 PM UTC

   We've performed an in-place restart of the impacted Marketing Cloud Engagement database which has moved into a recovery state. Affected customers remain unable to connect to services while recovery completes. We're monitoring progress closely. In parallel, we're preparing a secondary database as a backup option. We'll provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Sep 18, 2026, 03:16 PM UTC

   Affected customers remain unable to connect to the Marketing Cloud Engagement database affected by this incident. We're now evaluating whether to continue recovery efforts on this database or move forward to our secondary database, which is fully prepared. We'll provide an update in 30 minutes or sooner if additional information becomes available.

7. monitoring Sep 18, 2026, 03:55 PM UTC

   We continue to work on restoring the Marketing Cloud Engagement database. A replacement of a failed component on the storage array has been planned, and is expected to take a few hours. The replacement will run parallel to our recovery work without affecting it. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Sep 16, 2026, 07:39 PM UTC· resolved Sep 16, 2026, 08:27 PM UTC

1. identified Sep 16, 2026, 07:39 PM UTC

   Degradation Started: performanceDegradation

2. monitoring Sep 16, 2026, 07:42 PM UTC

   The Salesforce Technology team has completed its investigation and determined that the listed instances and services remained healthy and did not experience impact during the times outlined. We apologize for any inconvenience caused by the false positive notification, and we will undertake a full investigation as we look to improve our impact alerting and assessment configurations.

Read the full incident report →

Started Sep 16, 2026, 08:32 AM UTC· resolved Sep 16, 2026, 07:08 PM UTC

1. identified Sep 16, 2026, 08:32 AM UTC

   Disruption Started: serviceDisruption

2. monitoring Sep 16, 2026, 08:45 AM UTC

   We're investigating an issue impacting multiple instances across all regions where customers may experience severe delays, intermittent errors, or an inability to access some services. Some customers are also unable to submit new support cases through the Help portal. We're investigating the issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Sep 16, 2026, 09:10 AM UTC

   Investigations indicate that requests are stalling while waiting on a response from an internal login service, which is using up available server resources. Customers continue to experience severe delays, intermittent errors, and inability to access some services. This also affects support case creation. We've attempted a rolling restart on one of the impacted instances to see if that resolves the issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Sep 16, 2026, 09:57 AM UTC

   We believe that the issue is caused by an external dependency failure that's impacting the legacy login server. We're blocking the Application Programming Interface (API) endpoint as a potential mitigation step. We also engaged our third-party infrastructure provider to determine if there are any issues and they've confirmed that there are no issues with ‌third-party infrastructure. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Sep 16, 2026, 10:01 AM UTC

   We're no longer pursuing restarts as a path to remediation. Customers continue to experience severe delays, intermittent errors, and inability to access some services and support case creation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Sep 16, 2026, 10:18 AM UTC

   One of our core system components experienced increased load, which limited its capacity to process requests. We're working on a fix to resolve this issue and restore services. We'll provide an update in 30 minutes or sooner if additional information becomes available.

7. monitoring Sep 16, 2026, 10:31 AM UTC

   We're pursuing the fastest path to restore services. We're testing our fix on a test instance. Once the test is validated, we'll roll out the fix fleetwide. Customers continue to experience severe delays, intermittent errors, and inability to access some services and support case creation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

8. monitoring Sep 16, 2026, 10:56 AM UTC

   We've validated the fix successfully on the test instance. We'll now roll out the fix fleetwide to all impacted instances. We'll provide an update in 30 minutes or sooner if additional information becomes available.

9. monitoring Sep 16, 2026, 11:19 AM UTC

   A fleetwide rollout is in progress and customers are starting to see their service return to normal. In parallel, we're working on a code-level permanent fix. We'll provide an update in 30 minutes or sooner if additional information becomes available.

10. monitoring Sep 16, 2026, 11:41 AM UTC

    The rollout is progressing region by region and we're seeing improvement. We don't have a confirmed time of completion. GovCloud customers have been confirmed to be out of impact. Customers may continue to experience severe delays, intermittent errors, and inability to access some services and support case creation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

11. monitoring Sep 16, 2026, 12:13 PM UTC

    The rollout is progressing region-wise and services are returning to normal in regions that are completed. We're monitoring the rollout as it continues, and we're working on a permanent fix. We'll provide an update in 30 minutes or sooner if additional information becomes available.

12. monitoring Sep 16, 2026, 12:39 PM UTC

    As the rollout is progressing region-wise, most instances are recovering. Some customers may still see errors accessing the service until we finish a manual restart on their instance. We don't have a confirmed resolution time. We'll provide an update in 30 minutes or sooner if additional information becomes available.

13. monitoring Sep 16, 2026, 01:13 PM UTC

    We've determined that the rollout didn't fully complete for a number of instances, so some customers may still be experiencing the original issue. We're reapplying the fix now. Some customers may need to clear cached data or restart their session for full recovery. We'll provide an update in 30 minutes or sooner if additional information becomes available.

14. monitoring Sep 16, 2026, 02:00 PM UTC

    We've completed the next phase of the rollout. We're manually restarting ‌instances where the automated fix didn't fully resolve the issue. We’ve received reports of scheduled jobs not running as expected for some customers who are now able to access the service. We're investigating this. Investigations have highlighted that the impact radius is narrower than initially understood. We'll now remove any instances that haven't 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. We'll provide an update in 30 minutes or sooner if additional information becomes available.

15. monitoring Sep 16, 2026, 02:27 PM UTC

    We've completed the next phase of the rollout to the remaining impacted instances. We continue to manually restart ‌instances where the automated fix didn't fully resolve the issue. Customers who are affected may continue to experience severe delays, intermittent errors, and inability to access some services and support case creation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

16. monitoring Sep 16, 2026, 02:56 PM UTC

    We're seeing signs of recovery and many customers are coming out of impact. We continue to manually restart ‌instances where the automated fix didn't fully resolve the issue. We don't have a confirmed resolution time. Customers continue to experience severe delays, intermittent errors, and inability to access some services and support case creation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

17. monitoring Sep 16, 2026, 03:39 PM UTC

    We’ve narrowed the remaining impact to a subset of Hyperforce instances. First-party environments were not impacted. The mitigation is now in place across nearly all affected instances, and we’re completing targeted restarts and manual recovery actions on the remaining affected instances. Some customers may continue to experience severe delays, intermittent errors, and inability to access some services and support case creation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

18. monitoring Sep 16, 2026, 03:56 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.

19. monitoring Sep 16, 2026, 04:23 PM UTC

    We’ve completed applying the mitigation across the affected Hyperforce environments and are conducting fleetwide validation to confirm service recovery. Most customer-facing impact has cleared, while we work through a small number of remaining instances that require additional verification or targeted recovery actions. Customers on any remaining affected instances may continue to experience severe delays, intermittent errors, or difficulty accessing some services and creating support cases. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

20. monitoring Sep 16, 2026, 05:00 PM UTC

    Our telemetry is no longer showing active performance or availability impact across customer-facing Hyperforce environments. We’re validating recent customer reports against service health data and confirming the recovery time before declaring the issue resolved. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

21. monitoring Sep 16, 2026, 05:29 PM UTC

    Service telemetry has remained healthy across customer-facing Hyperforce environments since 15:26 UTC. Our review of recent customer reports has not identified any confirmed ongoing impact related to this incident. The mitigation remains active, and we’re applying additional preventive protections to related service paths while completing final validation. We’ll provide another update in 30 minutes or sooner if additional information becomes available.

22. monitoring Sep 16, 2026, 06:06 PM UTC

    We continue to observe healthy service telemetry across customer-facing Hyperforce environments, and our review of recent customer reports has not confirmed ongoing impact related to this incident. We’re completing validation of one isolated report before declaring the issue resolved. The mitigation remains active, and we’re adding preventive protections to related service paths to reduce the risk of recurrence. We’ll provide another update in 30 minutes or sooner if additional information becomes available.

23. monitoring Sep 16, 2026, 06:46 PM UTC

    Service telemetry remains healthy, and our review has not confirmed any ongoing customer impact related to this incident. Before declaring the issue resolved, we’re ensuring the existing mitigation remains active across all affected customer-facing Hyperforce environments. We’re applying targeted updates where the automated process did not complete, helping maintain service stability and reduce the risk of impact returning. We’ll provide another update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Sep 14, 2026, 05:11 PM UTC· resolved Oct 19, 2026, 04:00 PM UTC

1. identified Sep 14, 2026, 05:11 PM UTC

   Degradation Started: salesforceSpiffFeatureDegradation

2. monitoring Sep 16, 2026, 04:32 PM UTC

   We are investigating a potential cause of the issue.

3. monitoring Sep 18, 2026, 01:42 PM UTC

   We are investigating a potential cause of the issue.

4. monitoring Sep 21, 2026, 04:32 PM UTC

   We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.

5. monitoring Sep 23, 2026, 08:13 PM UTC

   We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information

6. monitoring Sep 25, 2026, 03:45 PM UTC

   We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.

7. monitoring Sep 28, 2026, 04:12 PM UTC

   We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.

8. monitoring Oct 01, 2026, 06:48 PM UTC

   We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information

9. monitoring Oct 05, 2026, 09:18 PM UTC

   We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information

10. monitoring Oct 07, 2026, 07:51 PM UTC

    We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information

11. monitoring Oct 09, 2026, 03:14 PM UTC

    We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information

12. monitoring Oct 12, 2026, 08:15 PM UTC

    We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.

13. monitoring Oct 13, 2026, 05:50 PM UTC

    We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.

14. monitoring Oct 14, 2026, 04:15 PM UTC

    We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.

15. monitoring Oct 15, 2026, 11:27 PM UTC

    We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.

Read the full incident report →

Started Sep 14, 2026, 04:10 PM UTC· resolved Sep 14, 2026, 05:16 PM UTC

1. identified Sep 14, 2026, 04:10 PM UTC

   Degradation Started: salesforceSpiffFeatureDisruption

2. monitoring Sep 14, 2026, 04:42 PM UTC

   We are investigating a potential cause of the issue.

3. monitoring Sep 14, 2026, 04:52 PM UTC

   We’ve confirmed that the solution implemented to mitigate the issue causing the feature degradation was successful. Engineers have observed that the service is now stable and have declared the incident resolved. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident.

Read the full incident report →

Started Sep 08, 2026, 08:19 PM UTC· resolved Sep 08, 2026, 11:30 PM UTC

1. identified Sep 08, 2026, 08:19 PM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Sep 08, 2026, 08:28 PM UTC

   We’re investigating an issue affecting Agentforce session scoring and tagging functionality for a subset of customers. Our teams are actively working to identify the trigger and restore service. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Sep 08, 2026, 08:58 PM UTC

   We’re continuing to investigate an issue affecting Agentforce session scoring and tagging for a subset of customers. Our teams are analyzing processing failures and reviewing affected customer environments to determine the trigger and identify a path to restore functionality. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Sep 08, 2026, 09:37 PM UTC

   Our teams have narrowed the investigation to failures occurring during session processing and are working to identify a path to restore functionality. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

5. monitoring Sep 08, 2026, 10:41 PM UTC

   We have identified a potential fix and are preparing to apply it to affected customer environments. We’ll monitor session tagging performance following the change to determine whether functionality recovers while our investigation into the underlying issue continues. We’ll provide another update as significant progress is made.

Read the full incident report →

Started Sep 08, 2026, 04:38 AM UTC· resolved Sep 08, 2026, 05:48 AM UTC

1. identified Sep 08, 2026, 04:38 AM UTC

   Degradation Started: featureServiceDisruption

2. monitoring Sep 08, 2026, 04:51 AM UTC

   We're aware of the issue affecting credit card transactions on Commerce Cloud, where customers are unable to complete purchases using credit cards at checkout. We're restarting the affected applications to restore transaction processing and working on a broader fix to resolve this for all impacted customers. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Sep 08, 2026, 05:15 AM 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.

4. monitoring Sep 08, 2026, 05:34 AM UTC

   We've applied manual fixes across all known affected environments to restore credit card transaction processing on Commerce Cloud checkouts. We're now testing an automated, fleet-wide fix to fully resolve this issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Sep 07, 2026, 07:04 PM UTC· resolved Sep 07, 2026, 08:53 PM UTC

1. identified Sep 07, 2026, 07:04 PM UTC

   Degradation Started: agentforcePerformanceDegradation

2. monitoring Sep 07, 2026, 07:04 PM UTC

   The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. Thank you for your patience as we work to resolve this issue.

Read the full incident report →

Started Sep 05, 2026, 11:33 AM UTC· resolved Sep 05, 2026, 12:25 PM UTC

1. identified Sep 05, 2026, 11:33 AM UTC

   Disruption Started: serviceDisruption

2. monitoring Sep 05, 2026, 11:46 AM UTC

   We isolated the issue and are working to find the best path to resolution. We will provide an update in 30 minutes or sooner if we have more information.

Read the full incident report →

Started Sep 05, 2026, 03:55 AM UTC· resolved Sep 05, 2026, 11:51 AM UTC

1. identified Sep 05, 2026, 03:55 AM UTC

   Degradation Started: performanceDegradation

2. monitoring Sep 05, 2026, 05:17 AM UTC

   We continue to explore multiple paths to quickly resolve the issue, which include analysing the error logs and additional diagnostic information to determine the potential trigger. We’ll provide an update upon a significant update, or sooner if additional information becomes available.

Read the full incident report →

Started Sep 04, 2026, 08:34 PM UTC· resolved Sep 04, 2026, 09:08 PM UTC

1. identified Sep 04, 2026, 08:34 PM UTC

   Degradation Started: SalesforceHBaseFeatureDegradation

Read the full incident report →

Started Sep 03, 2026, 10:30 PM UTC· resolved Sep 04, 2026, 06:29 AM UTC

1. identified Sep 03, 2026, 10:30 PM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Sep 03, 2026, 10:40 PM UTC

   Data Cloud customers using batch transforms may see completed jobs remain in an outdated status in the user interface. Automated flows, subsequent transforms, or other downstream processes that depend on the status update may not initiate, potentially delaying downstream data processing. Transform jobs continue to complete successfully, and no impact to the processed data has been identified. We have identified the trigger and initiated a rollback which is expected to remediate the issue. We will provide an update upon completion of the roll back, or sooner if more information becomes available.

3. monitoring Sep 04, 2026, 12:20 AM UTC

   As we complete the rollback on individual instances, we will post instance-level updates to accurately reflect each instance’s impact end time. Once an instance has been rolled back, we will remove it from this main post. Instances where rollback is still in progress will continue to receive updates in this post until remediation is complete.

4. monitoring Sep 04, 2026, 01:35 AM UTC

   Due to a functional issue identified following the rollback, we’ve now paused this activity. We are creating a roll-forward fix to address both the original issue and the new functional impact. Users may now experience that their manual and scheduled transform runs fail to start. This was first identified at 20:10 UTC, September 3. We will provide the next update once we can clarify how long the fix-forward will take to verify and deploy, or when new information becomes available. We apologize for any inconvenience this is causing to customers.

Read the full incident report →

Started Sep 03, 2026, 09:31 AM UTC· resolved Sep 03, 2026, 06:28 PM UTC

1. identified Sep 03, 2026, 09:31 AM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Sep 03, 2026, 09:45 AM UTC

   We’re investigating an issue affecting a subset of Industries Cloud customers using OmniStudio in sandbox environments. Affected customers can’t load or save changes in OmniScripts and FlexCards. Data Mappers and Integration Procedures aren't affected. We've identified a recent deployment as the likely trigger, and are evaluating whether a rollback is an appropriate action to restore service. The impact radius is broader than initially understood. We have updated this post 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 we have ‌significant update.

3. monitoring Sep 03, 2026, 10:15 AM UTC

   We’ve stopped the deployment to prevent further impact. While we assess the rollback, we’re checking other instances and verifying logs to understand what changes have gone in this release. Based on the findings, we’ll decide whether to proceed with a roll-back or a fix forward. We'll provide an update in 30 minutes or sooner if we have ‌ significant updates.

4. monitoring Sep 03, 2026, 10:33 AM UTC

   We’re reviewing logs and metrics to understand the trigger, while comparing recent release with previous releases to identify what changed. Our investigation also confirmed impact to a subset of production instances that received the release. We’ve updated this post with the affected instances, and impacted customers will receive incident communications going forward. We'll provide an update in 30 minutes or sooner if we have ‌ significant updates.

5. monitoring Sep 03, 2026, 11:08 AM UTC

   We’ve compared this release with previous releases but haven’t found any clear changes that explain the impact. To restore service, we’re testing a rollback on a test instance before deciding on the next step. In parallel, we’re also investigating a separate impacted sandbox instance to identify the trigger. We'll provide an update in 30 minutes or sooner if we have ‌ significant updates.

6. monitoring Sep 03, 2026, 11:55 AM UTC

   The rollback was successful on the test instance and restored it to the last known good version. However, we can’t roll back the full patch because it includes other critical fixes. We’re now looking at disabling a specific feature gate and rolling back only the affected change for affected customers. We'll provide an update in 60 minutes or sooner if we have ‌ significant updates.

7. monitoring Sep 03, 2026, 12:56 PM UTC

   Disabling the feature gate didn’t restore service. We’re now testing a targeted rollback while taking steps to reduce risk and avoid impacting other components. We'll provide an update in 60 minutes or sooner if we have ‌ significant updates.

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

   The targeted rollback is currently underway and we're analyzing whether this resolves the issue. The rollback is expected to take an hour to complete and further validation will be required following it’s completion. We'll provide an update in 90 minutes or sooner if we have‌ significant updates.

9. monitoring Sep 03, 2026, 01:35 PM UTC

   We've completed the targeted rollback on two testing instances, GBR40s and GBR138s. Customers on these instances are no longer affected, so we're removing them from this update. We'll post a separate Trust update for these instances so the impact times align correctly with each customer's incident history. We'll continue posting updates here for the remaining impacted instances. We'll provide an update in 90 minutes or sooner if we have significant updates.

10. monitoring Sep 03, 2026, 02:37 PM UTC

    We're continuing to perform the rollback across all impacted instances. We’re monitoring as the rollback progresses and we'll provide an update in 60 minutes or sooner if we have significant updates.

11. monitoring Sep 03, 2026, 03:44 PM UTC

    We’re continuing the rollback across impacted instances in a staggered manner to minimize the risk of additional disruption. As the rollback progresses, customers may begin to see OmniStudio functionality recover in their environments. We’ve also identified the change associated with the issue and are preparing an updated release before resuming deployments. We’ll provide another update as we make significant progress or have additional information to share.

12. monitoring Sep 03, 2026, 05:46 PM UTC

    We’ve completed the rollback across the impacted production and sandbox instances, restoring access to OmniScripts and FlexCards. However, some customers continue to experience errors in certain browser-based workflows when using the latest version of Chrome. We’re validating a corrected update designed to resolve the remaining issue without reintroducing the earlier impact. Once validation is complete, we’ll deploy the update to a test environment before proceeding with a broader rollout. We’ll provide another update as we make significant progress or have additional information to share.

Read the full incident report →

Started Sep 03, 2026, 08:11 AM UTC· resolved Sep 03, 2026, 01:01 PM UTC

1. identified Sep 03, 2026, 08:11 AM UTC

   Disruption Started: ccStorefrontSAndOrBusinessManagerUnavailable

2. monitoring Sep 03, 2026, 08:17 AM UTC

   We’re investigating an issue where a subset of B2C Commerce Cloud customers are experiencing Storefront and Business Manager unavailability following a recent release. We’re investigating and working to restore service. We'll provide an update 30 minutes or sooner as more information becomes available.

3. monitoring Sep 03, 2026, 08:45 AM UTC

   We’re continuing to investigate an issue with Storefront and Business Manager unavailability, following a recent release. We’re checking the potential connection to the release and working to identify the underlying cause and restore service. We'll provide the next update within 30 minutes or sooner as more information becomes available.

4. monitoring Sep 03, 2026, 08:50 AM 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.

5. monitoring Sep 03, 2026, 09:20 AM UTC

   We’ve identified that the issue is related to application restart failures following a recent deployment. The deployment removed a required network configuration entry, preventing the impacted services from connecting to the application servers. We're applying a targeted configuration fix to restore the missing network address entry and enable the impacted services to reconnect. We’ll provide the next update within 30 minutes or sooner as more information becomes available.

6. monitoring Sep 03, 2026, 09:40 AM UTC

   We’ve applied the targeted configuration fix, but service hasn't yet been restored for the affected customers. We’re investigating why the updated configuration isn't being reflected as expected and reviewing logs to identify the issue preventing the impacted services from reconnecting successfully. We’ll provide the next update within 30 minutes or sooner as more information becomes available.

7. monitoring Sep 03, 2026, 10:29 AM UTC

   We identified and stopped the service responsible for the overwrite and manually repaired the configuration, but this didn't restore service. We’re now evaluating a targeted rollback of the recent release as the next step to restore Storefront and Business Manager access. We’ll provide the next update within 30 minutes or sooner as more information becomes available.

8. monitoring Sep 03, 2026, 10:57 AM UTC

   We’re completing pre-checks before proceeding with the targeted rollback. We've identified an issue during this validation step, and are working to resolve it before moving forward. We’ll provide the next update within 30 minutes or sooner as more information becomes available.

9. monitoring Sep 03, 2026, 11:30 AM UTC

   We’ve resolved the issue identified during the rollback pre-check. However, Storefront and Business Manager remain unavailable, as the impacted application remains in an unhealthy state, which is preventing the targeted rollback from proceeding. We’re investigating the cause and continuing recovery efforts to restore access. We will provide our next update within 30 minutes, or sooner if more information becomes available.

10. monitoring Sep 03, 2026, 12:02 PM UTC

    We’ve identified a possible cause tied to a recent release that may be impacting the application’s responsiveness and preventing it from returning to a healthy state. We’re working to determine whether changes to the recent release can restore service. We’ll provide an update within 30 minutes, or sooner if additional information becomes available.

11. monitoring Sep 03, 2026, 12:31 PM UTC

    We’ve identified the cause as a misconfigured setting that's impacting application connectivity following the recent release. We successfully tested a configuration correction and confirmed that restarting the application restored connectivity. We’re now applying the same to ‌affected customer instances and validating the results. We’ll provide an update within 30 minutes, or sooner if additional information becomes available.

Read the full incident report →

Started Sep 02, 2026, 07:33 PM UTC· resolved Sep 03, 2026, 01:12 AM UTC

1. identified Sep 02, 2026, 07:33 PM UTC

   Degradation Started: muleSoftFeatureDegradation

2. monitoring Sep 02, 2026, 07:46 PM UTC

   We have identified an issue where customers viewing Agent Broker and Flex Gateway metrics are seeing zero values instead of expected data. Our teams have identified the technical trigger and are currently testing and validating a fix before deploying it to all affected areas. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Sep 02, 2026, 08:32 PM UTC

   We don’t have any updates to provide at this time, as we’re still testing and validating the potential fix. More information will be provided as soon as it becomes available.

Read the full incident report →

Started Sep 02, 2026, 05:47 PM UTC· resolved Sep 02, 2026, 06:30 PM UTC

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.

Read the full incident report →

Started Sep 02, 2026, 01:57 AM UTC· resolved Sep 02, 2026, 04:32 AM UTC

1. identified Sep 02, 2026, 01:57 AM UTC

   Degradation Started: featurePerfDegradation

Read the full incident report →

Started Sep 01, 2026, 09:45 PM UTC· resolved Sep 03, 2026, 01:12 AM UTC

1. identified Sep 01, 2026, 09:45 PM UTC

   Degradation Started: muleSoftPerformanceDegradation

2. monitoring Sep 01, 2026, 09:45 PM UTC

   We’ve identified some private spaces on which customers might not be able to deploy new applications, update existing applications, scale applications up or down, or restart applications. MuleSoft engineering is working on a mitigation, during which, impacted customers will observe their applications being graceful terminated and restarted. No action is needed from customers during this operation We'll provide another update as additional information becomes available.

3. monitoring Sep 02, 2026, 04:47 AM UTC

   We have made significant progress restoring most of the private spaces affected by this issue, with the majority now in a healthy state. We're continuing network configuration and certificate management fixes for the remaining spaces so customers can resume deploying, updating, restarting, and scaling applications. We'll provide an update as additional information becomes available.

4. monitoring Sep 02, 2026, 05:14 PM UTC

   We've restored all other previously impacted private spaces to normal operation. We continue to work on restoring the impact to private CloudHub 2.0 space in the US-EAST-1 region where customers may be unable to deploy, update, restart, or scale their applications. We'll provide an update as additional information becomes available.

Read the full incident report →