- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu, eu-west-1
- Down Index
- 16of 100
What to do
Check whether you use Hightouch in eu, eu-west-1. 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-05-01 23:48 UTC and 2025-05-01 21:55 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
Starting at 21:55 UTC, a small number of customers using SSH tunnels in the AWS eu-west-1 region experienced a delay in the execution of their sync runs. A temporary issue with our SSH tunneling infrastructure caused some syncs to remain in a queued state longer than usual. The issue has been resolved, and the affected syncs have since completed. 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-6ef38e172b
Is Hightouch still down?
No, this incident was resolved 2025-05-01 21:55 UTC. For Hightouch's live state, see https://down.guide/hightouch.
How long did it last?
0m, from 2025-05-01 23:48 UTC to 2025-05-01 21:55 UTC, by the times Hightouch posted.
What was affected?
Hightouch named in eu, eu-west-1.
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.