Tableau Cloud Outage History

Started Jul 09, 2026, 09:38 PM UTC· resolved Jul 10, 2026, 12:33 AM UTC

1. identified Jul 09, 2026, 09:38 PM UTC

   Disruption Started: ccCartsUnavailable

2. monitoring Jul 09, 2026, 09:57 PM UTC

   We are investigating an issue where customers are unable to place orders due to an error message at checkout. Investigations have identified a recent release as the primary cause, and our teams have started the process to roll this release back to a known good state. Engineering teams are noting that error rates are also returning to normal levels, and some affected storefronts may be seeing recovery. Teams are actively monitoring the rollback status as well as the B2C Commerce Cloud environment to confirm service restoration. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jul 09, 2026, 10:42 PM UTC

   We have completed the rollback of the recent release. We have observed that order flow has returned to normal levels across the majority of impacted storefronts. Our teams are actively monitoring the environment to confirm full service restoration for the remaining affected instances. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Jul 09, 2026, 11:36 PM UTC

   During our validations, we’ve identified one specific environment that continues to experience errors. We are actively investigating and working to fully restore services. We'll provide an update once additional information becomes available.

Read the full incident report →

Started Jul 09, 2026, 05:01 PM UTC· resolved Jul 11, 2026, 10:31 AM UTC

1. identified Jul 09, 2026, 05:01 PM UTC

   Degradation Started: agentforcePerformanceDegradation

2. monitoring Jul 09, 2026, 05:23 PM UTC

   On July 8 at 17:00 UTC, we became aware of an issue where customers may observe an Agentforce icon in Sandbox and Production environments even when the Agentforce Default Agent setting is disabled. Our investigation has confirmed this is the Small Business Suites Employee Assistance agent, which is enabled by design for eligible organizations with Foundation. There is currently no organization-level option to disable or hide this agent. We are developing a fix and will provide another update as more information becomes available. For additional information, please refer to our Help article: https://help.salesforce.com/s/issue?id=a02g7000005ohtJ

3. monitoring Jul 09, 2026, 07:23 PM UTC

   We have completed development of the fix and have begun deploying it across affected environments. For additional information, please refer to our Help article: https://help.salesforce.com/s/issue?id=a02g7000005ohtJ We will provide an update when the deployment is complete or if additional information becomes available.

4. monitoring Jul 09, 2026, 09:55 PM UTC

   We continue to deploy the fix across affected environments. As we implement these changes, users may experience brief periods of degraded performance. This behavior is expected and will resolve automatically once the process is complete. We are monitoring our systems closely to ensure minimal impact to your business. We apologize for this inconvenience. We will provide an update when the deployment is complete or if additional information becomes available.

5. monitoring Jul 10, 2026, 06:56 PM UTC

   The fix is continuing to be deployed across all affected environments. We will provide an update when the deployment is complete or if additional information becomes available.

Read the full incident report →

Started Jul 09, 2026, 08:22 AM UTC· resolved Jul 09, 2026, 10:11 AM UTC

1. identified Jul 09, 2026, 08:22 AM UTC

   Disruption Started: serviceDisruption

2. monitoring Jul 09, 2026, 09:02 AM UTC

   We're aware that some customers are unable to log into their sandbox environments due to unexpected multi-factor authentication (MFA) prompts, despite having MFA exemptions configured. We’ve identified that a recent change is enforcing MFA and passkey verification and we’re preparing a rollback to restore services. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jul 09, 2026, 09:33 AM UTC

   We've started rolling back the recent change and are monitoring the system to verify that expected login behavior is restored. We’ve also identified a few additional impacted instances, and those have now been included in the Trust post. Customers on those instances will receive notifications going forward. We're continuing to identify any other impacted instances and we'll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Jul 09, 2026, 01:16 AM UTC· resolved Jul 09, 2026, 01:50 AM UTC

1. identified Jul 09, 2026, 01:16 AM UTC

   Disruption Started: muleSoftServiceDisruption

2. monitoring Jul 09, 2026, 01:16 AM UTC

   Some customers are experiencing issues logging into the Anypoint Platform via single-sign-on. We're aware of the issue and are actively investigating. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jul 09, 2026, 01:34 AM UTC

   We’ve identified the issue and are proceeding to roll back a configuration change we believe is the cause. This should take no longer than approximately 30 minutes to complete. We will provide additional information as new details become available. We apologize for any inconvenience this issue is causing to customers.

Read the full incident report →

Started Jul 08, 2026, 11:54 AM UTC· resolved Jul 09, 2026, 02:41 PM UTC

1. identified Jul 08, 2026, 11:54 AM UTC

   Degradation Started: agentforcePerformanceDegradation

2. monitoring Jul 08, 2026, 12:23 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 Jul 08, 2026, 12:51 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.

