Fivetran Outage History

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.

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.

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.

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.

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.

This incident has been resolved. We observed a short delay in sending Webhook Events, and the events are now being delivered as expected post the fix. Description: We identified an issue where there was a gap in the delivery of Webhook Sender events for around 40 minutes. Timeline: The issue began on March 9, 2026, at 15:23 UTC and was resolved at 16:07 UTC. Cause: The issue was caused due to a scheduled maintenance of the Webhook Sender Service completed on Mar 7th 2026. Resolution: A fix was deployed as part of the post-maintenance action items, and the issue is now resolved.

This incident has been resolved. We observed connector sync success rates returning to normal levels, and HubSpot connector syncs are now running as expected. Incident Summary: Description: We identified an issue where HubSpot connector syncs were failing with the error: Endpoint [marketing_email] encountered an exception: "The requested resource does not exist." Timeline: The issue began on March 5, 2026, at 10:30 AM UTC and was resolved at 12:10 PM UTC. Cause: The issue was caused by a third-party outage on HubSpot's infrastructure. HubSpot status page: https://status.hubspot.com/incidents/9szm40l2fq2s Resolution: HubSpot identified and resolved the issue on their end. No changes were required on our side.

This incident has been resolved. We have observed that instance rates are returning to normal levels and affected models are syncing successfully. Incident Summary Description: We identified an issue for DBT and Quickstart Transformation which resulted in models failing with below error. Error : ValueError: Proto enum SubmitSQLResultType has values not defined in Python enum SubmitSQLResultType: ['GET_MODIFICATION_INFO']. All proto enum values must have corresponding Python enum members Timeline: This issue began on 5th March, 10:02 AM UTC and was resolved on 5th March, 11:22 AM UTC. Cause: A recently released dbt image introduced a compatibility issue with a dependent internal service, which led to service disruption. Resolution: We have rolled back the affected images to the previous stable version to restore services.

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 Hubspot connections, which resulted in syncs failing with the following error: "Failed to sync 1 endpoint(s) with error: {email_campaign=java.lang.NullPointerException: Cannot invoke <>" Timeline: This issue began on 2026-03-03 at 18:00 UTC and was resolved on 2026-02-25 at 22:00 UTC. Cause: This was determined to be caused by a change in connector sync behavior. Resolution: The changes to the sync strategy have been reverted and connections are now syncing successfully.

This incident has been resolved. We have observed that the setup tests are successful. Incident Summary Description: We identified an issue for the Partner Built Destinations and Connections where the setup is failing with the "Operation timeout" error. Timeline: This issue began on March 3rd 2026, at 10 AM UTC and was resolved on March 3rd 2026, at 2:30 PM UTC. Cause: Recent changes to the setup workflow caused the issue. Resolution: The changes have been reverted to ensure the setup is successful.