3rd Party: Some syncs are delayed in the AWS us-east-1 region
Incident
Report for Fivetran
Resolved
We have marked this incident as resolved. Sync rates are returning to normal levels and affected connectors are syncing successfully.
Incident Summary
Description:
We have identified an issue where some syncs are being delayed in the AWS us-east-1 region due to issues with the underlying cloud service provider. After the resolution from Amazon, we started to see sync failure for the connectors pointed at Managed Data Lake Service destinations largely due to rate limiting on STS calls from AWS side.
Timeline:
We noticed sync failures from October 20, 2025 at 14:30 UTC. Our syncs reverted to a normal state effective October 21, 2025 at 2:40 UTC.
Cause:
Issue was caused due to an outage on the third party side (Amazon Web Services).
Resolution:
The third party provider resolved their operational issues which fixed the connector sync issue on our side. Additionally, the STS rate limit issue from AWS causing sync failure to the connectors syncing to Managed Data Lake Service destinations, was auto resolved in few hours after the fix. You can find more detail below.
https://health.aws.amazon.com/health/status
Incident Summary
Description:
We have identified an issue where some syncs are being delayed in the AWS us-east-1 region due to issues with the underlying cloud service provider. After the resolution from Amazon, we started to see sync failure for the connectors pointed at Managed Data Lake Service destinations largely due to rate limiting on STS calls from AWS side.
Timeline:
We noticed sync failures from October 20, 2025 at 14:30 UTC. Our syncs reverted to a normal state effective October 21, 2025 at 2:40 UTC.
Cause:
Issue was caused due to an outage on the third party side (Amazon Web Services).
Resolution:
The third party provider resolved their operational issues which fixed the connector sync issue on our side. Additionally, the STS rate limit issue from AWS causing sync failure to the connectors syncing to Managed Data Lake Service destinations, was auto resolved in few hours after the fix. You can find more detail below.
https://health.aws.amazon.com/health/status
Monitoring
Connectors pointed at Managed Data Lake Service destinations have been failing largely due to rate limiting on STS calls. However, we are observing significant improvement in successful syncs. We believe that the relevant issues should be fully resolved in the next 2-3 hours. We are continuing to monitor.
Update
AWS has marked the incident as resolved, but we are continuing to see AWS outage related issues resulting in sync failures for connectors pointed at Managed Data Lake Service destinations. Our developers are actively investigating ways to mitigate these failures.
Update
We are starting to see improvements and successful syncs for connectors pointed at Redshift warehouses. AWS has assured us that they are continuing to work on resolving this incident.
Update
AWS has communicated that they are continuing to work on this incident.
Update
We are in contact with AWS. They have recently communicated that they are working to resolve the incident on their end.
Managed Data Lake Service destinations in regions outside of AWS us-east-1 have also seen related failures.
The AWS status page can also be found here: https://health.aws.amazon.com/health/status
We will continue to provide updates as we have them.
Managed Data Lake Service destinations in regions outside of AWS us-east-1 have also seen related failures.
The AWS status page can also be found here: https://health.aws.amazon.com/health/status
We will continue to provide updates as we have them.
Identified
We have identified an issue where some syncs are being delayed in the AWS us-east-1 region due to issues with the underlying cloud service provider. We are currently investigating in more detail and will provide additional updates accordingly.
This incident affected: Systems (Destinations).