3rd Party: X Ads and X Organic Performance Degradation

Update timeline

1. identified May 13, 2026, 06:41 PM UTC

   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.

2. identified May 14, 2026, 03:37 PM UTC

   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.

3. identified May 14, 2026, 10:20 PM UTC

   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

4. identified May 18, 2026, 04:41 PM UTC

   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 20th

5. identified May 21, 2026, 04:48 PM UTC

   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.

6. identified May 24, 2026, 03:43 AM UTC

   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

7. identified May 26, 2026, 11:14 PM UTC

   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

8. identified May 28, 2026, 10:52 PM UTC

   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.

9. identified May 30, 2026, 07:00 PM UTC

   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

10. identified Jun 03, 2026, 10:35 PM UTC

    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

11. identified Jun 05, 2026, 09:01 PM UTC

    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

12. identified Jun 09, 2026, 12:26 AM UTC

    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

13. identified Jun 10, 2026, 10:42 PM UTC

    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

14. identified Jun 12, 2026, 06:26 PM UTC

    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

15. identified Jun 15, 2026, 10:25 PM UTC

    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

16. identified Jun 17, 2026, 04:02 PM UTC

    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

17. identified Jun 19, 2026, 10:29 PM UTC

    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

18. identified Jun 23, 2026, 07:02 PM UTC

    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. Next update will be on Wednesday, June 24th.

19. identified Jun 24, 2026, 07:04 PM UTC

    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. Next update will be by or before June 26th.

20. resolved Jun 26, 2026, 07:18 PM UTC

    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.