- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Hightouch. 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 0m it lasted.
Anything that failed between 2025-07-31 17:16 UTC and 2025-07-31 14:30 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 1
- resolved
We identified and resolved an issue that may have caused up to a 2-hr delay in processing for a subset of Events. The underlying problem has been addressed, all impacted Events have been successfully processed, and Event processing has returned to normal.
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-1e202bc78e
Is Hightouch still down?
No, this incident was resolved 2025-07-31 14:30 UTC. For Hightouch's live state, see https://down.guide/hightouch.
How long did it last?
0m, from 2025-07-31 17:16 UTC to 2025-07-31 14:30 UTC, by the times Hightouch posted.
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.