Fivetran Status

Resolved: This incident has been resolved. We have observed that sync and re-sync actions are working as expected and no additional warnings have been found.

Incident Summary Description: Manual sync or re-sync requests via the Dashboard or API returned an error. The following error is returned by the Dashboard: "Failed to update integration. If this continues to occur, please contact support."

Timeline: The incident began on 2025-10-10 at 18:16 UTC and was resolved on 2025-10-10 at 21:36 UTC.

Cause: Scheduling configuration was stored in unexpected format, this caused a failure when manual sync operation tried to identify whether the connector has dependent transformations.

Resolution: A hotfix was deployed to cover additional cases of the scheduling configuration format.

Monitoring: The hotfix is now live, and manual syncs/re-syncs through the Dashboard and API are working as expected.

We are continuing to monitor all affected connectors after the recent fix deployment.

Monitoring: We have deployed a hotfix for this issue: Integrated scheduling is not outputting expected results, causing downstream queries which manual sync/re-sync operations depend on to fail.

Once the hotfix has gone live, we will continue to monitor all affected connectors until they resume their normal sync functionality.

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

Identified: Beginning at 18:16 UTC, manual sync or re-sync requests via the Dashboard or API started to return an error.

The following error is returned by the Dashboard: "Failed to update integration. If this continues to occur, please contact support."

The following error is returned by the API: "[SQL State: 22023] ERROR: cannot extract elements from a scalar"

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: Following a release to a shared component, several database connectors — including Oracle, SQL Server HVA, LogMiner, and Teleport-based connections — failed with the error "Failed to get or decrypt encryption key from file header." This affected sync and re-sync operations across multiple accounts.This was not a security incident and no data exposure or unauthorized access occurred.

Timeline: This issue began on 2025-11-06 23:04 UTC and was resolved on 2025-11-11 00:24 UTC.

Cause: A code change to a central component introduced an incompatible encryption mechanism, preventing connectors from decrypting existing data. We rolled back to a previous version; however, we identified incompatibilities between services that led to connections running with an increased sync frequency, overloading our systems.

Resolution: The issue was mitigated through Reverting the affected release and Scaling necessary infrastructure to restore stability.

Monitoring: We are continuing to see connectors recover. Monitoring is ongoing to ensure all failing connectors recover successfully.

Monitoring: We are continuing to see a steady increase in recovery and we are still monitoring syncs and completion rates.

Monitoring: We are seeing a steady increase in recovery and we are still monitoring syncs and completion rates.

Monitoring: We observed that the connections are still recovering. We will continue to monitor sync performance and completion rates until full restoration.

Monitoring: We are continuing to observe syncs recovering and will actively monitor sync performance and completion rates. We will provide the next update in the next hour.

Monitoring: We have observed that syncs are starting to get recovered successfully. We are continuing to closely monitor sync performance and completion rates and will update in the next hour.

Monitoring: We have identified and deployed a fix for the issue, and we expect affected connectors to recover automatically. Our team is closely monitoring the sync performance and will provide a further update in 30 minutes.

Monitoring: A fix has been implemented, We are monitoring syncs recovering and will provide another update in 30 minutes.

Identified: We are continuing to investigate the issue affecting Teleport-based PostgreSQL and Snowflake connections, and we are closely monitoring.

Identified: All connections except Teleport-based PostgreSQL and Snowflake have now recovered. We are actively investigating the issue affecting Teleport-based PostgreSQL connections and continue to monitor.

Monitoring: The system has been rolled back to a previously built version, and error rates are improving. We continue to closely monitor performance and stability.

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

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

Monitoring: Connector performance has stabilised, and the issue has been resolved.

We are continuing to monitor the system to ensure ongoing stability. Our team is working on an RCA, which will be shared once complete.

Identified: We are continuing to investigate an issue causing connector failures across multiple database connector types. The system has now been rolled back to a previously stable build, and it has significantly reduced the number of connector failures.

We are actively monitoring the system to ensure stability. Additional mitigation steps will be taken as necessary

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

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