Is 6sense down?

We are aware that some customers using the 6sense Sales Intelligence integration with HubSpot are seeing an in-product message indicating that the 6sense Sales Intelligence card will be removed after October 31, 2026, as part of HubSpot’s planned deprecation of Legacy CRM Cards. HubSpot has announced that integrations using Legacy CRM Cards will need to transition to its newer App Card framework before this date. At this time, there is no impact to the functionality of the 6sense integration and no action is required from customers. Customers can continue using the integration as normal. Our Product and Engineering teams are reviewing the change and evaluating any updates that may be required for the 6sense integration. We will provide additional guidance if customer action becomes necessary or if there is any change to the current functionality. We will continue to share updates as more information becomes available.

Update - As of October 31st, HubSpot will complete its planned retirement of Legacy CRM Cards, the older framework that powers the 6sense Sales Intelligence iframe. After this date, HubSpot will remove all Legacy CRM Cards, which is why some customers are seeing a banner in the iframe saying it will be removed. Ahead of HubSpot’s deadline, 6sense is moving the Sales Intelligence iframe to HubSpot’s newer App Card framework. We're currently on track to complete this on Monday, October 19th. What this means for you No action is required. You can keep using the Sales Intelligence iframe as usual and you can disregard the banner’s suggestion to contact us since our team is already handling the migration. If you experience any disruption in your Sales Intelligence iframe in Hubspot after the update on October 19th, please reach out to our support team.

We are currently experiencing an issue affecting outbound email delivery from the 6sense.com domain. This issue is limited to emails sent from our organization and does not impact customers' ability to send or receive emails through their own email systems. While we work to resolve the issue, our Support team will continue to provide updates on support cases directly within RevCity. We encourage customers to log in to RevCity https://revcity.6sense.com to monitor case activity and review the latest updates. We apologize for the inconvenience and will provide further updates as they become available.

The issue has been resolved and affected services are operating normally. We will continue to monitor the situation. Thank you for your patience.

On Friday, September 11, 2026, an issue occurred for a subset of customers using the AI Email Agent with Outlook, in which the integration became disconnected. The issue has now been resolved and affected services have been restored.. Impacted customers were sent an email indicating that their connection was interrupted. Our Engineering team has since restored all AI Email connections for customers who received a notification email. Campaigns were automatically paused when the integrations were disconnected, and were automatically resumed once reconnected If you continue to experience any issues please contact Support for assistance.

We are investigating an issue impacting a subset of customers using Salesforce and Pardot integrations. Affected customers may see an "Authentication Failed" error message when viewing their integration page. As a mitigation, customers experiencing this issue can update their integration credentials, which may restore the connection. If the issue persists after updating the credentials, please contact Support for further assistance. Our Engineering team is actively investigating the issue and we will provide additional updates as more information becomes available.

We are continuing to investigate this issue.

Update - We continue to investigate the Salesforce authentication issue affecting a subset of customers using Salesforce and Pardot integrations. Based on our investigation to date, the issue appears to be related to Salesforce integration credential expiration and may result in affected integrations requiring reauthorization. Customers who see their Salesforce Integration in an Error status can continue to update their integration credentials as a workaround. If the issue persists after reauthorizing, please contact Support. Our Engineering team remains actively engaged in identifying a long-term solution, and we will continue to share updates as our investigation progresses.

Update: Our Engineering team continues to investigate the Salesforce authentication issue affecting a subset of customers using Salesforce-connected data sources, including CRM integrations and AI Email. Our investigation indicates that the authentication failures originate outside of the 6sense platform and are related to Salesforce OAuth authentication. We have not identified any changes within the 6sense platform that would account for the observed behavior. As part of our investigation, we have observed a strong correlation between the timing of the affected connections and recent Salesforce OAuth refresh token behavior and we are actively working with Salesforce to determine the underlying cause and implement a long-term resolution. Customers whose Salesforce integration is affected may see the connection enter a disconnected state, resulting in delayed data synchronization and downstream processing until the connection is successfully reauthenticated. As a workaround, customers experiencing an "Authentication Failed" error or a disconnected Salesforce integration should reauthenticate their connection by navigating to Settings > Integrations > Salesforce. Reauthentication has successfully restored connectivity for the majority of affected customers. We will continue to provide updates as our investigation progresses.

