Fivetran Outage History

Started Mar 21, 2026, 05:58 AM UTC· resolved Mar 21, 2026, 05:58 AM UTC

1. resolved Mar 21, 2026, 05:58 AM UTC

   Description: We identified an issue for Hubspot which resulted in syncs failing due to increased API rate limiting. Timeline: This issue began on 20th March, 2026 at 20:45 UTC and was resolved on 20th March, 2026 at 23:00 UTC. Cause: A recent update intended to improve how our connection manages HubSpot authentication led to an unintended increase in how frequently access tokens were refreshed. This resulted in a higher number of authentication requests than expected, which triggered HubSpot’s rate limits and caused some syncs to fail. Resolution: We rolled back the change, which immediately resolved the issue. Syncs are now succeeding normally.

Read the full incident report →

Started Mar 20, 2026, 07:30 PM UTC· resolved Mar 20, 2026, 10:40 PM UTC

1. identified Mar 20, 2026, 07:30 PM UTC

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

2. monitoring Mar 20, 2026, 07:40 PM UTC

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

3. resolved Mar 20, 2026, 10:40 PM UTC

   We have resolved this incident.

Read the full incident report →

Started Mar 18, 2026, 02:30 PM UTC· resolved Mar 18, 2026, 02:30 PM UTC

1. resolved Mar 18, 2026, 06:00 PM UTC

   Incident Summary Description: A few Amazon S3 connections experienced intermittent failures due to an AWS-side issue, with the error: "Unable to execute HTTP request." Timeline: The issue began on March 18, 2026, at 10:30 UTC and was resolved by 13:40 UTC. Root Cause: The intermittent sync failures were caused by AWS-side timeout issues. Resolution: The issue was automatically resolved once connectivity from the AWS side was restored.

Read the full incident report →

Started Mar 18, 2026, 05:50 AM UTC· resolved Mar 18, 2026, 06:49 AM UTC

1. identified Mar 18, 2026, 05:50 AM UTC

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

2. monitoring Mar 18, 2026, 06:13 AM UTC

   We experienced an intermittent issue with a third-party API service that resulted in 500 errors. Connections are now recovering, and we are continuing to closely monitor sync performance.

3. resolved Mar 18, 2026, 06:49 AM UTC

   This incident has been resolved. We observed that Snapchat Ads connection sync success rates have returned to normal levels, and syncs are now running as expected. Description: We identified an issue where Snapchat Ads connections started failing with error "500 Internal Server Error" Timeline: The issue began on March 18, 2026, at 04:03 UTC and was resolved on March 18th, 2026, at 05:01 UTC. Cause: The issue was caused by an intermittent issue with a third-party API service that resulted in 500 errors. Resolution: No changes were required on our side. The issue was automatically resolved on the third-party side, and syncs are back to normal.

Read the full incident report →

Started Mar 17, 2026, 06:00 PM UTC· resolved Mar 17, 2026, 06:00 PM UTC

1. resolved Mar 17, 2026, 06:18 PM UTC

   This incident has been resolved. We observed that HubSpot connector sync success rates have returned to normal levels, and syncs are now running as expected. Description: We identified an issue where some HubSpot connector syncs were failing with the error: "Unknown failure." Timeline: The issue began on March 17, 2026, at 17:10 UTC and was resolved at 17:26 UTC. Cause: The issue was caused by timeouts while attempting to reach HubSpot's OAuth endpoint. Resolution: No changes were required on our side. The issue was automatically resolved once connectivity to HubSpot's OAuth endpoint was restored.

Read the full incident report →

Started Mar 16, 2026, 11:21 PM UTC· resolved Mar 16, 2026, 11:21 PM UTC

1. resolved Mar 16, 2026, 11:23 PM UTC

   Description We identified an issue with our public REST API that caused API calls to fail with a "column api.disabled_at does not exist" exception. Timeline: This issue began on 22:15 UTC on March 16, 2026 and was resolved on 22:50 UTC on March 16, 2026. Cause: A migration change caused the issue. Resolution: A fix was implemented to address the migration issue, after which instance rates and all implementations of the Fivetran public REST API returned to normal.

Read the full incident report →

Started Mar 15, 2026, 07:35 AM UTC· resolved Mar 15, 2026, 12:12 PM UTC

1. identified Mar 15, 2026, 07:35 AM UTC

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

2. identified Mar 15, 2026, 09:00 AM UTC

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

3. monitoring Mar 15, 2026, 09:56 AM UTC

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

4. resolved Mar 15, 2026, 12:12 PM UTC

   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.

Read the full incident report →

Started Mar 14, 2026, 10:55 PM UTC· resolved Mar 15, 2026, 05:01 AM UTC

1. identified Mar 14, 2026, 10:55 PM UTC

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

2. identified Mar 14, 2026, 11:12 PM UTC

   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.

3. monitoring Mar 14, 2026, 11:22 PM UTC

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

4. resolved Mar 15, 2026, 05:01 AM UTC

   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

Read the full incident report →

Started Mar 14, 2026, 09:00 AM UTC· resolved Mar 14, 2026, 12:11 PM UTC

