Vendor reports: operationalResolved · vendor status “resolved”Official status API

Processing delay and duplicate delivery for subset of Events

Reported by Hightouch · Data & Analytics · source last read 5 min ago

Official source (opens in a new tab)
Vendor start
Aug 5, 2026, 20:14 UTC
Vendor's clock
Resolved
Aug 5, 2026, 20:14 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
Not available
Needs both vendor times

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Hightouch reports operational: "Processing delay and duplicate delivery for subset of Events".[E1, E2]
  • The vendor marked it resolved at 2026-08-05 20:14 UTC.[E3, E7]

Affected products and regions

  • Components: Event syncing (US), Real-time Personalization (US).[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-08-05 20:14 UTC · summary s1, evidence 07093f83709bb2d7

Evidence (7)
  1. E1Hightouch reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Processing delay and duplicate delivery for subset of Events". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-08-05 20:14 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Event syncing (US), Real-time Personalization (US). (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-08-05 20:14 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Event syncing (US), Real-time Personalization (US)

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Hightouch is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Aug 5, 2026, 20:14 UTCVendor-reported startVendor time
  2. Aug 5, 2026, 20:14 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.

Hightouch: Processing delay and duplicate delivery for subset of Events — statuswall