Monitoring - We have deployed a fix that resolves authentication errors for the majority of affected Salesforce sources.
For most users: reconnecting your Salesforce data source through the Funnel UI will restore access and resume data collection. We recommend doing this if your source is currently showing "No Access."
For a subset of users: we are aware that the reconnection flow is not completing successfully in some cases. We have identified this as a separate issue and are actively working to resolve it. No action is required from affected users at this time, we will provide an update as soon as a resolution is in place.
We continue to monitor all Salesforce connections closely.
May 15, 2026 - 17:30 CEST
For most users: reconnecting your Salesforce data source through the Funnel UI will restore access and resume data collection. We recommend doing this if your source is currently showing "No Access."
For a subset of users: we are aware that the reconnection flow is not completing successfully in some cases. We have identified this as a separate issue and are actively working to resolve it. No action is required from affected users at this time, we will provide an update as soon as a resolution is in place.
We continue to monitor all Salesforce connections closely.
May 15, 2026 - 17:30 CEST
Investigating - Due to mandatory security updates required by Salesforce, we recently enabled stricter token security controls across our Salesforce connectors (Marketing Cloud not affected)
We are seeing an increased number of Salesforce sources reporting authentication errors ("No Access"). This is caused by existing refresh tokens being invalidated as part of the Salesforce security rollout. Affected sources need to be reconnected to generate a new valid token.
We are also currently investigating issues with the reconnection flow that may prevent some users from completing the reconnect. We are working to unblock this with highest priority.
May 12, 2026 - 20:25 CEST
We are seeing an increased number of Salesforce sources reporting authentication errors ("No Access"). This is caused by existing refresh tokens being invalidated as part of the Salesforce security rollout. Affected sources need to be reconnected to generate a new valid token.
We are also currently investigating issues with the reconnection flow that may prevent some users from completing the reconnect. We are working to unblock this with highest priority.
May 12, 2026 - 20:25 CEST
Update - We are continuing to monitor the ongoing issue affecting X Ads and X Organic data sources. This remains a top priority for our team. The root cause lies on X’s side and we are in ongoing contact with them. We do not have any new updates to share at this time, but will post here as soon as we do.
We appreciate your patience and understanding on the matter and will share updates with you here as soon as we have more information to share.
May 13, 2026 - 18:38 CEST
We appreciate your patience and understanding on the matter and will share updates with you here as soon as we have more information to share.
May 13, 2026 - 18:38 CEST
Update - We are still working on this issue, and can see some issues being corrected on the X APIs. However, we are still unable to get all breakdowns needed to provide correct data for reporting. We have unblocked the sources to see what combination of settings have incorrect data.
This means that some data sources might look like they are working. But they show up with no data. We are investigating if which combinations are truly no data and which ones are due to X returning no data incorrectly.
We are actively working together with X to sort this out.
May 07, 2026 - 15:54 CEST
This means that some data sources might look like they are working. But they show up with no data. We are investigating if which combinations are truly no data and which ones are due to X returning no data incorrectly.
We are actively working together with X to sort this out.
May 07, 2026 - 15:54 CEST
Update - 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.
Apr 30, 2026 - 15:31 CEST
Apr 30, 2026 - 15:31 CEST
Update - 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.
Apr 27, 2026 - 15:42 CEST
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.
Apr 27, 2026 - 15:42 CEST
Update - 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
Apr 22, 2026 - 14:57 CEST
Apr 22, 2026 - 14:57 CEST
Update - 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.
Apr 19, 2026 - 23:29 CEST
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.
Apr 19, 2026 - 23:29 CEST
Update - 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.
Apr 17, 2026 - 17:34 CEST
Apr 17, 2026 - 17:34 CEST
Update - 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.
Apr 16, 2026 - 19:06 CEST
Apr 16, 2026 - 19:06 CEST
Update - We are continuing to work on a fix for this issue.
Apr 13, 2026 - 15:06 CEST
Apr 13, 2026 - 15:06 CEST
Identified - 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
Apr 11, 2026 - 13:33 CEST
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
Apr 11, 2026 - 13:33 CEST
Identified - After discussion with X, the discrepancies are due to a major overhaul of the X adstack between the period of 3.14 through 3.31.
Still investigating when and if the reporting will be back to normal
Apr 07, 2026 - 19:55 CEST
Still investigating when and if the reporting will be back to normal
Apr 07, 2026 - 19:55 CEST
Update - We have made progress in our investigation into the data issues affecting X Ads sources.
We have identified two separate issues contributing to the disruption, both not only limited to Funnel but confirmed across the broader X Ads API ecosystem:
Intermittent errors when retrieving campaign data. This caused some downloads to fail entirely. Based on our monitoring, this issue has largely subsided.
Incomplete or missing metrics for certain ad configurations, some X Ads sources are returning incomplete data for metrics such as impressions, clicks, and cost. This issue appears to still be ongoing and is not limited to Funnel.
We are continuing to monitor both issues closely. Sources affected by the first issue has successfully been resolved.
For the second issue, we are tracking the situation and will trigger re-syncs once complete data is available.
We understand this impacts your reporting and continue to treat this with the highest priority.
Apr 03, 2026 - 17:02 CEST
We have identified two separate issues contributing to the disruption, both not only limited to Funnel but confirmed across the broader X Ads API ecosystem:
Intermittent errors when retrieving campaign data. This caused some downloads to fail entirely. Based on our monitoring, this issue has largely subsided.
Incomplete or missing metrics for certain ad configurations, some X Ads sources are returning incomplete data for metrics such as impressions, clicks, and cost. This issue appears to still be ongoing and is not limited to Funnel.
We are continuing to monitor both issues closely. Sources affected by the first issue has successfully been resolved.
For the second issue, we are tracking the situation and will trigger re-syncs once complete data is available.
We understand this impacts your reporting and continue to treat this with the highest priority.
Apr 03, 2026 - 17:02 CEST
Investigating - We're aware of an issue where some customers are not seeing data after 2026-03-26 for their X Ads sources. We're currently investigating the cause.
Apr 01, 2026 - 11:41 CEST
Apr 01, 2026 - 11:41 CEST
About This Site
This is the status page for Funnel. It is used for announcing technical issues and posting updates as issues are diagnosed and resolved.
It was put in place in November 2019, which means you will not find information about prior issues.
Funnel
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance