Cross-Cloud Service Disruption

Investigations have highlighted that the impact radius is broader than initially understood. Marketing Cloud Intelligence, Tableau Cloud, Revenue Cloud, Core, and Hyperforce are also impacted by the issue. We have multiple teams involved and exploring multiple paths to resolution.
We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Further investigation has uncovered that the issue might be related to a third-party vendor. We are awaiting confirmation. Additionally, we continue to explore all other possible paths to resolve the issue.
We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Further investigations have highlighted that the impact radius is broader than initially understood. The issue also impacts Experience Cloud, Marketing Cloud Account Engagement, MuleSoft, the Salesforce+ site, the Salesforce Chat experience, and Service Cloud. We have also determined that Gov Cloud is not impacted by this issue.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Investigations have determined that the customers relying on multi-factor authentication are affected, while standard users who use a username and password may see intermittent login issues. Additionally, Marketing Cloud Engagement, Marketing Cloud Intelligence, MuleSoft, the Salesforce+ site and Tableau Cloud customers will experience intermittent login failures. The Salesforce chat connection is dropping intermittently mid-conversations, impacting customer experience.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Customers who use services that utilize Core (Sales, Service, Revenue, etc) and use salesforce.com to log in can use Salesforce Authenticator TOTP to log in. Please follow the Knowledge Article for Salesforce Authenticator TOTP: https://help.salesforce.com/s/articleView?id=xcloud.salesforce_authenticator_notifications_unavailable.htm&type=5
Maintenance activity on a third-party vendor has been ruled out as a potential trigger. We are working with a separate third-party cloud services provider to investigate whether there was any activity or planned change that could have triggered the issue. Additionally, we are exploring whether any recent changes in our Heroku environment would have contributed to the issue.
We’ll provide an update in 30 minutes or sooner if additional information becomes available.

The third-party provider disabled a single server, which did not yield a positive outcome. We are continuing our investigations with the provider.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

The impact has been mitigated for Marketing Cloud Intelligence customers following a short-term configuration change.
A subset of Commerce Cloud customers have reported improvements without our intervention, but this is due to the intermittent nature of the issue; a significant number of Commerce Cloud customers are still seeing errors while logging in and processing orders.
We have identified some network configuration issues on one of the servers within our Heroku environment, which could trigger this issue. We are exploring this further and remain focused on providing a long-term solution for all affected customers.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

The Heroku service is experiencing an intermittent service disruption, which is currently being investigated. Dynos are having issues with external connectivity, and Dashboard and Application Programming Interface (API) are failing intermittently. This is also affecting Salesforce+ event registrations and Trailblazer profile/settings pages.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Customers across multiple services continue to experience issues using a variety of services.
Due to the nature of the impact on Heroku, certain services can experience downstream functionality impact.
Heroku - The Heroku service is experiencing an intermittent service disruptionDynos are having issues with external connectivity, and Dashboard and Application Programming Interface (API) are failing intermittently.
Core Services - Customers who use services that utilize Core (Sales, Service, Revenue, etc) and use salesforce.com to log in can use Salesforce Authenticator TOTP to log in. Please follow the Knowledge Article for Salesforce Authenticator TOTP: https://help.salesforce.com/s/articleView?id=xcloud.salesforce_authenticator_notifications_unavailable.htm&type=5
Commerce Cloud - Customers who use OCI (Omnichannel Inventory) or SOM (Salesforce Order Management) may experience issues with order placement and processing.
Marketing Cloud Engagement - Customers are unable to log in to their service or add/edit campaigns.
Marketing Cloud Intelligence - Following a short-term configuration change, the customer impact was mitigated at 07:21 UTC.
MuleSoft - Customers can’t log in to the Anypoint platform
Salesforce+ site - Users are unable to register for events or view broadcasted and on-demand content.
Service Cloud - Customers are experiencing failures using the third-party messaging (Enhanced and Standard WhatsApp, SMS).
Tableau Cloud - Customers will experience intermittent login failures. Additionally,
Revenue Cloud - Customers may experience an impact on features such as quote calculation, quote preview, and document preview.
The Ask Agentforce bot on the Salesforce help site is intermittently not responding.
The Trailhead and Trailhead Academy sites are also experiencing issues with profile loading and settings pages. AppExchange is impacting site and search functionality.


We’ll provide an update in 30 minutes or sooner if additional information becomes available.

We have restarted a subset of our Heroku-based Application Programming Interface (API) and verification-related instances. This has shown positive results for the impacted services. We are working to restart the rest of the Heroku instances to fully restore the services. We are continuing to validate and closely monitor the services. Some customers are seeing improvements while accessing their services; however, the current impact still remains. Further investigations highlighted that an automated change on the Heroku environment was the potential trigger of this issue. The network configuration change, which was performed earlier, did not show any improvements.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

We’ve restarted Heroku’s internal platform apps and are actively monitoring to confirm whether the issue is resolved. However, errors are resurfacing.

We suspect a recent configuration change as the likely trigger and are working to revert it. In parallel, we’re developing an expedited rollout strategy and safeguards to prevent the recurrence of this config change.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

