- Level
- confirmed
- Worst impact
- Degraded
- Components
- Destinations
- Down Index
- 17of 100
What to do
Check whether you use Hightouch Destinations. 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 40m it lasted.
Anything that failed between 2026-07-20 11:42 UTC and 2026-07-20 12:22 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 2
- identified
We have identified an issue impacting a subset of syncs to Meta. We are actively investigating and working to resolve the issue, and will provide an update as soon as more information is available.
provider
- resolved
This incident has been resolved. There was no data loss. Impact was limited to Meta destinations. Syncs that failed during this window will complete successfully on their next scheduled run. No action is required.
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-0e1725d97f
Is Hightouch still down?
No, this incident was resolved 2026-07-20 12:22 UTC. For Hightouch's live state, see https://down.guide/hightouch.
How long did it last?
40m, from 2026-07-20 11:42 UTC to 2026-07-20 12:22 UTC, by the times Hightouch posted.
What was affected?
Hightouch named Destinations.
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.