Hightouch Status

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Investigating: We are continuing to investigate this issue.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Investigating: We are continuing to investigate this issue.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Investigating: We are continuing to investigate this issue.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Investigating: We are continuing to investigate this issue.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Investigating: We are continuing to investigate this issue.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Investigating: We are continuing to investigate this issue.

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.

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.

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.

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.

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.

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.

Investigating: We are continuing to investigate this issue.

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.

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.

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.

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.

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.

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.

Investigating: We are continuing to investigate this issue.

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.

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.

Monitoring: A fix has been implemented and we are monitoring the results. No action is required. The next scheduled sync will resolve the issue, or you can manually trigger one at any time.

Investigating: We’re investigating an issue causing a subset of Hightouch file drop destinations to not respect column order when writing data to the destination file. File drop syncs to S3 and SFDC in Archive mode were impacted

If you are seeing your data incorrectly ordered, rerunning your sync should resolve the issue.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Investigating: We are continuing to investigate this issue.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.