Skip to main content
Hightouch

Upstream AWS outage continuing to impact some Hightouch services intermittently

Degraded Lasted 12h 21m · started · Hightouch's page

Level
confirmed
Worst impact
Degraded
Components
AWS ap-south-1 (Mumbai), Sources, AWS eu-west-1 (Ireland), Destinations, Event syncing (US), AWS us-east-1 (N. Virginia), GCP us-east4 (N. Virginia), GCP europe-west1 (Belgium), Azure eastus (Virginia)
Regions
ap-south-1, apac, eu, eu-west-1, europe-west1, us, us-east-1, us-east4
Down Index
43of 100

What to do

  • Check whether you use Hightouch AWS ap-south-1 (Mumbai), Sources, AWS eu-west-1 (Ireland), Destinations and 5 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 12h 21m it lasted.

    Anything that failed between 2025-10-20 14:26 UTC and 2025-10-21 02:47 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 7

  1. investigating

    Some Hightouch services are showing higher error rates and latency due to an upstream AWS outage in the us-east-1 region. Syncs from Databricks, Redshift and Snowflake instances in the us-east-1 region are more significantly impacted.

    provider

  2. investigating

    We are continuing to investigate this issue.

    provider

  3. monitoring

    As we continue to monitor, we can provide additional clarity on impact: - Hightouch Events: Reduced availability; events from SDKs may not be captured in us-east-1 - Functions: Experiencing disruptions in us-east-1 - Sources + Destinations: Warehouse and destinations are affected, with potential duplicate event delivery to some streaming destinations. We are actively working to restore full service and will continue to provide updates as the situation evolves.

    provider

  4. monitoring

    Some Hightouch customers may be continuing to experience slow syncs or syncs that do not start on time. This is due to an upstream outage in the AWS us-east-1 region that is impacting Hightouch as well as some of our integration partners. Please do not attempt to cancel and restart syncs as this will disrupt your position in the queue. We will continue to update you as the situation progresses.

    provider

  5. monitoring

    AWS has recently completed remediating the underlying outage. Hightouch and our integration partners are working to ensure a return to normal operations as quickly as possible. Please do not attempt to cancel or restart syncs at this time. We will update you again within two hours.

    provider

  6. monitoring

    The sync pipeline has returned to normal as of 19:58 ET. We are continuing to monitor all services for health and stability. We are continuing to actively work to restore the Hightouch Events services. Event ingestion is fully recovered, but event delivery may be delayed until service is fully restored. We will provide updates as the situation evolves.

    provider

  7. resolved

    Hightouch Events services have been restored. Events may not have been collected during periods of full AWS downtime, any collected events were processed. No data was dropped once it was collected by Hightouch. All Hightouch services now appear to be stable. 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-815e0f4d9c

Is Hightouch still down?

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

How long did it last?

12h 21m, from 2025-10-20 14:26 UTC to 2025-10-21 02:47 UTC, by the times Hightouch posted.

What was affected?

Hightouch named AWS ap-south-1 (Mumbai), Sources, AWS eu-west-1 (Ireland), Destinations and 5 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.