Hightouch Outage History

Service appears restored, we will continue to monitor.

Between 4:20 PM PT on May 5 and 2:40 PM PT on May 6, a subset of Match Booster syncs did not complete successfully due to an enrichment issue. The issue has been resolved, and impacted syncs will recover on their next scheduled run. No action is required.

We identified and resolved an issue affecting event processing. Between 12:06 PM and 1:39 PM ET customers using tunnels to connect to Event sources experienced delays in event processing. 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.

We identified and resolved an issue affecting event processing. Between 1:13 PM and 3:12 PM ET, customers in us-east-1 experienced delayed event processing across Event Collection, Event Streaming, and Realtime Audiences. During this time, Event Streaming, Realtime Audiences, and Event Collection syncs to S3 may have also delivered duplicate events to downstream destinations. 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.

A subset of sync runs triggered between March 18 at 12:32 PM ET and March 19 at 10:37 AM ET may have experienced delays while in the processing state. This only affected sync runs with zero added and changed row operations. The issue was fully resolved as of 1:15 PM ET on March 19. No action is required.

We have identified and resolved the issue that caused intermittent failures for some in-app operations in workspaces hosted in the GCP europe-west1 region between 4:30 AM and 12:38 PM UTC. In-app behavior has returned to normal.

From 11:49 AM ET to 12:55 PM ET, an issue caused delays for a subset of events. No data was lost. The issue has been resolved, and performance has returned to normal.

Between 1:12PM PT (on January 14th) and 6:21AM PT (on January 15th), some Customer Studio journeys may have failed with “Journey execution blocked” errors. As a result, journey syncs may have been delayed, but no data loss has occurred. We have identified and resolved the issue. All functionality has returned to normal.

This incident has been resolved.

Between 7:24 AM PT and 8:06 AM PT, customers on legacy access control may have experienced issues accessing their Customer Studio audiences. Sync scheduling and execution were not impacted. This issue has been resolved.

This incident has been resolved.

Customer impact: - Syncs to S3 using All mode did not respect column order when writing data to the destination file. - Customers may have experienced failures for syncs to SFDC using Archive mode. No action is required. Syncs will resume on their next scheduled run, or you can manually trigger a run at any time.

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.

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.

We’ve resolved an issue that caused some Databricks syncs to fail. No action is required. Syncs will resume on their next scheduled run, or you can manually trigger a run at any time.

We’ve resolved an issue that caused some syncs to fail between 4:50 PM and 5:20 PM PT. No action is required. Syncs will resume on their next scheduled run, or you can manually trigger a run at any time.

This is now resolved. We have fully processed the backlog and syncs are now caught up and running as expected.

We identified an issue that caused delays of up to 50 minutes for a subset of sync runs starting around 5:20 PM ET. The issue has been resolved, and all syncs are now running on schedule. No action is required.

We fixed an issue caused by changes in Reddit’s API. Customers will need to re-authenticate their Reddit Ads connection for syncs to resume running successfully.

This UI issue has been resolved.

Between 8:06 AM and 9:40 AM PT, customers may have experienced issues accessing the app, as well as delays in rETL and event ingestion and processing. This issue has now been resolved. All functionality has returned to normal.

This issue has been resolved. We apologize for any disruptions to your day.

This incident has been resolved. Any incorrectly rejected rows will sync correctly on their next sync run.

The issue is fully resolved. All events are being delivered with normal latencies.

We have traced the issue back to a small number of API keys created by Hightouch users with invalid or expired Google auth. Affected users can reactivate their account (and associated API keys) by logging in to their workspace.