Skip to main content
Hightouch

Upstream AWS outage impacting some Hightouch services

Partial outage Lasted 2h 44m · started · Hightouch's page

Level
confirmed
Worst impact
Partial outage
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)
Regions
ap-south-1, apac, eu, eu-west-1, europe-west1, us, us-east-1, us-east4, us-west-2
Down Index
50of 100

What to do

  • Check whether you use Hightouch AWS ap-south-1 (Mumbai), Customer API, AWS eu-west-1 (Ireland), Event ingestion (US) and 11 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 44m it lasted.

    Anything that failed between 2025-10-20 07:47 UTC and 2025-10-20 10:31 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 6

  1. identified

    Some Hightouch services are currently unavailable or showing higher error rates due to an upstream AWS outage. Our team is monitoring the AWS incident and taking steps to recover affected services where possible.

    provider

  2. identified

    Our team is monitoring the AWS incident and taking steps to recover affected services where possible. Users may experience queued syncs or elevated error rates until the upstream outage is resolved.

    provider

  3. identified

    We are monitoring the upstream AWS outage and taking steps to restore affected services where possible. Users may experience queued syncs or elevated error rates until the upstream issue is resolved. AWS has not provided an estimated time for recovery. We will continue to post updates as we learn more.

    provider

  4. monitoring

    We are observing signs of recovery following the upstream AWS outage. Our engineering teams are working to accelerate recovery of affected services. Users may continue to experience queued syncs or elevated error rates during this period. We will provide an update once recovery is complete.

    provider

  5. monitoring

    We’ve confirmed full recovery across most services and features. Syncs are now processing normally for nearly all customers. However, some customers using sources hosted in AWS may continue to experience errors if those services remain affected by the upstream AWS incident. Event delivery may still be delayed, and we’re working to expedite recovery for that service.

    provider

  6. resolved

    All Hightouch services have been restored following the upstream AWS incident. If you have any questions or need assistance, please reach out to our support team.

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

Is Hightouch still down?

No, this incident was resolved 2025-10-20 10:31 UTC. For Hightouch's live state, see https://down.guide/hightouch.

How long did it last?

2h 44m, from 2025-10-20 07:47 UTC to 2025-10-20 10:31 UTC, by the times Hightouch posted.

What was affected?

Hightouch named AWS ap-south-1 (Mumbai), Customer API, AWS eu-west-1 (Ireland), Event ingestion (US) and 11 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.