Fivetran Status

Identified: 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

Identified: 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

Identified: 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

Identified: 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.

Identified: 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

Identified: 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

Identified: 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.

Identified: 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

Identified: 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

Identified: 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.

Identified: 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.

Resolved: This incident has been resolved. We have observed that instance rates have returned to normal levels, and affected connections are syncing successfully.

Incident Summary

Description: We identified an issue where Shopify connections were failing with an HTTP 404 Not Found error.

Timeline: The issue began on 2026-06-03 at 13:10 UTC and was resolved on 2026-06-03 at 15:00 UTC.

Cause: The failures were caused by an issue on Shopify's side, which resulted in unexpected API error responses. For more information, please refer to the Shopify Status Page: https://www.shopifystatus.com/incidents/gbqcx5fk01gz

Resolution: No action was required from our side. The issue was resolved by Shopify, and affected syncs recovered automatically once the upstream issue was addressed.

Monitoring: Update from Shopify: "We've identified the problem and are seeing recovery from our mitigation efforts. We will continue to monitor and update."

We are seeing that Shopify connector syncs are now recovering.

Next Expected Update: 3 hours

Identified: We are preparing a fix to skip the failing endpoints until Shopify resolves the issue.

Next Expected Update: 1 hour

Identified: Our requests to multiple Shopify API endpoints are failing with 404 errors.

There is an outage reported on the Shopify status page - https://my.shopifystatus.com/

Next Expected Update: 1 hour

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