Fivetran Status

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 that caused delays in connection syncs and transformations. During this time, new syncs in AWS and Azure were delayed, while ongoing syncs continued to run normally. In the GCP regions, ongoing syncs failed, and new syncs were delayed.

Timeline: This issue began on March 15, 2026, at 6:20 UTC and was resolved on March 15, 2026, at 11 UTC.

Cause: A recent infrastructure change caused the issue.

Resolution: A fix was implemented to address the infrastructure issue, after which instance rates returned to normal, and affected connectors resumed syncing successfully.

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

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

Identified: We have identified an issue where multiple connection syncs and transformations are delayed.

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 for Qualtrics which resulted in syncs failing with HTTP Error Code 429.

Timeline: This issue began on 10th March at around 10PM UTC and was resolved on 14th March at 10:30PM UTC.

Cause: This issues was caused by Third party 429s for distribution History endpoint which started spiking after 10th March at around 10PM UTC, we suspect if qualtrics had enforced additional rate limits at an app level in addition to the brand level api limit of 300 per minute

Resolution: We increased the retries and also added exponential sleep between api calls to reduce the load on qualtrics server

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

Identified: We identified an issue where the Distribution Contact endpoint was retrying requests too frequently, which caused some syncs to fail with rate limit errors (429).

A hotfix has been raised to adjust the retry behavior so that retries are spaced out more effectively. We will continue to monitor the syncs after deployment.

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

Resolved: This incident has been resolved, and we have observed that the sync is now completing successfully.

Incident Summary Description: We have identified an issue where some HubSpot connector syncs are failing with the error

Failed to sync 1 endpoint(s) with error: {CAPTURE_DELETES_USING_WEBHOOKS=com.fivetran.platform.interfaces.security.credentials.RefreshCredentialsException: HTTP 477 }

Timeline: The issue began on March 14, 2026, at 09:01 UTC and was resolved on March 14, 2026, at 10:43 UTC.

Cause: The recent migration of the Fivetran public app by HubSpot has caused the issue.

Resolution: A fix has been implemented to resolve the issue.

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

Identified: Recent migration of the Fivetran public app by HubSpot has caused the issue. A hotfix is being deployed to resolve the issue.

Identified: We identified an issue with the HubSpot Connections where the syncs are failing with an HTTP 477 RefreshCredentials error.

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 on the Fivetran Connection Status page that caused Sync Events not to display correctly in the event log.

Timeline: This issue began on March 12th at 18:14:00 UTC and was resolved on March 12th at 21:30:00 UTC.

Cause: The issue was caused by a recent code change that allowed malformed messages to be accepted by our backend service. These malformed messages could not be processed, resulting in a backlog of properly formatted messages.

Resolution: We deployed a hotfix to handle the malformed messages. Once those malformed messages were handled properly, the backlog of correctly formed messages began to be processed, and UI events recovered.

Monitoring: We have deployed a fix for this issue: We created a hotfix to handle malformed messages which were preventing normal messages from processing

We will continue to monitor all affected sync events until we are caught up and the Connection Status page is back to normal.

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

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 for PostgreSQL connectors which resulted in schema fetch failing with a "Fetch source columns failed" error. Users were unable to expand tables or edit column configs in the Schema tab. The issue also impacted Terraform users, who experienced HTTP 400 errors when attempting to retrieve schema columns.

Timeline: The issue began on March 11, 2026 at 01:48 UTC and was fully resolved on March 12, 2026 at 02:48 UTC.

Cause: The issue was caused by a recent code change made to the connector.

Resolution: Engineering identified the root cause and reverted the recent changes. After deploying the revert and a hotfix, the connectors resumed normal operation.

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

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.

Resolved: This incident has now been resolved. We have confirmed that the affected connectors are running successfully and operating as expected.

Incident Summary

Description: We identified an issue where MySQL connectors using Teleport were failing with the error: “Some tables failed to sync.”

Timeline: The issue began on March 11, 2026 at 01:00 UTC and was fully resolved on March 11, 2026 at 09:15 UTC.

Cause: The issue was caused by a recent code change made to the connector.

Resolution: Engineering identified the root cause and reverted the recent changes. After deploying the revert and a hotfix, the connectors resumed normal operation.

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

Identified: We have identified the root cause of the issue and are actively working on a hotfix to resolve it.

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

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.

Resolved: This incident has been resolved. We observed STripe connector sync success rates returning to normal levels, and syncs are now running as expected.

Description: We identified an issue where some Stripe connector syncs were failing with the error: "Transaction fee report: HTTP 404 Not Found"

Timeline: The issue began on March 10, 2026, at 19:00 UTC and was resolved at 21:07 UTC.

Cause: The issue was caused by file downloads returning 404 errors.

Resolution: No changes were required on our side. The issue was resolved automatically once access to file downloads was restored.

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 impacting Criteo connections, which resulted in syncs failing with the following error: "Failed to upsert additional attributes for creative"

Timeline: This issue began on 2026-03-10 at 15:15 UTC and was resolved on 2026-03-10 at 21:12 UTC.

Cause:

The issue occurred when the source returned "unknown" attribute types for certain creatives, resulting in sync failures.

Resolution:

A fix has been implemented to skip the problematic attribute types.

Identified: Connector syncs are currently failing due to an unknown creative type format returned by the source API. Our team is actively working on a hotfix to treat this as a warning instead of causing sync failures.

We will share another update once the fix has been deployed.

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

Resolved: This incident has been resolved. We have observed that destination setup tests are now running successfully and operating as expected.

Incident Summary

Description: We identified an issue impacting destination setup tests, causing them to fail across regions.

Timeline: This issue began on 2026-03-10 at 02:40 UTC and was resolved on 2026-03-10 at 19:20 UTC.

Cause: The issue was caused by a faulty pull request related to a new feature, which introduced changes to the token registration process used for setup test jobs.

Resolution: Engineering identified the root cause and reverted the recent changes to restore the original token registration model. Following the revert and hotfix deployment, destination setup tests resumed functioning normally.

Monitoring: A fix has been implemented, and we are currently monitoring the results.

Identified: We have identified the root cause of the issue and are actively working on a hotfix to resolve it.

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.