Current answer
Fivetran experienced a minor incident: 3rd Party: Impact connections experiencing sync issue. Resolved on Sep 29, 2026.
The notice publication date does not establish the outage start. Provider resolved: .
Looking for an update now? Check the current status, or follow Fivetran for future changes.
Provider notice timeline
Affected Components
Impact Brand
Incident Timeline
Resolved
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully.
Incident Summary
Description:
We identified an issue affecting the Impact connector. The source did not return data within the expected wait period, causing syncs to fail with the following error: “The Impact server encountered an unknown failure that prevented it from fulfilling our request. We will sync later.”
Timeline:
The issue began on 2026-09-29 at 8:30 AM UTC and was resolved on 2026-09-29 at 12:18 PM UTC.
Cause:
Impact connections were failing on the performance_by_day endpoint because the poll job remained in QUEUED status and did not complete. We check the job status through the performance_by_day_queued endpoint, with a maximum of 30 retries while waiting for the status to change from QUEUED to SUCCESS. The job did not complete within those retries, causing the affected connections to fail.
Resolution:
Fivetran increased the polling wait time and implemented logic to skip the affected endpoint if its report job does not complete within the maximum wait time. This allows affected connectors to continue syncing.
Incident Summary
Description:
We identified an issue affecting the Impact connector. The source did not return data within the expected wait period, causing syncs to fail with the following error: “The Impact server encountered an unknown failure that prevented it from fulfilling our request. We will sync later.”
Timeline:
The issue began on 2026-09-29 at 8:30 AM UTC and was resolved on 2026-09-29 at 12:18 PM UTC.
Cause:
Impact connections were failing on the performance_by_day endpoint because the poll job remained in QUEUED status and did not complete. We check the job status through the performance_by_day_queued endpoint, with a maximum of 30 retries while waiting for the status to change from QUEUED to SUCCESS. The job did not complete within those retries, causing the affected connections to fail.
Resolution:
Fivetran increased the polling wait time and implemented logic to skip the affected endpoint if its report job does not complete within the maximum wait time. This allows affected connectors to continue syncing.
Sep 29, 2026 at 4:43 PM UTC
Monitoring
We have deployed a fix for this issue by increasing the poll job wait time and skipping the affected endpoint if the poll job does not complete within the maximum wait time.
We will continue to monitor all affected connectors until they resume their normal sync functionality.
Next Expected Update: 3 hours
We will continue to monitor all affected connectors until they resume their normal sync functionality.
Next Expected Update: 3 hours
Sep 29, 2026 at 1:20 PM UTC
Identified
We are still working on the fix.
Next Expected Update: 1 hour
Next Expected Update: 1 hour
Sep 29, 2026 at 12:33 PM UTC
Identified
We have identified an issue affecting the "performance_by_day report". Report jobs are remaining in QUEUED status and are not progressing, causing affected connections to fail.
We are currently investigating the issue with third-party.
Next Expected Update: 1 hour
We are currently investigating the issue with third-party.
Next Expected Update: 1 hour
Sep 29, 2026 at 11:00 AM UTC
Identified
We have identified an issue where Impact connections are failing with error "The impact server encountered an unknown failure that prevented it from fulfilling our request. We'll retry the sync later."
We are investigating the issue.
Next Expected Update: 1 hour
We are investigating the issue.
Next Expected Update: 1 hour
Sep 29, 2026 at 10:00 AM UTC
Was your business affected by this Fivetran outage?
Follow Fivetran and route available status alerts to email or a team channel.