Fivetran Status

Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. The next update will be on Monday, June 22, 2026

Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. The next update will be on Friday, June 19, 2026

Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. The next update will be on Wednesday, June 17, 2026

Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. The next update will be on Monday, June 15, 2026

Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. The next update will be on Friday, June 12, 2026

X Corp has assured us that Segmentation data will soon be fixed for AGE, GENDER, PLATFORM, and METROS(DMA). We will continue to provide updates as soon as new information becomes available. Next Expected Update: Wednesday, June 10th, 2026

Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. The next update will be on Monday, June 8, 2026

All reports have recovered, except for ORGANIC_TWEET_REPORT. Following a call with X Corp, we understand that they are working on a fix on their end. X Corp has assured us that Segmentation data after April 5th will soon be fixed for AGE, GENDER, PLATFORM, and METROS(DMA). X Corp has confirmed that they are still investigating the reported 500 and 503 exceptions, but do not have an update for us at this time. We will continue to provide updates as soon as new information becomes available. Next Expected Update: Friday, June 5th, 2026

We are starting to see some improvements for jobs with null values in the segment field. We are closely monitoring the situation. We will continue to provide updates as soon as new information becomes available. Next Expected Update: Tuesday, June 2, 2026

Our team continues to actively work with X to address all known issues. We will continue to provide updates as soon as new information becomes available. The next update will be on Saturday, May 30th.

Our team continues to work with X to address all known issues. We have recently followed up with them regarding their progress. We are closely monitoring the situation. We will continue to provide updates as soon as new information becomes available. Next Expected Update: Thursday, May 28, 2026

Our team continues to work with X to address all known issues. We are closely monitoring the situation. We will continue to provide updates as soon as new information becomes available. Next Expected Update: Tuesday, May 26, 2026

The HTTP 500 Internal Server Errors across both the X Ads and X Organic connectors have been resolved. Reports without segmentation are syncing successfully with cursors advancing as expected. We continue to see data integrity issues with segmented tables. The API returns job results indicating that the `segment` field is null for some entities, causing those records to be dropped during upsert because `segment` is part of the primary key. This has been reported to X Corp along with multiple examples. We are continuing to actively work with X Corp toward a resolution Next Expected Update: Saturday, May 23rd.

We are working to identify possible workarounds. In the meantime, we are continuing to communicate with the X team. We will continue to provide updates as soon as new information becomes available. Next expected update: Thursday, May 21th

Our team continues to work with X to address all known issues. We are closely monitoring the situation. We will continue to provide updates as soon as new information becomes available. Next Expected Update: Monday, May 18, 2026

We are continuing to observe HTTP 500 Internal Server Errors across both the X Ads and X Organic connectors. As a result, data ingestion for those endpoints is currently being skipped to avoid further processing failures. You will notice an alert on your dashboard for the same. However, we are no longer receiving empty reports for most report types. This issue currently persists only for ORGANIC_TWEET_REPORT. We are actively working with the X support team to resolve the remaining API issues. If you have started seeing the latest data in your reports tables and no longer see the "Stats Report Server Error" alert on your dashboard, you may perform a full resync to backfill any missing historical data.

X's async reporting API has been intermittently returning empty or zero-value data and experiencing a higher rate of Internal Server errors since approximately April 9, 2026. This affects all report tables in the Twitter Ads and Twitter Organic connectors. We have reported this issue to X Corp and are actively working with them toward a resolution.

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.

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

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

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

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.

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

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

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

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. <b>Next Expected Update: 1 hour</b>

This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully. <b>Incident Summary</b> Description: We identified an issue for Customer.io, which resulted in syncs failing with a 502 HTTP error. Timeline: This issue began on 2026-06-13 20:26 UTC and was resolved on 2026-06-14 14:52 UTC. Cause: The issue was caused by intermittent upstream API failures on the Customer.io side. The root-cause behaviour fluctuated throughout the incident, shifting between generic server errors across multiple endpoints. Resolution: Fivetran implemented a skip-on-failure mechanism to bypass 502 HTTP errors and allow syncs to proceed. A permanent root-cause fix will be deployed by Customer.io.

We observed a shift in the issue behavior around 12:00 UTC for the Customer export api. While initial failures occurred during job creation, the connector is now failing during the report download phase. - We have implemented a skip mechanism to mitigate these 502 errors on the affected endpoints, and are continuing to closely monitor all active syncs. - Additionally, we reported the ongoing behavior to Customer.io, as their initial fix did not resolve the issue. We are currently awaiting their response. <b>Next Expected Update:</b> < 3 hours >

We noticed that the connections were failing again with "502 Server Error". We've raised a hotfix, and the failures are gradually reducing. We're monitoring the affected connections. <b>Next Expected Update:</b> < 3 hours >

We are continuing to monitor all affected connectors after the recent fix deployment. <b>Next Expected Update:3 hours </b> <3 hours = P2, 2 hours = P1>

A hotfix has been deployed to skip the failing endpoints until the source resolves the issue. We will continue monitoring the connections while we wait for a response from the source team. <b>Next Expected Update: 3 hours</b> <3 hours = P2, 2 hours = P1>

We are preparing a fix to skip the failing endpoints until the source resolves the issue. <b>Next Expected Update: 1 hour</b> <1 hour = P2, 30 minutes = P1>

We identified that multiple REST API requests are failing with 502 Bad Gateway errors returned by the source API. We have reached out to the source regarding this. <b>Next Expected Update: 1 hour</b> <1 hour = P2, 30 minutes = P1>

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

This incident has been resolved. We have observed that instance rates have returned to normal levels and affected connectors are syncing successfully. <b>Incident Summary</b> Description: We identified an issue for Facebook Pages which resulted in syncs failing with an <b>An unknown error has occurred</b> error while fetching monetization metrics. Timeline: This issue began on 2026-05-15 at 16:30 UTC and was resolved on 2026-05-16 at 17:55 UTC. Cause: An added monetization metrics path in Facebook Pages was unstable and occasionally failed when Facebook returned a transient error, which caused syncs to fail. Resolution: We disabled monetization metrics processing for Facebook Pages connector, which stopped the failing requests and allowed affected connectors to recover.

We disabled monetization metrics processing for Facebook Pages and have not noticed any new failures. We will continue to monitor all affected connectors until they resume their normal sync functionality.

We have identified that this issue was caused by instability in newly introduced Facebook Pages monetization metrics and we are currently working on a fix.

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

Description: We identified an issue affecting manual and API-triggered connection syncs, causing syncs to fail to start and return API errors. Timeline: This issue began on June 8, 2026, at 22:00 UTC and was resolved on June 8, 2026, at 22:35 UTC. Cause: The elevated API error count was caused by an incident with a third-party service used to orchestrate sync execution. As a result, requests to trigger connection syncs through both the API and the Fivetran dashboard were intermittently unsuccessful. Reference: https://status.temporal.io/incidents/8msytm7vpfbv Resolution: The third-party service provider resolved the underlying issue, restoring normal functionality. Following confirmation that sync triggering was operating as expected, the incident was closed. Customers can now successfully trigger syncs through both the API and the dashboard.