- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Sources
- Down Index
- 28of 100
What to do
Check whether you use Hightouch Sources. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 53m it lasted.
Anything that failed between 2025-10-10 10:45 UTC and 2025-10-10 11:38 UTC may need a replay.Subscribe to Hightouch's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=hightouch works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Hightouch 3
- monitoring
We are investigating an issue causing a subset of Databricks syncs to fail. We will provide an update as soon as we have more information.
provider
- investigating
We are currently investigating this issue.
provider
- resolved
We’ve resolved an issue that caused some Databricks syncs to fail. No action is required. Syncs will resume on their next scheduled run, or you can manually trigger a run at any time.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-8884060bdf
Is Hightouch still down?
No, this incident was resolved 2025-10-10 11:38 UTC. For Hightouch's live state, see https://down.guide/hightouch.
How long did it last?
53m, from 2025-10-10 10:45 UTC to 2025-10-10 11:38 UTC, by the times Hightouch posted.
What was affected?
Hightouch named Sources.
What caused it?
Hightouch hasn't published a root cause. If it does, it shows here.
Where does this come from?
Hightouch's official status page, https://status.hightouch.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.