We’ve restarted Heroku’s internal platform apps and are actively monitoring to confirm whether the issue is resolved. However, errors are resurfacing.

We suspect a recent configuration change as the likely trigger and are working to revert it. In parallel, we’re developing an expedited rollout strategy and safeguards to prevent the recurrence of this config change.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

Investigations are still ongoing. A permanent fix is in progress, and it will require disabling the configuration change that reintroduces impact.

Please note that the Heroku Support portal, located here https://help.heroku.com/, is now accessible. The ability for Heroku customers to log a ticket has been restored. If you need to contact the Heroku team, please log a ticket via https://help.heroku.com/. Should you be unable to log a ticket, kindly email us at outage-support@heroku.com, and our Support team will provide updates. Thank you for your patience.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

We continue to work on the permanent fix and explore alternate paths to resolution. Once the fix is developed, an estimated time to resolution will be shared.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

We’ve identified the likely trigger of the issue and are making strong progress toward a resolution. A recent automated update disrupted network connectivity on affected instances. We're working on a fix to prevent this from recurring and will provide an ETA for resolution when it's available.
We’ll provide an update in 30 minutes or sooner if additional information becomes available.

We are actively developing the fix and working to determine a resolution timeline. Once the fix is complete, it will undergo testing in our pre-production environments to validate its effectiveness.
We will provide another update within 30 minutes or sooner if new information becomes available.

We are observing positive results in our initial testing on pre-production environments. We’re continuing to test the fix before applying it to production environments and will provide a resolution timeline once determined.

We will provide another update within 30 minutes or sooner if new information becomes available.

We continue to see incremental improvements, though we don’t have additional information to share at this time. Our efforts remain focused on internal testing and validation. We will share a resolution timeline as soon as it becomes available. We apologize for the continued inconvenience and appreciate your patience.

We will provide another update within 30 minutes or sooner if new information becomes available.

We don’t have additional information to share at this time. Our efforts remain focused on internal testing and validation as we continue to see incremental improvements. We will provide a resolution timeline as soon as possible, and we apologize for the continued trouble.

We will provide another update within 30 minutes or sooner if new information becomes available.

We have resolved issues with dashboard.heroku.com, and the site is now accessible to customers. As a workaround, while we continue implementing fixes, customers still impacted can run the following commands via their Heroku Command Line Interface:

heroku ps --app ”$APP” to get a listing of all dyno names
heroku ps:stop --dyno-name ”$DYNO” --app ”$APP”

Important to note that dynos should be restarted one at a time to avoid a service disruption.

Our efforts remain focused on internal testing and validation, and we continue to see incremental improvements in our other products. We will provide a resolution timeline as soon as possible, and we apologize for the continued trouble.

We will provide another update within 30 minutes or sooner if new information becomes available.

The Heroku status page is now back online, Heroku customers can find specific instructions on the manual dyno start/stop instructions here: https://status.heroku.com/incidents/2822

Alongside the manual dyno stop/start guidance, we’ve initiated a fleetwide dyno restart that is expected to take approximately three hours to fully propagate. If you choose to manually restart your dynos before the automated process reaches your services, please be aware that there may be a brief period of service degradation when the automated restart is applied.

We’ll provide another update once the fleetwide restart is complete, or sooner if new information becomes available.

We continue to see improved performance across the fleet as the upgrade is rolled out. There is no ETA as to when this will be completed. We have received validation that customers using Heroku Connect report the platform is performing as expected. Heroku customers can continue to find specific instructions on the manual dyno start/stop instructions here: https://status.heroku.com/incidents/2822. While we continue implementing fixes to resolve this incident, as a workaround, customers can review KB: Remediation steps for Heroku Incident: https://help.heroku.com/6RBHRPNK/remediation-steps-for-heroku-incident-on-june-10-2025.

We have received new reports that data.heroku.com is not functioning as expected, and this is being investigated.

We’ll provide another update once the fleetwide restart is complete, or sooner if new information becomes available.

The Salesforce Technology team continues to pursue deploying fleetwide updates to the Heroku platform as the primary route to bringing all impacted Salesforce Clouds out of impact. An automated change to our Heroku platform has been identified as the likely root cause of the issue affecting Salesforce Clouds via Heroku integrations. Heroku Cloud customers able to change their own Heroku configurations can follow instructions in the KB post, which should restore their services sooner than the fleetwide update: https://help.heroku.com/6RBHRPNK/remediation-steps-for-heroku-incident-on-june-10-2025

The following Salesforce Clouds have been confirmed as being out of impact: Marketing Cloud Engagement, Gov Cloud, Marketing Cloud Intelligence, Revenue Cloud, and investigations into the data.heroku.com issue show that this is also now working as expected. Salesforce Clouds that are seeing improvement but are not fully restored at this time are: Tableau, Commerce Cloud, Heroku, and Service Cloud/Core Platform.

We’ll provide another update once the fleetwide restart is complete, or sooner if new information becomes available.