4. monitoring Jul 08, 2026, 01:27 PM UTC

   We're aware of an issue impacting Agentforce availability for a subset of GovCloud customers. Affected customers may experience intermittent failures when interacting with Agents. When this occurs, chat sessions may fail and automatically transfer to a human agent, or may fail and require a new session. We're actively investigating the cause of intermittent failures and working to identify the source of the issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Jul 08, 2026, 01:57 PM UTC

   We continue to investigate an intermittent issue impacting Agentforce Agent availability for a subset of GovCloud customers. We'll provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Jul 08, 2026, 02:26 PM UTC

   We continue to investigate an intermittent issue impacting Agentforce Agent availability for a subset of GovCloud customers. We've identified that some requests from a specific agent type are being routed to a service that is not available, causing chat sessions to fail. When a failure occurs, chat sessions automatically transfer to a human agent, or customers must start a new session. We're exploring a potential emergency release with a fix. We'll provide an update in 60 minutes or sooner if additional information becomes available.

7. monitoring Jul 08, 2026, 04:05 PM UTC

   We have identified the trigger for this issue and are working to develop a fix which will be deployed once it has been fully validated. We'll provide another update as additional information becomes available.

8. monitoring Jul 08, 2026, 09:02 PM UTC

   The fix has been developed and the deployment has started. We'll provide another update upon completion of the deployment or when additional information becomes available.

9. monitoring Jul 09, 2026, 12:29 AM UTC

   The fix has been validated, and deployment of the fix continues across GovCloud environments. The deployment is being undertaken with a staggered approach, with monitoring and validation assessed on those where the deployment has completed. We currently don’t have an estimated time when the full rollout will be completed. We'll provide another update once we can clarify rollout timings, or when new information becomes available.

Read the full incident report →

Started Jul 07, 2026, 09:39 PM UTC· resolved Jul 08, 2026, 03:39 AM UTC

1. identified Jul 07, 2026, 09:39 PM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Jul 07, 2026, 09:40 PM UTC

   Currently customers cannot send transactional emails when using Marketing Cloud Next using the custom automation events or Activation trigger flows. All standard DMOs will not be impacted.

Read the full incident report →

Started Jul 07, 2026, 11:39 AM UTC· resolved Jul 08, 2026, 02:18 PM UTC

1. identified Jul 07, 2026, 11:39 AM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Jul 07, 2026, 11:39 AM UTC

   We're investigating an issue affecting the Dynamic Highlights Panel when customers are accessing it using the latest update to Chrome or Edge browsers. The panel isn't rendering the primary field values correctly for affected customers . This is impacting their ability to view key record information such as case numbers. We've engaged relevant teams to assist in the investigation. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

3. monitoring Jul 07, 2026, 11:52 AM UTC

   We’re‌ testing a work around which we believe will bring affected customers out of impact. If successful, we'll share the details of the work around with customers here. In parallel, we're also investigating a long term fix to resolve this issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

4. identified Jul 07, 2026, 12:02 PM UTC

   Degradation Started: performanceDegradation

5. monitoring Jul 07, 2026, 12:02 PM UTC

   Work is still underway to identify a viable workaround for customers. We’ve established that the level of impact differs from what was initially understood and is considered a performance degradation rather than a feature degradation as was previously communicated. We've also determined that the start time of the impact is different than initially understood. We've updated the incident posting to reflect the current impact and start time accurately. We apologize for any confusion this may have caused. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Jul 07, 2026, 12:25 PM UTC

   We're testing a configuration change that we believe will bring customers out of impact. Once validated that it's successful, the change will be rolled out to all affected instances. The testing is expected to take approximately 60 minutes to complete. In parallel, we're still testing a workaround for customers. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

7. monitoring Jul 07, 2026, 01:16 PM UTC

   We have determined that the proposed workaround which we were testing is not a viable option for customers. Our current focus is now solely on testing the configuration change, which is taking longer than expected. Additional teams have been engaged to assist with the testing. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

8. monitoring Jul 07, 2026, 02:12 PM UTC

   Upon further investigation we've been able to reproduce the issue and have identified workarounds which customers use. The details of the workarounds can be found here: https://help.salesforce.com/s/issue?id=a02g7000005pKxt We have determined that this issue is more complex than initially understood. We're working to engage browser vendors as part of this investigation. Internal testing on a configuration change are still underway. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

9. monitoring Jul 07, 2026, 03:13 PM UTC

   A possible path to resolve the issue is a configuration change. We're working to validate whether this is viable. We've engaged our release team and have them on standby to ensure that the configuration can be deployed if validated as a fix. In parallel, we have also engaged the browser vendor to assist with this investigation. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

10. monitoring Jul 07, 2026, 04:28 PM UTC

    We're continuing to work with our vendor and are validating a configuration change as a possible solution. Once validated, we'll deploy this change and monitor to ensure it fully resolves the issue. We’ll provide an update in 60 minutes or sooner if substantial changes come from our validations.

