Skip to main content
Hightouch

Hightouch sync run delays

Degraded Lasted 0m · started · Hightouch's page

Level
confirmed
Worst impact
Degraded
Regions
us, us-east4
Down Index
16of 100

What to do

  • Check whether you use Hightouch in us, us-east4. 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 2026-09-24 14:29 UTC and 2026-09-24 14:27 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

  1. resolved

    A small number of sync runs may have encountered delays in sending data between 13:05 and 13:40 UTC in GCP us-east4. All syncs are now running normally with no data loss.

    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-5586c449bd

Is Hightouch still down?

No, this incident was resolved 2026-09-24 14:27 UTC. For Hightouch's live state, see https://down.guide/hightouch.

How long did it last?

0m, from 2026-09-24 14:29 UTC to 2026-09-24 14:27 UTC, by the times Hightouch posted.

What was affected?

Hightouch named in us, us-east4.

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.