Skip to main content
Hightouch

Processing delay and duplicate delivery for subset of Events

Degraded Lasted 0m · started · Hightouch's page

Level
confirmed
Worst impact
Degraded
Components
Event syncing (US), Real-time Personalization (US)
Regions
us, us-east-1
Down Index
16of 100

What to do

  • Check whether you use Hightouch Event syncing (US), Real-time Personalization (US) in us, us-east-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 2026-08-05 20:14 UTC and 2026-08-05 20:14 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

    We identified and resolved an issue affecting event processing. Between 2:50 PM and 3:55 PM ET, a subset of customers in us-east-1 experienced delayed event processing up to 50 minutes across Event Streaming, Warehouse syncs and Realtime Audiences. A small number of events delivered through Event Streaming syncs may have been duplicated. Warehouse syncs and Realtime Audiences for affected events were delayed during this time. The underlying problem has been addressed and all impacted Events have been successfully processed, there was 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-ecfe61e2a1

Is Hightouch still down?

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

How long did it last?

0m, from 2026-08-05 20:14 UTC to 2026-08-05 20:14 UTC, by the times Hightouch posted.

What was affected?

Hightouch named Event syncing (US), Real-time Personalization (US) in us, us-east-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.