Fivetran: Teleport-Based Connections failing with the Encryption key issue
Incident
Report for Fivetran
Resolved
All connectors have now recovered from the initial error condition. If you have a Postgres connector that is continuing to fail, please open a support ticket so we can investigate further.
Update
We are continuing to see connectors recover. Monitoring is ongoing to ensure all failing connectors recover successfully.
Update
We are continuing to see a steady increase in recovery and we are still monitoring syncs and completion rates.
Update
We are seeing a steady increase in recovery and we are still monitoring syncs and completion rates.
Update
We observed that the connections are still recovering. We will continue to monitor sync performance and completion rates until full restoration.
Update
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.
Update
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.
Update
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.
Update
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.
Update
We are continuing to work on a fix for this issue.
Identified
The issue has been identified and we are working to resolve it.
This incident affected: Database connectors (PostgreSQL).