Skip to main content
Hightouch

Processing delay for subset of syncs

Degraded Lasted 2h 12m · started · Hightouch's page

Level
confirmed
Worst impact
Degraded
Components
AWS ap-south-1 (Mumbai), AWS eu-west-1 (Ireland), AWS us-east-1 (N. Virginia), GCP us-east4 (N. Virginia), GCP europe-west1 (Belgium), Azure eastus (Virginia)
Regions
ap-south-1, apac, eu, eu-west-1, europe-west1, us, us-east-1, us-east4
Down Index
39of 100

What to do

  • Check whether you use Hightouch AWS ap-south-1 (Mumbai), AWS eu-west-1 (Ireland), AWS us-east-1 (N. Virginia), GCP us-east4 (N. Virginia) and 2 more in ap-south-1, apac, 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 2h 12m it lasted.

    Anything that failed between 2026-08-07 00:48 UTC and 2026-08-07 03:01 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

  1. investigating

    We are currently investigating an issue causing delays for some sync runs. A subset of syncs may also experience failures. We will provide an update as more information becomes available.

    provider

  2. monitoring

    Service is recovering, though some sync runs may continue to experience delays. We are monitoring recovery.

    provider

  3. resolved

    This issue has been resolved. Between 8:14 PM and 9:22 PM ET, some sync runs experienced delays or failures. Event delivery was also delayed between 7:33 PM and 9:28 PM ET. There was no data loss. Affected syncs will recover on their next scheduled run. All services are now operating normally.

    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-f06d6157cb

Is Hightouch still down?

No, this incident was resolved 2026-08-07 03:01 UTC. For Hightouch's live state, see https://down.guide/hightouch.

How long did it last?

2h 12m, from 2026-08-07 00:48 UTC to 2026-08-07 03:01 UTC, by the times Hightouch posted.

What was affected?

Hightouch named AWS ap-south-1 (Mumbai), AWS eu-west-1 (Ireland), AWS us-east-1 (N. Virginia), GCP us-east4 (N. Virginia) and 2 more in ap-south-1, apac, 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.