Is Fivetran down?

Description: We identified an issue affecting manual and API-triggered connection syncs, causing syncs to fail to start and return API errors. Timeline: This issue began on June 8, 2026, at 22:00 UTC and was resolved on June 8, 2026, at 22:35 UTC. Cause: The elevated API error count was caused by an incident with a third-party service used to orchestrate sync execution. As a result, requests to trigger connection syncs through both the API and the Fivetran dashboard were intermittently unsuccessful. Reference: https://status.temporal.io/incidents/8msytm7vpfbv Resolution: The third-party service provider resolved the underlying issue, restoring normal functionality. Following confirmation that sync triggering was operating as expected, the incident was closed. Customers can now successfully trigger syncs through both the API and the dashboard.

We have identified an issue where Microsoft Advertising connectors are failing with a "Report processing failed: (StreamProcessing)" exception. We are currently investigating in more detail. Next Expected Update:

We have performed an initial analysis and identified that the issue appears to be related to an incident with the Bing Ads Reporting API affecting the "GeographicPerformanceReport" report Next Expected Update:

The issue appears to have been resolved on the Microsoft end, and the affected connections are recovering. We will continue to monitor all affected connectors until they resume their normal sync functionality. Next Expected Update:

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 Microsoft Advertising connections, which resulted in syncs failing with a "Report processing failed: (StreamProcessing)" error. Timeline: This issue began on June 7, 2026, at 05:00 UTC and was resolved on June 7, 2026, at 13:00 UTC. Cause: The connectors that were syncing Geographic Performance report tables in Microsoft Ads started failing consistently due to an issue with the Microsoft Ads API on Microsoft's end. Resolution: This has been automatically resolved on the Microsoft Ads API affecting the GeographicPerformanceReport, and the connectors are succeeding now.

The issue has been identified and we are working to resolve it.

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:

A fix has been implemented and we are monitoring the results.

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.

The issue has been identified and we are working to resolve it.

Our requests to multiple Shopify API endpoints are failing with 404 errors. There is an outage reported on the Shopify status page - https://my.shopifystatus.com/ Next Expected Update: 1 hour

We are continuing to work on a fix for this issue.

Update from Shopify: "We've identified the problem and are seeing recovery from our mitigation efforts. We will continue to monitor and update." We are seeing that Shopify connector syncs are now recovering. Next Expected Update: 3 hours

This incident has been resolved. We have observed that instance rates have returned to normal levels, and affected connections are syncing successfully. Incident Summary Description: We identified an issue where Shopify connections were failing with an HTTP 404 Not Found error. Timeline: The issue began on 2026-06-03 at 13:10 UTC and was resolved on 2026-06-03 at 15:00 UTC. Cause: The failures were caused by an issue on Shopify's side, which resulted in unexpected API error responses. For more information, please refer to the Shopify Status Page: https://www.shopifystatus.com/incidents/gbqcx5fk01gz Resolution: No action was required from our side. The issue was resolved by Shopify, and affected syncs recovered automatically once the upstream issue was addressed.

The Fivetran Hybrid Deployment Agent is experiencing an issue that may cause syncs to fail to start or connections to fail during setup tests and syncs. The error in the agent logs is "Return CreateJobResponse/Failure, Caused By User: false - CREATE_JOB_ERROR/Connection pool shut down {process_id=XXX}"

We have identified the root cause and have deployed a hot fix.

The hot fix should be reflected in the new HD agent images. For existing HD agents, restarting the controller should resolve the issue. Customers are advised to restart their controller with the following commands: cd ~/fivetran ./hdagent.sh stop ./hdagent.sh start

A fix has been implemented and we are monitoring the results.

This incident has been resolved.