Fivetran Outage History

Fivetran experienced a minor incident where some Spotify Ads connections were failing with "unknown failure" errors. The issue affected the Spotify Ads connector component and lasted approximately 1.2 hours. The problem was identified and Fivetran was actively working on a resolution.

Fivetran's HubSpot connector syncs were intermittently failing with "The requested resource does not exist" errors due to a third-party outage on HubSpot's infrastructure that affected certain API services. The issue lasted 1.4 hours from 10:30 AM to 12:10 PM UTC on March 5, 2026, impacting HubSpot data synchronization operations. HubSpot resolved the outage on their end, and Fivetran confirmed that connector sync success rates returned to normal levels without requiring any changes to their systems.

Fivetran's DBT and Quickstart Transformation models failed for 2 hours due to a ValueError related to Proto enum compatibility issues between a recently released dbt image and an internal service. The incident was resolved by rolling back the affected images to the previous stable version, restoring normal sync functionality.

HubSpot connections in Fivetran experienced sync failures for 3.9 hours due to a NullPointerException error in the email_campaign endpoint, caused by recent changes to the connector's sync behavior. The issue was resolved by reverting the problematic sync strategy changes, restoring normal syncing functionality for affected connectors.

Fivetran experienced a 2.7-hour outage where Partner Built Destinations and Connections setup was failing with "Operation timeout" errors, affecting Destinations, Convex, PlanetScale, and Tracksuit components. The issue was caused by recent changes to the setup workflow, which were identified and reverted through a hotfix deployment. The incident was resolved when setup tests began completing successfully.

Fivetran's Box connections experienced failures due to HTTP "429 Too Many Requests" errors caused by an incident on Box's platform. The issue affected Box data synchronization for 3.7 hours until Box resolved their underlying incident. Fivetran monitored the recovery as connections automatically resumed normal operation once Box's services were restored.