Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
We’re still holding the X connectors in blocked state until reporting data is verified end-to-end. The time zone alignment issue and server errors are unchanged since our last update. We’re actively following up with X and will post the next update by [today + 4 days], or sooner if anything material changes.
We continue to hold the X (Twitter) Ads connector in a blocked state while we verify reporting data end-to-end.
In addition to the time zone alignment issue we described previously (which X is working to correct), we are now also seeing intermittent server errors from the reporting paths we use, including responses that fail when requesting certain breakdowns of the data. We are in contact with X to confirm whether this is related to the ongoing corrections to reporting.
We will not enable the connector for general use until we are confident the data in Funnel is complete and correct for your reports. The next update will be posted by 2 days once we have more from X, or sooner if the situation changes materially.
We’ve identified an issue in how X’s API returns data in relation to time zones, which can affect how performance metrics line up to dates in your reports. We’re working with X, who have acknowledged the issue and are working on a correction. We’re keeping the X connector in a blocked state until we’ve verified that the data we receive matches what we expect for accurate reporting. We expect to share a further update by the end of the week
We have made further progress with X on restoring downloads, but we are still validating that the data fully matches your reporting periods and is safe to rely on. Until that is confirmed, we are not writing new data for the affected X Ads and X Organic configurations, so we do not replace existing correct figures with values that may be misaligned.
X has confirmed they are treating the underlying platform issues as a high priority. We remain in close contact with them and will post the next update when we can either confirm reliable delivery or share a clearer timeline.
In collaboration with X we now got a bit further in finding ways to get the X Ads and X organic connectors up and working. However we are still validating if the workaround produces valid data, and can be scaled. The focus is currently on getting X ads working first, and X organic secondly.
During conversation with X dev team, the issues are known and they are working on it with highest prio. However, no ETA when it can be solved.
We are continuing to work on a fix for this issue.
We have identified an issue where X endpoints we are using for specific reports are not returning data.
Our hypothesis is that this is due to the major update on X Ad platform.
Sources with the issue:
X Ads
- All configuration except Campaign Non-Agg
X Organic
- Tweet Activity (User insights is working)
The issue has been reported by multiple other vendors.
The issues started 2026-04-10.
We are working on findings ways around the issue.
See also related Status page X Ads - Missing data since 26 March https://status.funnel.io/incidents/dsyj3s7hzrzf
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with