rewindex

CompaniesHightouchIncidents

Hightouch: Processing delay for subset of Events

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.hightouch.io (opens in new tab)
Part of an outage event

AWS outage, Nov 6, 2026 · 9 vendors, 9 incidents

Hightouch’s incident names AWS (location or integration). (hop 1, posted −1 h 51 min vs AWS’s own post)

“…etween 3:45 PM and 4:40 PM ET, a small portion of events sent to Event Streaming syncs in us-east-1 were delayed by up to 55 minutes. The underlying problem has been addressed and all impacted Events…”

Swipe sideways to see the whole diagram.

depends on AWSAWSposted 22:51 UTCPosted before AWS did1 vendorHightouchWithin an hour3 vendors, 2 blamed AWSDagster, Databricks, Semgrep1 to 4 hours later1 vendor, 1 blamed AWSStarburstKnown dependency3 vendorsBandwidth, Sigma Computing, SegmentHightouch (this incident)posted −1 h 51 min
depends on AWSAWSposted 22:51 UTCPosted before AWS did1 vendorHightouchWithin an hour3 vendors, 2 blamed AWSDagster, Databricks, Semgrep1 to 4 hours later1 vendor, 1 blamed AWSStarburstKnown dependency3 vendorsBandwidth, Sigma Computing,SegmentHightouch (this incident)posted −1 h 51 min
Hightouch is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS<br/>posted 22:51 UTC"]:::root
  before["Posted before AWS did<br/>1 vendor<br/>Hightouch"]:::names
  root --> before
  h1["Within an hour<br/>3 vendors, 2 blamed AWS<br/>Dagster, Databricks, Semgrep"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed AWS<br/>Starburst"]:::blames
  root --> h4
  dr["Known dependency<br/>3 vendors<br/>Bandwidth, Sigma Computing, Segment"]:::hop2
  root -.->|"depends on AWS"| dr
  me["Hightouch (this incident)<br/>posted −1 h 51 min"]:::me
  before --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    We identified and resolved an issue affecting event processing. Between 3:45 PM and 4:40 PM ET, a small portion of events sent to Event Streaming syncs in us-east-1 were delayed by up to 55 minutes.
    The underlying problem has been addressed and all impacted Events have been successfully processed. There was no data loss, and no action is required at this time.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on status.hightouch.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Hightouch, started 2026-11-06 21:00 UTC, resolved after 0 min, 1 update(s).

Title
Processing delay for subset of Events
Vendor
Hightouch
Date
URL
https://rewindex.com/company/hightouch/incidents/4gz9vdd3fvxq

Hightouch profileRecent Hightouch incidentsAll outages on November 6, 2026Hightouch in November 2026MarkdownJSON