Is Fivetran down?

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

We have identified that the source API is repeatedly returning HTTP 529 responses, causing sync failures. We are actively working with the third-party source to resolve the issue and will continue to provide updates. Next Expected Update: 1 hour

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

This incident has been resolved. We have observed that error rates have returned to normal levels, and all affected Ramp connections are syncing successfully. Incident Summary Description: We identified an issue affecting Ramp connections that caused sync failures due to repeated HTTP 529 responses from the source API. Timeline: The issue began on 2026-07-10 at 16:50 UTC and was resolved on 2026-07-10 at 19:30 UTC. Cause: The source API was repeatedly returning HTTP 529 responses across multiple endpoints, resulting in sync failures. Resolution: No action was required from our side. The issue was resolved by the source, and affected connections recovered automatically once the source API resumed returning successful responses.

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

We have identified that the issue occurs when querying the CreditCardPaymentTxn entity. The source API is returning the following error: "invalid context declaration: creditcardpaymenttxn" This appears to be happening because the source may have changed the entity name from CreditCardPaymentTxn to CreditCardPayment. Our team is working on accommodating this change. Next Expected Update: 1 hour

We have deployed a fix for this issue by switching to the new entity for data retrieval for the table CreditCardPayment We will continue to closely monitor all affected connections until they have fully recovered and returned to normal sync operations. Next Expected Update: 1 Hour

This incident has been resolved. We have observed that error rates have returned to normal levels, and all affected connectors are syncing successfully. Incident Summary Description: We identified an issue affecting QuickBooks connections that caused syncs to fail for the CreditCardPaymentTxn entity. Timeline: The issue began on 2026-07-07 at 2:00 PM UTC and was resolved on 2026-07-07 at 7:10 PM UTC. Cause: The QuickBooks query entity was changed from CreditCardPaymentTxn to CreditCardPayment, causing API requests made by the connector to fail with a 400 ValidationFault. Resolution: We made the required changes for the connector to use the new CreditCardPayment query entity. After deploying this change, the affected connectors recovered successfully, and syncs resumed normal operation.

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

We have identified an issue with the AppLovin connector where syncs for the advertiser_report table are failing with HTTP 500 Internal Server Errors. This is caused by a query timeout on AppLovin's backend — the expanded column set being requested exceeds AppLovin's server-side query execution limit. We are actively working on a fix and will provide further updates.

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

We have applied a fix that resolves the 500 internal server error for the advertiser_report table. Affected connectors should resume syncing normally. We are monitoring recovery across all affected accounts.

This incident has been resolved. We have observed that instance rates are returning to normal levels, and affected connections are syncing successfully. Incident Summary Description: We have identified an issue with the AppLovin connector where syncs are failing with HTTP 500 Internal Server Error. Timeline: The issue began on July 6, 2026, at 8:30 PM UTC and was resolved on July 6, 2026, at 10:00 PM UTC. Cause: The failures were caused by a backend issue on AppLovin’s side, resulting in API requests timing out or returning HTTP 500 errors. Some syncs were also impacted by increased query complexity due to an expanded set of requested fields, which exceeded AppLovin’s server-side query execution limits. Resolution: AppLovin resolved the backend issue on their end, after which connections using the /skaReport endpoint began syncing successfully again. We rolled back the expanded column set for affected customers. This mitigation reduced query complexity and allowed impacted connections to resume syncing successfully

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

We have identified that this issue was caused by a recent change, and we are currently working on reverting the changes via a hotfix. Next Expected Update: 2 hours

A hotfix has been deployed, and the syncs are recovering. We will continue monitoring the syncs Next Expected Update: 3 hours

This incident has been resolved. We have observed that instance rates are returning to normal levels, and affected connections are syncing successfully. Incident Summary Description: We identified an issue in which Apple Search Ads connections were failing with the error "HTTP 400 Bad Request." Timeline: This issue began on June 18, 2026, at 17:47 UTC and was resolved on June 19, 2026, at 11:02 UTC. Cause: The issue was caused by a recent code change that introduced an unexpected error in Apple Search Ads connection processing. Resolution: Identified the problematic change and reverted it Following the change, affected Apple Search Ads connections resumed normal operation and the issue was fully resolved.

We have identified an issue where Hybrid Deployment Connections are failing with a "Failed to generate data key for HD encryption context" or "Failed to receive message length" exception. We are currently investigating in more detail. Next Expected Update:

We have identified that this issue was caused by a recent change, and we are currently working on a HotFix. Next Expected Update: 1 hour

We are continuing to work on a fix for this issue. Next Expected Update: 1 hour

We have deployed a fix for this issue. We will continue to monitor all affected connectors until they resume their normal sync functionality. Next Expected Update: 3 hours

Incident Summary Description: We identified an issue where Hybrid Deployment connections were failing with a "Failed to generate data key for HD encryption context" or "Failed to receive message length" exception. Timeline: This issue began on June 17, 2026, at 08:10 UTC and was resolved on June 17, 2026, at 15:50 UTC. Cause: A recent code change introduced an issue affecting Hybrid Deployment connectors, specifically Oracle HVA and SQL Server HVA connectors. As a result, sync jobs for impacted connectors would start and then fail. Resolution: We reverted the problematic change and deployed a hotfix. After the fix was deployed, affected connectors began recovering and syncs started succeeding again.