Vendor reports: partial outageResolved · vendor status “resolved”Official status API

Upstream AWS outage impacting some Hightouch services

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

Official source (opens in a new tab)
Vendor start
Oct 20, 2025, 07:47 UTC
Vendor's clock
Resolved
Oct 20, 2025, 10:31 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
2 h 44 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Hightouch reports partial outage: "Upstream AWS outage impacting some Hightouch services".[E1, E2]
  • The vendor marked it resolved at 2025-10-20 10:31 UTC.[E3, E7]

Affected products and regions

  • Components: AWS ap-south-1 (Mumbai), Customer API, AWS eu-west-1 (Ireland), Event ingestion (US), AWS eu-west-1 (Ireland), Partner API, AWS us-east-1 (N. Virginia), Event syncing (US), AWS us-east-1 (N. Virginia), AWS us-west-2 (Oregon), Event ingestion (EU), GCP us-east4 (N. Virginia), Event syncing (EU), GCP europe-west1 (Belgium), Azure eastus (Virginia).[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: 2025-10-20 10:31 UTC · summary s1, evidence d563735d13f322fa

Evidence (7)
  1. E1Hightouch reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Upstream AWS outage impacting some Hightouch services". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-10-20 07:47 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: AWS ap-south-1 (Mumbai), Customer API, AWS eu-west-1 (Ireland), Event ingestion (US), AWS eu-west-1 (Ireland), Partner API, AWS us-east-1 (N. Virginia), Event syncing (US), AWS us-east-1 (N. Virginia), AWS us-west-2 (Oregon), Event ingestion (EU), GCP us-east4 (N. Virginia), Event syncing (EU), GCP europe-west1 (Belgium), Azure eastus (Virginia). (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-10-20 10:31 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: AWS ap-south-1 (Mumbai), Customer API, AWS eu-west-1 (Ireland), Event ingestion (US), AWS eu-west-1 (Ireland), Partner API, AWS us-east-1 (N. Virginia), Event syncing (US), AWS us-east-1 (N. Virginia), AWS us-west-2 (Oregon), Event ingestion (EU), GCP us-east4 (N. Virginia), Event syncing (EU), GCP europe-west1 (Belgium), Azure eastus (Virginia)

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. Oct 20, 2025, 07:47 UTCVendor-reported startVendor time
  2. Oct 20, 2025, 10:31 UTCVendor-reported resolutionVendor time

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