Upstream AWS outage continuing to impact some Hightouch services intermittently

Hightouch Events services have been restored. There was no loss of data or events during this time, but events were delayed while we worked through the backlog.

All Hightouch services now appear to be stable. If you have any questions or need assistance, please reach out to our support team.

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.

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.

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.

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.

We are continuing to investigate this issue.

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.