1. identified Mar 14, 2026, 09:00 AM UTC

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

2. identified Mar 14, 2026, 10:15 AM UTC

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

3. monitoring Mar 14, 2026, 10:45 AM UTC

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

4. resolved Mar 14, 2026, 12:11 PM UTC

   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.

Read the full incident report →

Started Mar 12, 2026, 07:35 PM UTC· resolved Mar 12, 2026, 09:31 PM UTC

1. identified Mar 12, 2026, 07:35 PM UTC

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

2. monitoring Mar 12, 2026, 09:10 PM UTC

   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.

3. resolved Mar 12, 2026, 09:31 PM UTC

   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.

Read the full incident report →

Started Mar 11, 2026, 09:25 PM UTC· resolved Mar 12, 2026, 03:31 AM UTC

1. identified Mar 11, 2026, 09:25 PM UTC

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

2. identified Mar 11, 2026, 09:28 PM UTC

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

3. monitoring Mar 12, 2026, 02:56 AM UTC

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

4. resolved Mar 12, 2026, 03:31 AM UTC

   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.

Read the full incident report →

Started Mar 11, 2026, 05:15 AM UTC· resolved Mar 11, 2026, 09:41 AM UTC

1. identified Mar 11, 2026, 05:15 AM UTC

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

2. identified Mar 11, 2026, 05:50 AM UTC

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

3. identified Mar 11, 2026, 05:51 AM UTC

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

4. identified Mar 11, 2026, 07:43 AM UTC

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

5. monitoring Mar 11, 2026, 09:13 AM UTC

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

6. resolved Mar 11, 2026, 09:41 AM UTC

   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.

Read the full incident report →

Started Mar 10, 2026, 10:23 PM UTC· resolved Mar 10, 2026, 10:23 PM UTC

1. resolved Mar 10, 2026, 10:23 PM UTC

   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.

Read the full incident report →

Started Mar 10, 2026, 06:25 PM UTC· resolved Mar 10, 2026, 10:01 PM UTC

1. identified Mar 10, 2026, 06:25 PM UTC

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

2. identified Mar 10, 2026, 08:15 PM UTC

   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.

3. resolved Mar 10, 2026, 10:01 PM UTC

   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.

Read the full incident report →

Started Mar 09, 2026, 10:00 AM UTC· resolved Mar 09, 2026, 10:00 AM UTC

1. resolved Mar 09, 2026, 04:51 PM UTC

   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.

Read the full incident report →

Started Mar 05, 2026, 12:50 PM UTC· resolved Mar 05, 2026, 01:29 PM UTC

1. identified Mar 05, 2026, 12:10 PM UTC

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

2. identified Mar 05, 2026, 12:31 PM UTC

   The issue has been identified as a HubSpot outage that caused temporary unavailability of certain API services. As a result, affected connections experienced intermittent sync failures. HubSpot has implemented a fix, and services are currently recovering. For additional details, please refer to the HubSpot Status Page: https://status.hubspot.com/incidents/9szm40l2fq2s

3. monitoring Mar 05, 2026, 12:50 PM UTC

   HubSpot has resolved the issue, and we are currently monitoring the results to ensure sync operations continue to run as expected.

4. resolved Mar 05, 2026, 01:29 PM UTC

   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.

Read the full incident report →

Started Mar 05, 2026, 11:05 AM UTC· resolved Mar 05, 2026, 01:04 PM UTC

1. identified Mar 05, 2026, 11:05 AM UTC

   We have identified that the models are failing with the 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.

2. monitoring Mar 05, 2026, 11:33 AM UTC

   A fix has been Implemented and we are monitoring the results on our end.

3. resolved Mar 05, 2026, 01:04 PM UTC

   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.

Read the full incident report →

Started Mar 03, 2026, 06:25 PM UTC· resolved Mar 03, 2026, 10:20 PM UTC

1. identified Mar 03, 2026, 06:25 PM UTC

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

2. identified Mar 03, 2026, 07:52 PM UTC

   We have identified the root cause of the issue: recent changes to the HubSpot connector introduced a NullPointerException in the email_campaign object, resulting in sync failures, and we are actively working on a hotfix to resolve it.

3. monitoring Mar 03, 2026, 10:05 PM UTC

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

4. resolved Mar 03, 2026, 10:20 PM UTC

   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.

Read the full incident report →

Started Mar 03, 2026, 12:10 PM UTC· resolved Mar 03, 2026, 02:50 PM UTC

1. identified Mar 03, 2026, 12:10 PM UTC

   We identified an issue for the Partner Built Destinations and Connections where the setup is failing with the "Operation timeout" error.

2. identified Mar 03, 2026, 12:41 PM UTC

   Recent changes to the setup workflow caused the issue. A hotfix is being deployed to resolve the issue.

3. monitoring Mar 03, 2026, 02:09 PM UTC

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

4. resolved Mar 03, 2026, 02:50 PM UTC

   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.

Read the full incident report →

Started Mar 02, 2026, 06:20 AM UTC· resolved Mar 02, 2026, 06:20 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Feb 25, 2026, 06:22 AM UTC· resolved Feb 25, 2026, 06:22 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →