6sense logo

Is 6sense Down?

SaaSLive status, outages, and incident history

No. 6sense is up right now.

Every monitored 6sense system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 5m agoLive · 60s while moving

Know the moment 6sense breaks

6sense is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official 6sense status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

6sense Component Status

The main 6sense systems on this page. All 15 are operational right now.

15operational
Account Based Marketing
Operational
Advertising
Operational
API » Company Firmographics API
Operational

12 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking API » Company Identification API, API » Lead Scoring and Firmographics API, API » Lead Scoring API, API » People Enrichment API, API » People Search API, Conversational Email, Platform » Alerts, Platform » Reports, Platform » Revcity, Platform » Segments, Sales Intelligence, Workflows and Orchestrations.

See all of them free

Component statuses may change independently during partial outages.

Recent 6sense Outages & Incidents

Incident history from the official 6sense status page, including resolution updates.

AI Email Outlook IntegrationResolved Sep 11, 2026 · 0 minResolved

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.

Authentication Errors with Salesforce and Pardot IntegrationsResolved Aug 6, 2026 · 509h 3mResolved

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. As a result, some Salesforce and Pardot integrations unexpectedly became disconnected. This configuration was not intentionally enabled by 6sense and we were not previously aware that it was active on the affected Connected Apps. The configuration is not exposed through the standard Salesforce interface and we are working directly with Salesforce to understand this better. We will continue to work with Salesforce on the remaining follow-up items and long-term measures to help prevent similar issues in the future. 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 to ensure they remain stable. 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. --- [2026-08-17T14:21:54.052Z] (monitoring) 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. --- [2026-08-13T13:47:45.583Z] (investigating) 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. --- [2026-08-12T19:16:53.613Z] (investigating) 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. --- [2026-08-11T15:29:34.230Z] (investigating) 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. --- [2026-08-10T18:44:39.355Z] (investigating) 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. --- [2026-08-07T13:48:56.416Z] (investigating) 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. --- [2026-08-06T13:55:00.998Z] (investigating) We are continuing to investigate this issue. --- [2026-08-06T07:41:15.125Z] (investigating) 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.

Sales Intelligence: Export FailureResolved Aug 4, 2026 · 4h 11mResolved

This incident has been resolved. --- [2026-08-04T18:50:40.317Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-08-04T15:27:46.837Z] (investigating) 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.

6sense Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a 6sense incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 10 days with incidentsSep 25

Live 6sense Outage Reports

Problems reported by engineers using 6sense. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No 6sense problems reported yet.

Something wrong with 6sense on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About 6sense

6sense exposes 17 monitored components on its status page at status.6sense.com — Sales Intelligence, Company Identification API and Segments among them. Follow 6sense downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured 6sense uptime at 100.00%. Response times, incident history, and SLA tracking for 6sense are available on the PulsAPI dashboard.

6sense Status FAQ

Is 6sense down right now?

The verdict at the top of this page comes from the latest poll of the official 6sense status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if 6sense is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until 6sense recovers.

How do I check 6sense uptime history?

PulsAPI tracks 6sense uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever 6sense changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect 6sense outages?

PulsAPI reads the official 6sense status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual 6sense components?

Yes. PulsAPI monitors 15 individual 6sense components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when 6sense goes down?

Yes. Create a free account and subscribe to 6sense: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with 6sense to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot 6sense problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor 6sense?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so 6sense plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track 6sense with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services