Fivetran Status Page

Jul 10, 2026 · resolved Jul 10

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.

Jul 7, 2026 · resolved Jul 7

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.

Jul 6, 2026 · resolved Jul 7

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

May 13, 2026 · resolved Jun 26

X has confirmed that the root cause originates within their API environment and they are actively working towards complete resolution.  While the fix must be implemented on their side, Fivetran continues to actively work with X until all known issues are resolved.  Affected Fivetran customers have been contacted.  Fivetran will continue to send direct communications to affected customers as we have additional information, including once X reaches full resolution.

Jun 19, 2026 · resolved Jun 19

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.

Is Fivetran down right now?

No — Fivetran is up. All systems operational as of Jul 13, 11:42 PM UTC.

What is Fivetran's current status?

Fivetran: All Systems Operational. Alert24 checks Fivetran's status page continuously and can notify you the moment it changes.

How do I get alerted when Fivetran goes down?

Alert24 monitors Fivetran and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.