11. monitoring Jul 07, 2026, 05:43 PM UTC

    We are aiming to begin deploying the validated configuration change at approximately 19:00 UTC while continuing to work with our vendor to expedite their fix across all impacted browser versions. Please see this Known Issue article (https://help.salesforce.com/s/issue?id=a02g7000005pKxt) documenting available workarounds. We’ll provide an update as soon as substantial information is available.

12. monitoring Jul 07, 2026, 11:32 PM UTC

    We have identified a Cascading Style Sheets (CSS) rendering change introduced in a recent browser update as the cause of this issue. We’ve completed development and validation of a fix, and deployment is now underway fleet-wide. We have no clear indication of how long our fleet-wide deployment may take. We will provide the next update when we can clarify this. A period of monitoring will be undertaken once deployments are completed across all instances. Workarounds are documented and available via the Known Issue article: https://help.salesforce.com/s/issue?id=a02g7000005pKxt We’ll provide an update as soon as any new information becomes available.

13. monitoring Jul 08, 2026, 06:09 AM UTC

    We've made significant progress with the fleet-wide deployment of the fix. During the rollout, we identified and resolved a temporary issue that affected a small number of instances. The fix has now been deployed to the majority of instances, and the remaining instances are planned to be completed by 15:00 UTC, July 8. We will provide another update once the fleet-wide deployment is complete or if additional information becomes available.

14. monitoring Jul 08, 2026, 12:19 PM UTC

    The fleet-wide deployment of the fix is progressing as expected. Customers whose instances have received the fix will soon receive a separate, dedicated notification, including a summary of the incident and accurate start and end times.

Read the full incident report →

Started Jul 07, 2026, 08:16 AM UTC· resolved Jul 07, 2026, 02:33 PM UTC

1. identified Jul 07, 2026, 08:16 AM UTC

   Degradation Started: salesforceDataCloudFeatureDegradation

Read the full incident report →

Started Jul 06, 2026, 06:46 PM UTC· resolved Jul 07, 2026, 12:11 AM UTC

1. identified Jul 06, 2026, 06:46 PM UTC

   Degradation Started: intermittentLoginErrors

2. monitoring Jul 06, 2026, 07:33 PM UTC

   We have identified a recent deployment as the trigger for this issue and are actively rolling it back as part of our mitigation efforts to restore services. We'll provide an update in 60 minutes or sooner if additional information becomes available.

3. monitoring Jul 06, 2026, 08:39 PM UTC

   The rollback is in progress. We're resolving configuration blocks affecting a portion of the remaining instances and continue to monitor for service restoration. We'll provide an update in 90 minutes or sooner if additional information becomes available.

4. monitoring Jul 06, 2026, 10:13 PM UTC

   The rollback is continuing to progress. We'll provide another update upon completion of the rollback, or sooner if additional information becomes available.

Read the full incident report →

Started Jul 06, 2026, 03:53 PM UTC· resolved Jul 06, 2026, 04:30 PM UTC

1. identified Jul 06, 2026, 03:53 PM UTC

   Disruption Started: salesforceDataCloudFeatureDisruption

Read the full incident report →

Started Jul 06, 2026, 01:32 PM UTC· resolved Jul 06, 2026, 02:34 PM UTC

1. identified Jul 06, 2026, 01:32 PM UTC

   Disruption Started: herokuServiceDisruption

2. monitoring Jul 06, 2026, 01:54 PM UTC

   Engineers have identified an issue with an upstream service provider that impacts customers with apps in Cedar Private Spaces. Customers may experience failures with starting and scaling dynos of Cedar Private Spaces apps in Virginia. Engineers are working with the upstream provider to expedite a resolution.

3. monitoring Jul 06, 2026, 02:12 PM UTC

   Engineers have verified some service recovery and are monitoring for full impact resolution.

Read the full incident report →

Started Jul 06, 2026, 07:18 AM UTC· resolved Jul 06, 2026, 04:30 PM UTC

1. identified Jul 06, 2026, 07:18 AM UTC

   Degradation Started: featureServiceDisruption

2. monitoring Jul 06, 2026, 07:21 AM UTC

   Data 360 customers are unable to ingest data, as data stream jobs are failing or becoming stuck, which is stopping downstream business processes. We identified a recent deployment as the likely trigger. We're working to determine the appropriate remediation steps. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jul 06, 2026, 07:52 AM UTC

   A service version upgrade deployed over the weekend appears to have introduced a permissions issue preventing jobs from accessing required files. We're comparing the impacted environment with a healthy environment to confirm the trigger, and we're evaluating a rollback to restore service. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Jul 06, 2026, 09:17 AM UTC

   Our investigation has confirmed that the impact extends across multiple instances. The issue is broader than initially understood, and we’ve updated the Trust post to reflect all impacted instances. Data 360 customers on impacted instances are still unable to run data stream jobs, disrupting data ingestion and downstream processes.We’re continuing to validate a confirmed permissions issue preventing the Data Connector Service from starting on impacted instances. A full rollback isn’t possible, so we’re evaluating a targeted redeployment to determine if this can restore the services. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Jul 06, 2026, 09:50 AM UTC

   A configuration gap introduced during a recent deployment has been identified as the trigger, affecting services on the impacted instances. We’re now implementing a targeted fix, starting with a controlled validation on a lower-impact instance before rolling it out to remaining environments. We’re also verifying that no automated processes will reverse the change. Monitoring is active as we work toward full service restoration. We'll provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Jul 06, 2026, 10:31 AM UTC

   We’ve deployed a manual fix to the first impacted environment and are validating service restoration through live traffic. Once validation is confirmed, we will roll out the fix across all remaining instances. We’re also working with our cloud infrastructure provider to determine how the deployment introduced the permission gap and to ensure automated processes do not reintroduce the issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

7. monitoring Jul 06, 2026, 11:26 AM UTC

   The missing permissions policy that was manually added to the impacted instances as a manual fix is showing no errors. We're applying the same fix to the remaining impacted instances in parallel and verifying that no automated process will overwrite the manual change during rollout. Data 360 customers on impacted instances are still unable to run data stream jobs, disrupting data ingestion and downstream processes. We'll provide an update in 30 minutes or sooner if additional information becomes available.

8. monitoring Jul 06, 2026, 11:59 AM UTC

   The manual fix has successfully resolved the errors and monitoring confirms the previously observed errors haven't recurred. We're analyzing logs to validate the fix, as both successful and failed jobs are present on the impacted instances. We're continuing to work on remediating the issue to restore services. We apologize for the inconvenience this is causing. We'll provide an update in 30 minutes or sooner if additional information becomes available.

9. monitoring Jul 06, 2026, 12:27 PM UTC

   Validation of the fix is in progress and we're continuing to work on remediating the issue to restore services. Data 360 customers may still be unable to run data stream jobs, disrupting data ingestion and downstream processes. We'll provide an update in 30 minutes or sooner if additional information becomes available.

10. monitoring Jul 06, 2026, 02:19 PM UTC

    The manual fix resolved the Data 360 data stream failures on selected instances where the fix was applied. These changes are temporary. We're going to roll back the change that triggered the issue to the last-known stable version. This is expected to take several hours to complete. We'll provide an update in 60 minutes or sooner if additional information becomes available.

11. monitoring Jul 06, 2026, 02:41 PM UTC

    Following the application of a manual fix to selected instances, Data 360 data stream failures have been resolved. Customers who were experiencing impact have been confirmed that normal service has been restored. The rollback to the last-known stable version is in progress and the rollback is expected to fully resolve the issue. We'll provide an update in 60 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Jul 03, 2026, 12:23 AM UTC· resolved Jul 03, 2026, 02:10 AM UTC

1. identified Jul 03, 2026, 12:23 AM UTC

   Degradation Started: performanceDegradation

2. monitoring Jul 03, 2026, 12:54 AM UTC

   We are currently investigating a performance degradation whereby customers may experience intermittent connection issues. Customers may experience connection request delays or connection failures. We’ll provide another update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jul 03, 2026, 01:14 AM UTC

   We are continuing to investigate the issue. We believe that we have identified the apps contributing to the issue and are assessing a restart to mitigate the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Jul 03, 2026, 01:33 AM UTC

   The rolling restart of the apps we believe to be causing the issue is in progress. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Jul 03, 2026, 01:53 AM UTC

   The rolling restart process continues and we are beginning to validate as services are restored. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Jul 02, 2026, 08:47 AM UTC· resolved Jul 03, 2026, 03:03 PM UTC

1. identified Jul 02, 2026, 08:47 AM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Jul 02, 2026, 08:47 AM UTC

   We're aware of an issue affecting a subset of Data 360 customers where search index rebuilds triggered between 22:20 UTC on June 30 and 16:40 UTC on July 1 are stuck in the ‘submitted’ status. We've implemented a fix to ensure that rebuilds triggered outside of this time will have been processed correctly. We’re in the process of developing a fix to process the blocked rebuilds, and this is expected to take some time to complete. We'll provide an update in 2 hours or sooner if additional information becomes available.

3. monitoring Jul 02, 2026, 09:30 AM UTC

   We are continuing to work on developing the necessary code fix to allow the stuck search index rebuilds to complete processing. In the meantime, as part of the investigation, we have identified a number of additional instances which are impacted by this issue. We have added them to this messaging and they'll receive all future updates regarding this issue. We'll provide an update in 2 hours or sooner if additional information becomes available.

4. monitoring Jul 02, 2026, 10:36 AM UTC

   The code fix has been developed and is being tested. Once it is successfully tested, it will be deployed to all impacted instances in a staggered approach. The testing will take several hours to complete. An additional number of instances have been identified as impacted and they’ll now receive further updates as this incident progresses. We'll provide an update in 5 hours or sooner if additional information becomes available.

5. monitoring Jul 02, 2026, 04:27 PM UTC

   Code fix testing remains in progress, and once successful, the fix will be deployed to all impacted instances in a staggered approach. We'll provide additional updates as significant developments occur or sooner if new information becomes available.

6. monitoring Jul 03, 2026, 01:06 PM UTC

   The code fix was successfully tested and has is now being deployed to all impacted instances in a staggered approach. As a result customers will come out of impact in batches as the deployment completes. A number of instances have already been brought out of impact and they will be removed from this messaging and receive their own separate Trust posting to accurately reflect their impact duration. We'll provide additional updates as significant developments occur or sooner if new information becomes available.

Read the full incident report →

Started Jul 01, 2026, 03:44 PM UTC· resolved Jul 01, 2026, 07:22 PM UTC

1. identified Jul 01, 2026, 03:44 PM UTC

   Degradation Started: slowDataProcessing

2. monitoring Jul 01, 2026, 03:57 PM UTC

   We're aware of an issue impacting Data 360 Batch Data Transforms. As a result, customers may be unable to run or complete Batch Data Transform jobs. We're actively investigating and working to restore full functionality. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jul 01, 2026, 04:25 PM UTC

   We're aware of an issue affecting Data 360 customers using Bring Your Own Lake (BYOL) with Redshift connections. Customers may experience delays in data availability rather than complete job failures, as the Batch Data Transform service includes a retry mechanism. We've identified a network configuration as the likely trigger and have applied a fix that's currently being validated across affected environments. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Jul 01, 2026, 04:55 PM UTC

   We continue to investigate an issue impacting Data 360 customers who use Bring Your Own Lake (BYOL) with Redshift connections. Validation of the network configuration fix is still in progress across all impacted environments. We'll provide an update in 60 minutes or sooner if additional information becomes available.

5. monitoring Jul 01, 2026, 05:57 PM UTC

   We continue to investigate an issue impacting Data 360 customers who use Bring Your Own Lake (BYOL) with Redshift connections. Additional teams are now engaged to assist with end-to-end validation before the fix is rolled out to all remaining impacted environments. We'll provide an update in 60 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Jun 30, 2026, 05:49 AM UTC· resolved Jun 30, 2026, 10:22 PM UTC

1. identified Jun 30, 2026, 05:49 AM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Jun 30, 2026, 06:00 AM UTC

   We're aware of an issue impacting Event Log File delivery for customers with Salesforce Shield licensing. As a result, customers may experience delays in receiving Event Log Files. We are actively investigating and working toward a resolution. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jun 30, 2026, 06:26 AM UTC

   We've identified a recent configuration change as the likely trigger for Event Log File delivery. We're exploring multiple paths to ‌resolution. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Jun 30, 2026, 07:15 AM UTC

   We have completed an initial rollback of the recent configuration changes in a test environment and are currently validating whether this resolves the issue Post-validation we'll apply the configuration changes to the remaining impacted instances. We'll provide another update in 30 minutes or sooner if additional information becomes available.

5. monitoring Jun 30, 2026, 07:36 AM UTC

   Further investigation revealed that the recent configuration changes had reduced processing capacity, which has triggered ‌the delays of the Event Log Files. We've hit an issue with rolling back the configuration change. We're evaluating options to create an emergency fix which will add the necessary capacity to handle requests. Additional teams are being engaged to assist with developing this fix. There's currently no work-around available to customers. We'll provide another update in 60 minutes or sooner if additional information becomes available.

6. monitoring Jun 30, 2026, 08:14 AM UTC

   We’ve completed a capacity increase and are now validating whether it has had a positive effect on the impacted instances.In parallel, we’re forcing a restart to ensure the infrastructure correctly routes to the new capacity. We'll provide another update in 60 minutes or sooner if additional information becomes available.

7. monitoring Jun 30, 2026, 08:49 AM UTC

   We haven’t seen improvement in the service following the increase in capacity. The infrastructure appears to be reading from a cached configuration of previous lower capacity limits. We are performing a change to ensure the infrastructure recognizes the correct increased capacity limits. We'll provide another update in 60 minutes or sooner if additional information becomes available.

8. monitoring Jun 30, 2026, 09:32 AM UTC

   We're continuing to perform the necessary configuration changes to the infrastructure to allow it to recognize the increased capacity limits. We’ll monitor the changes to validate whether they're successful. We'll provide another update in 60 minutes or sooner if additional information becomes available.

9. monitoring Jun 30, 2026, 10:11 AM UTC

   Work is still underway to complete configuration changes which we believe should bring customers out of impact. We'll provide another update in 60 minutes or sooner if additional information becomes available.

10. monitoring Jun 30, 2026, 11:13 AM UTC

    We have completed the configuration steps and have observed that the backlog in processing Event Log Files is reducing. We are continuing to monitor it’s progress. We'll provide another update in 60 minutes or sooner if additional information becomes available.

11. monitoring Jun 30, 2026, 12:09 PM UTC

    During recovery, we identified that additional remediation was required for a small portion of Event Log File processing. We restarted the affected processing pipelines and are continuing to monitor processing volumes to confirm full recovery. We are actively working to ensure processing returns to normal and will provide an update within 60 minutes, or sooner if additional information becomes available.

12. monitoring Jun 30, 2026, 01:22 PM UTC

    We are actively monitoring the recovery to ensure the processing backlogs continue to clear as expected. Due to a large backlog, processing of pending Event Log Files will take several hours. Files are being processed in order, and the backlog is gradually reducing. We'll provide an update when there are significant changes, or sooner if additional information becomes available.

13. monitoring Jun 30, 2026, 03:03 PM UTC

    We continue to closely monitor the recovery process to ensure that progress in resolving Event Log File delivery delays remains on track for affected customers. The backlog is reducing, with completion expected to take several hours. We'll provide an update when there are significant changes, or sooner if additional information becomes available.

Read the full incident report →

Started Jun 26, 2026, 01:56 PM UTC· resolved Jun 26, 2026, 06:10 PM UTC

1. identified Jun 26, 2026, 01:56 PM UTC

   Degradation Started: tableauFeatureDegradation

2. monitoring Jun 26, 2026, 02:08 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.

3. monitoring Jun 26, 2026, 02:09 PM UTC

   We're aware of an issue affecting the Tableau Cloud sign-in service were subset of customers in European regions are unable to sign in to their Tableau Cloud PODs. We're investigating the trigger of this issue and will provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Jun 26, 2026, 02:35 PM UTC

   We believe the trigger has been identified and our teams are working to reroute traffic to healthy infrastructure to restore service. We'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Jun 26, 2026, 03:04 PM UTC

   We continue to make progress in restoring service and have rerouted traffic away from the impacted infrastructure to healthy PODs. The majority of the affected customers have access restored, and we’re continuing to apply the same steps for theremaining customers to achieve full restoration. We'll provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Jun 26, 2026, 03:21 PM UTC

   We continue to make progress in restoring service and will apply the same steps for the remaining impacted customers to achieve full restoration. We'll provide the next update upon a significant development or once full service restoration is confirmed.

7. monitoring Jun 26, 2026, 05:42 PM UTC

   Investigations have shown that the impact also included some customers in the India region who were unable to sign in. We changed Domain Name System (DNS) records to route traffic to healthy instances, and access has been restored. We're actively monitoring performance and completing health checks to confirm full stability. We'll provide the next update upon a significant development or once full service restoration has been confirmed.

Read the full incident report →

Started Jun 26, 2026, 01:11 PM UTC· resolved Jun 27, 2026, 12:40 AM UTC

1. identified Jun 26, 2026, 01:11 PM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Jun 26, 2026, 01:29 PM UTC

   We're investigating an issue where Omnichannel agents are experiencing unexpected disconnections and reconnections, disrupting their ability to manage and receive customer interactions in real-time. We're actively investigating the issue and are still determining the scope of impact. We'll provide an update in 30 minutes or sooner, if additional information becomes available.

3. monitoring Jun 26, 2026, 01:37 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 Jun 26, 2026, 01:46 PM UTC

   Investigations indicate a recent change as the potential trigger for this issue. We're rolling back the change to see if it resolves the issue. Investigations have highlighted that the impact radius is broader than initially understood. We're updating 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.

5. monitoring Jun 26, 2026, 01:49 PM UTC

   We have observed that the impact has increased and is now disrupted. We have amended the posting to reflect this and highlighted the approximate timings of this transition.

6. monitoring Jun 26, 2026, 01:59 PM UTC

   We're continuing to work on rolling back the change that was identified as a potential trigger. We're also working to increase capacity. Omnichannel agents continue to experience unexpected disconnections and reconnections, disrupting their ability to manage and receive customer interactions in real-time. We'll provide an update in 30 minutes or sooner, if additional information becomes available.

7. monitoring Jun 26, 2026, 02:17 PM UTC

   The scope of this issue has now increased as this has been tied to a broader issue. Customers using Salesforce Edge could‌ experience an impact. We're exploring multiple paths to resolution. The rollback of the change is currently in progress and a memory increase is underway. We've discovered a feature that's causing resource consumption and are disabling the feature to see if this helps. We'll provide an update in 30 minutes or sooner, if additional information becomes available.

8. monitoring Jun 26, 2026, 03:01 PM UTC

   This issue isn't limited to Omnichannel. Any Salesforce Core, MuleSoft, and Tableau customer relying on Salesforce Edge may be affected and may experience connection timeouts, and pages not loading. Our three paths to resolution are underway: the rollback of the change, memory increase, and disabling the feature causing resource consumption. Investigations have highlighted that the impact radius is broader than initially understood. We're updating 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.

9. monitoring Jun 26, 2026, 03:39 PM UTC

   Our three paths to resolution continue in parallel. The memory increase is progressing across additional instances, with the initial instance now stable and serving as the model for the broader rollout. The release rollback has completed validation and we're preparing to apply it in production. We'll provide an update in 30 minutes or sooner, if additional information becomes available.

10. monitoring Jun 26, 2026, 04:10 PM UTC

    The memory increase is our primary path to restoring the service and is now being deployed across additional instances. The release rollback will also be‌ applied to production following the memory increase. We'll provide an update in 30 minutes or sooner, if additional information becomes available.

11. monitoring Jun 26, 2026, 04:38 PM UTC

    The memory increase is progressing across additional instances globally. Deployments are continuing across all remaining instances, with completion expected within the next hour. We'll provide another update upon completion of the deployment or sooner, if additional information becomes available.

12. monitoring Jun 26, 2026, 06:05 PM UTC

    The memory increase is taking longer than originally anticipated but is continuing to progress. Once the memory increase has been completed, the rollback will be initiated. We'll provide an update in 60 minutes or sooner, if additional information becomes available.

13. monitoring Jun 26, 2026, 07:03 PM UTC

    We've completed the memory increase across all production environments and are preparing for the rollback. This phase may take several hours to complete. We'll provide updates as significant developments become available.

14. monitoring Jun 26, 2026, 08:52 PM UTC

    We’ve increased memory capacity across our production environments, significantly improving performance for the majority of affected customers. We’re now actively working on the release rollback to restore services. We'll provide the next updates as significant developments become available.

15. monitoring Jun 26, 2026, 10:42 PM UTC

    We’ve completed the release rollback across our production environments and have initiated background operations to clean up residual configurations. In parallel, we're executing ‌a change to safely re-enable Edge across the affected environments where it was disabled. Customers should continue to see improved performance as this process continues to progress. We'll provide the next updates as significant developments become available.

16. monitoring Jun 26, 2026, 11:56 PM UTC

    We’ve successfully re-enabled Edge across our production environments. We’re now executing the final set of background operations to clean up residual configurations We'll provide the next updates as significant developments become available.

Read the full incident report →

Started Jun 26, 2026, 09:33 AM UTC· resolved Jun 26, 2026, 10:10 AM UTC

1. identified Jun 26, 2026, 09:33 AM UTC

   Degradation Started: intermittentPageLoadErrors

Read the full incident report →

Started Jun 25, 2026, 08:18 AM UTC· resolved Jun 25, 2026, 12:09 PM UTC

1. identified Jun 25, 2026, 08:18 AM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Jun 25, 2026, 08:29 AM UTC

   We’re investigating an issue impacting inbound SMS messaging for a subset of Marketing Cloud Growth & Advanced Editions on Core where customers are unable to receive inbound SMS messages or delivery receipts when end users reply to SMS. Outbound SMS messaging is not impacted. We’ve identified the trigger as a recent migration during which certain sender codes were not migrated correctly. The issue is limited to customers using the impacted sender codes. We’re applying the required configuration changes and validating the changes as they are deployed. We’ll provide another update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jun 25, 2026, 08:55 AM UTC

   We are implementing a code change to restore service. Before deployment, we’re validating the code changes to ensure it fully resolves the issue without creating additional impact. This validation is taking additional time. We’ll provide another update in 60 minutes or sooner if additional information becomes available.

4. monitoring Jun 25, 2026, 09:55 AM UTC

   Investigation has identified two contributing issues impacting inbound event processing. The first issue was caused by a synchronization gap that prevented a required configuration field from being propagated for a subset of sender codes. A remediation has been applied, and validation across multiple regions confirms inbound event processing has resumed for remediated codes. During the investigation, we identified a second issue impacting a subset of codes that were not fully synchronized between dependent systems. We've implemented a targeted remediation to backfill the missing data and reprocess impacted codes. The remediation is being validated on a limited set of records before being rolled out in phases to all impacted codes to ensure newly provisioned codes are not impacted by this synchronization issue. The implementations will take 2 to 3 hours and will provide an update as additional information becomes available.

5. monitoring Jun 25, 2026, 11:35 AM UTC

   We’ve successfully tested the remediation on a subset of codes to backfill the missing data and reprocess the codes. We're now in the process of performing the remediation to all impacted codes. We'll provide the next update in 60 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Jun 23, 2026, 02:38 AM UTC· resolved Jun 23, 2026, 04:29 AM UTC

1. identified Jun 23, 2026, 02:38 AM UTC

   Degradation Started: muleSoftFeatureDegradation

2. monitoring Jun 23, 2026, 02:40 AM UTC

   We're aware of an issue impacting Runtime Manager for MuleSoft Anypoint Platform CloudHub 2.0 customers. Customers attempting to change their Mule runtime version via the Runtime Manager UI are finding the change appears to succeed, but actually does not, and it reverts to the previous version. Some customers may also encounter an error when attempting to update. We are working on a workaround and will publish this as soon as it is available. We're working to restore full functionality as quickly as possible and will provide an update in 60 minutes, or sooner if additional information becomes available.

3. monitoring Jun 23, 2026, 03:18 AM UTC

   We're continuing to investigate the issue impacting Runtime Manager for MuleSoft Anypoint Platform CloudHub 2.0 customers. We've identified a configuration change which we believe is the likely trigger of the issue and are now working to roll back this change. The rollback is underway and is estimated to take approximately two hours to complete. We will then undertake a period of monitoring to validate performance. We'll provide an update in 60 minutes or sooner if additional information becomes available.

4. monitoring Jun 23, 2026, 03:39 AM UTC

   We're continuing to address an issue impacting Anypoint Runtime Manager for CloudHub 2.0 customers. We've identified the underlying trigger — a recent change to the Runtime Manager UI — and a rollback of this change is currently underway. The rollback is estimated to take approximately two hours to complete. A workaround is available. Please visit our Known Issue article here, http://sfdc.co/WEHv3 for guidance on steps you can take while we complete the rollback. We'll provide an update in 60 minutes, or sooner if additional information becomes available.

Read the full incident report →

Started Jun 22, 2026, 02:41 PM UTC· resolved Jun 22, 2026, 03:42 PM UTC

1. identified Jun 22, 2026, 02:41 PM UTC

   Degradation Started: tableauPerformanceDegradation

2. monitoring Jun 22, 2026, 03:17 PM UTC

   We’ve implemented a solution to resolve the issue causing the performance degradation. Initial results indicate that the feature is working as expected. Engineers continue to monitor the situation closely. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Read the full incident report →

Started Jun 19, 2026, 09:07 PM UTC· resolved Jun 20, 2026, 02:00 AM UTC

1. identified Jun 19, 2026, 09:07 PM UTC

   Disruption Started: salesforceDataCloudFeatureDisruption

2. monitoring Jun 19, 2026, 09:50 PM UTC

   We're aware of an issue impacting the Tableau Next Analytics Agent. Users leveraging the Tableau Next Data Source (TDS) feature may be unable to access the Analytics Agent through supported interfaces. We've implemented a mitigation that is expected to stabilize the affected service and are continuing to investigate remaining connectivity issues. We'll provide another update in 60 minutes, or sooner if additional information becomes available.

3. monitoring Jun 19, 2026, 10:42 PM UTC

   We've successfully implemented a mitigation to address the underlying service instability and have stabilized the affected infrastructure. However, users leveraging Tableau Next Data Source (TDS) workflows may continue to experience failures when accessing the Tableau Next Analytics Agent through supported interfaces. Our investigation has narrowed the issue to a connectivity failure affecting a dependent service required for TDS-related requests. We're actively working with the owning engineering teams to restore connectivity and fully resolve the impact We'll provide another update in 90 minutes or sooner if additional information becomes available.

4. monitoring Jun 19, 2026, 11:50 PM UTC

   We've successfully implemented a mitigation to address the underlying service instability and have stabilized the affected infrastructure. However, users leveraging Tableau Next Data Source (TDS) workflows may continue to experience failures when accessing the Tableau Next Analytics Agent through supported interfaces. Our investigation has narrowed the issue to a connectivity failure affecting a dependent service required for TDS-related requests. We're actively working with the owning engineering teams to restore connectivity and fully resolve the impact We'll provide the next update when additional information becomes available.

Read the full incident report →

Started Jun 19, 2026, 06:46 PM UTC· resolved Jun 19, 2026, 07:17 PM UTC

1. identified Jun 19, 2026, 06:46 PM UTC

   Disruption Started: herokuRetroactiveServiceDisruption

Read the full incident report →

Started Jun 19, 2026, 11:57 AM UTC· resolved Jun 19, 2026, 03:37 PM UTC

1. identified Jun 19, 2026, 11:57 AM UTC

   Degradation Started: salesforceDataCloudFeatureDegradation

2. monitoring Jun 19, 2026, 11:58 AM UTC

   We're aware of an issue impacting Calculated Insights in Data 360. Customers' scheduled Calculated Insights queries are failing to run successfully. The issue began following a deployment at 22:00 UTC on June 18, 2026. We've initiated a rollback of the deployment on a test instance to validate a path forward. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jun 19, 2026, 12:24 PM UTC

   We're continuing to validate a rollback of the deployment. We'll provide an update on validation progress in 30 minutes or sooner if additional information becomes available.

4. monitoring Jun 19, 2026, 12:50 PM UTC

   The validation rollback is encountering issues that are preventing it from completing as expected. We're actively working to resolve this and we'll provide an update in 30 minutes or sooner if additional information becomes available.

5. monitoring Jun 19, 2026, 01:19 PM UTC

   We fixed the problem that stopped the validation rollback from finishing. We're re-starting validation now and we'll provide an update in 30 minutes or sooner if additional information becomes available.

6. monitoring Jun 19, 2026, 01:48 PM UTC

   We're continuing to validate the rollback. We'll provide an update in 30 minutes or sooner.

7. monitoring Jun 19, 2026, 02:15 PM UTC

   Initial validations are positive. We'll provide an update in 30 minutes or sooner.

8. monitoring Jun 19, 2026, 02:42 PM UTC

   We've validated that the deployment rollback resolves the issue and begun a wider rollback at 14:40 UTC. This is expected to complete within 30-60 minutes. The ability to run Calculated Insights queries successfully will be restored to instances in stages as the rollback progresses. Customers can periodically attempt a manual run of their previously failed scheduled queries or opt to wait for the next scheduled time. We'll provide an update on rollback progress in 30 minutes or sooner if additional information becomes available.

9. monitoring Jun 19, 2026, 03:08 PM UTC

   The rollback is complete and we're verifying service restoration. We'll provide an update in 30 minutes or sooner.

Read the full incident report →