Service disruption: X Organic April 10, 2026

Update timeline

1. investigating Apr 10, 2026, 08:33 AM UTC

   We are currently investigating a performance degradation within the X Organic connector that began on April 10 at 00:00 AM UTC. This issue is specifically impacting the "Tweet engagements" report type. You may encounter the following error message: “Query failed: Could not process the query. Please try again later.” Our engineering team is actively working on exploring potential workarounds to restore full functionality, but initial investigation indicates the error is stemming from X’s API. We will provide further updates as soon as more information becomes available. Thank you for your patience while we resolve this.

2. identified Apr 10, 2026, 11:49 AM UTC

   Our engineering team has confirmed that the current service degradation originates from X’s API, as suggested by our initial findings. While we are actively exploring potential workarounds to mitigate the impact, the primary resolution requires action from X’s development team. We are monitoring the situation closely and will provide immediate updates should the performance stabilize or if a viable internal solution is identified. We appreciate your continued patience as we address this issue.

3. identified Apr 14, 2026, 10:58 AM UTC

   We are writing to share an update regarding recent changes in X’s API behavior that may be affecting your experience. Some users are currently receiving a 'no data' notification when running queries via our X Organic connector. This is a deviation from previously reported errors and is due to a change in the API’s response behaviour. After a thorough investigation, we have identified that the root cause is stemming from X’s API. While we are working diligently to advocate for a swift resolution with their team, the final fix must be implemented on their end. We have escalated the issue to the team on X’s side and are awaiting action from their side and we will of course update you as soon as we know more. Thank you for your continued patience and understanding as we address this issue.

4. identified Apr 21, 2026, 10:56 AM UTC

   We are writing to provide an update on the ongoing technical issue. We have been in consistent contact with the team at X, and they have confirmed that the root cause originates within their API environment. While the fix must be implemented on their end and are actively working on it, we are still tracking the situation closely and monitoring our systems for any changes in behaviour. We are committed to keeping you informed and will provide an update the moment new information becomes available. Thank you for your continued patience!