Our Engineering team continues to actively investigate the Salesforce authentication issue affecting a subset of customers using Salesforce-connected data sources, including CRM /MAP integrations and AI Email. Since our last update, our joint investigation with Salesforce has narrowed the issue to a Salesforce OAuth refresh-token configuration that may be contributing to the unexpected token expirations and resulting integration disconnections. Salesforce is currently validating a configuration change in a controlled environment to determine whether it resolves the observed behavior. We continue to work closely with Salesforce while this validation is underway. Customers whose Salesforce / Pardot integration is affected may continue to see the connection enter a disconnected state, resulting in delayed data synchronization and downstream processing until the connection is successfully reauthenticated. As a workaround, customers experiencing an "Authentication Failed" error or a disconnected Salesforce / Pardot integration should reauthenticate their connection by navigating to Settings > Integrations > Salesforce / Pardot. Reauthentication continues to successfully restore connectivity for the majority of affected customers. We appreciate your patience as we work with Salesforce to validate the underlying cause and implement a long-term resolution. We will continue to provide updates as more information becomes available.

Update: Our Engineering team continues to work closely with Salesforce on the investigation into the Salesforce authentication issue affecting a subset of customers using Salesforce-connected data sources, including CRM/MAP integrations and AI Email. Since our last update, the investigation has progressed further and Salesforce Support has identified a Salesforce-managed backend configuration related to refresh-token expiration that may be contributing to the unexpected token expirations and resulting integration disconnections. This configuration is not exposed through the Salesforce user interface. We are working with Salesforce to validate the impact of this configuration and determine whether a change will resolve the observed behavior. The validation is ongoing and we are continuing to monitor affected integrations while we work toward a long-term resolution. Customers whose Salesforce/Pardot integration is currently disconnected or displaying an "Authentication Failed" error should reauthenticate their connection by navigating to Settings > Integrations > Salesforce/Pardot. Reauthentication continues to successfully restore connectivity for the majority of affected customers. We understand the impact this issue may have on data synchronization and downstream processing and appreciate your continued patience. We will provide further updates as our investigation and validation with Salesforce progresses.

Update: Our Engineering team continues to work closely with Salesforce to address the authentication issue affecting a subset of customers using Salesforce-connected data sources. For the Salesforce Connected App used by the 6sense ABM and Sales Intelligence (SI) platform, Salesforce has implemented a configuration change related to Salesforce OAuth refresh-token behavior. We are actively monitoring the effectiveness of this change to confirm that it prevents new unexpected integration disconnections. Customers whose Salesforce/Pardot integration within the ABM or Sales Intelligence platform was previously disconnected or is currently displaying an "Authentication Failed" error will still need to reauthenticate their connection to restore connectivity. Please navigate to Settings > Integrations > Salesforce/Pardot to complete the reauthentication. Customers whose integrations are currently authenticated and operating normally do not need to take any action at this time. For the AI Email platform, our investigation remains ongoing. We are continuing to work closely with Salesforce, as the configuration change has not yet been applied to the Salesforce Connected App used by AI Email. We will continue to provide updates as we make progress toward a long-term resolution. We appreciate your patience and will continue to share updates as our investigation progresses.

Our Engineering team, in collaboration with Salesforce, has implemented the configuration changes related to Salesforce OAuth refresh-token behavior for the Connected Apps used by our ABM, Sales Intelligence (SI) and AI Email platforms. We are actively monitoring the integrations to validate the effectiveness of these changes and to identify any potential downstream impact. At this time, customers whose Salesforce/Pardot integrations are currently authenticated and operating normally do not need to take any action. Customers whose integration is currently disconnected or displaying an "Authentication Failed" error will still need to reauthenticate their connection to restore connectivity. Please navigate to Settings > Integrations > Salesforce/Pardot to complete the reauthentication. We will continue to closely monitor the integrations and provide further updates as we validate the stability of the changes. We appreciate your patience and understanding while we work through this issue.

We have completed remediation for the Salesforce authentication issue affecting a subset of customers using Salesforce-connected data sources. Our investigation with Salesforce confirmed that a backend configuration, Refresh Token TTL, was enabled on the affected Connected Apps. This configuration caused refresh tokens to expire after a fixed period of approximately 30 days, even when the integrations continued to actively use them. This resulted in unexpected integration disconnections for affected customers. Working with Salesforce, we updated the affected Connected App configurations to address this behavior. We have validated the changes and will continue to monitor the integrations. Customers whose Salesforce/Pardot connections were previously disconnected may still need to reauthenticate their integration to restore connectivity. Customers whose integrations are currently connected and operating normally do not need to take any action. We will continue to work with Salesforce on remaining follow-up items and long-term measures to help prevent similar issues in the future.

We are aware of an issue impacting the performance of Sales Intelligence export jobs, which is causing some jobs to fail. Our Engineering teams are actively investigating the matter and working diligently to resolve it as quickly as possible. We appreciate your patience and understanding as we work to address this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.