Fivetran incident
3rd Party: Some Impact Brand connections are failing with "HTTP 500 Internal server" error
Fivetran experienced a minor incident on June 7, 2026 affecting General Services, lasting 50m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 07, 2026, 06:20 AM UTC
The issue has been identified and we are working to resolve it.
- identified Jun 07, 2026, 06:48 AM UTC
We identified that this issue is caused by the source API returning 500 Internal Server Errors, impacting the following tables: performance_by_partner, performance_by_day, adv_performance_by_ad_media_date. We have reached out to the source regarding this issue. We are also observing that affected connectors are recovering without any intervention from Fivetran. Next Expected Update:
- monitoring Jun 07, 2026, 07:25 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 07, 2026, 07:38 AM UTC
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 with the Impact Brand connections, which resulted in syncs failing with 500 Internal Server Errors on the following reporting endpoints:performance_by_partner, performance_by_day, adv_performance_by_ad_media_date Timeline: This issue began on 2026-06-07 at 05:16:55 UTC and was resolved on 2026-06-07 at 19:00:55 UTC. Cause: The failure was caused by a server-side issue on the Impact source. Resolution: We reached out to the Impact source team to investigate the 500 Internal Server Errors. The issue has now been resolved on the Impact side, and no action was taken from Fivetran.