Is Fivetran Down?

This incident has been resolved. We have observed that error rates have returned to normal levels, and all affected Ramp connections are syncing successfully. <b>Incident Summary</b> 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. --- [2026-07-10T20:38:20.885Z] (monitoring) The source API is now returning HTTP 200 responses with the expected data instead of HTTP 529 errors, and affected connections have started recovering. --- [2026-07-10T19:38:04.695Z] (identified) 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. <b>Next Expected Update: 1 hour</b> --- [2026-07-10T19:10:10.028Z] (identified) The issue has been identified and we are working to resolve it.

This incident has been resolved. We have observed that error rates have returned to normal levels, and all affected connectors are syncing successfully. <b>Incident Summary</b> 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. --- [2026-07-07T19:07:31.460Z] (monitoring) 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. <b>Next Expected Update: 1 Hour </b> --- [2026-07-07T17:40:43.999Z] (identified) 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. <b>Next Expected Update:</b> 1 hour --- [2026-07-07T17:20:10.796Z] (identified) The issue has been identified and we are working to resolve it.

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 --- [2026-07-07T00:50:12.307Z] (monitoring) We have applied a fix. Affected connectors should resume syncing normally. We are monitoring recovery across all affected accounts. --- [2026-07-06T23:45:09.907Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-07-07T00:49:49.891Z] (identified) We have identified an issue with the AppLovin connector in which syncs are failing with HTTP 500 Internal Server Error responses. 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. --- [2026-07-06T23:05:09.080Z] (identified) The issue has been identified and we are working to resolve it.