All Systems Operational
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
Past Incidents
Jan 17, 2026
No incidents reported today.
Jan 16, 2026
Resolved -
We have received information from TikTok's team that this was an intended but unannounced change in their API.
We have now updated our connector accordingly, and affected data sources will soon start receiving data again. As the report types in question cannot be backfilled, this incident will unfortunately result in a data gap of 2-3 days for affected data sources. We apologize for any inconvenience this may cause.
Jan 16, 13:55 CET
We have now updated our connector accordingly, and affected data sources will soon start receiving data again. As the report types in question cannot be backfilled, this incident will unfortunately result in a data gap of 2-3 days for affected data sources. We apologize for any inconvenience this may cause.
Jan 16, 13:55 CET
Investigating -
We have observed that a small subset of data sources (about 80 in total) using the TikTok Organic connector are struggling to retrieve new data from the TikTok Organic API. There does not appear to be any distinct common denominator among the affected data sources, aside from that they are configured to retrieve "Video Insights" or "Video Insights Daily Activity" reports.
We have reached out to TikTok's support team for further investigation, and have received word back that the issue has been forwarded to their developers.
Jan 15, 10:36 CET
We have reached out to TikTok's support team for further investigation, and have received word back that the issue has been forwarded to their developers.
Jan 15, 10:36 CET
Resolved -
Snapchat have confirmed that the aforementioned new API behavior has been rolled back, and is unlikely to return without prior warning. This issue is now resolved.
Jan 16, 10:01 CET
Jan 16, 10:01 CET
Monitoring -
Snapchat seem to have rolled back the changes on their side. Data sources previously affected by this problem are now managing to download new data successfully.
We are waiting to receive confirmation from Snapchat on what actions they have taken, and which adjustments (if any) we should make to our connector to ensure this issue does not happen again. We will continue to monitor the connector closely until we hear back from Snapchat.
Jan 15, 10:22 CET
We are waiting to receive confirmation from Snapchat on what actions they have taken, and which adjustments (if any) we should make to our connector to ensure this issue does not happen again. We will continue to monitor the connector closely until we hear back from Snapchat.
Jan 15, 10:22 CET
Identified -
We are in talks with a representative from Snapchat on how to proceed in this case. Additionally, we have received more specifics on the issue itself, namely that metrics related to Subscriptions are incompatible with the Country dimension.
Previously, this incompatibility would simply return a metric value of 0 for affected metrics, however this behavior has now been altered to raise an error instead, resulting in the issue we are trying to resolve here.
We are now looking into updating our integration to exclude Subscription-related metrics when a data source has been configured to use Country as its dimension to accommodate this new API behavior.
Jan 14, 17:08 CET
Previously, this incompatibility would simply return a metric value of 0 for affected metrics, however this behavior has now been altered to raise an error instead, resulting in the issue we are trying to resolve here.
We are now looking into updating our integration to exclude Subscription-related metrics when a data source has been configured to use Country as its dimension to accommodate this new API behavior.
Jan 14, 17:08 CET
Investigating -
We have observed that many Snapchat data sources are currently experiencing issues with importing new data. This appears to relate to a particular metric, conversion_subscribe (or "Subscriptions"), that the Snapchat API has suddenly started treating as incompatible when included in our requests.
We have reached out to Snapchat's developer support to get insights on what the problem is. Should the issue continue to persist, we will consider temporarily removing the metric in question in order to get affected data sources up and running again.
Jan 14, 10:52 CET
We have reached out to Snapchat's developer support to get insights on what the problem is. Should the issue continue to persist, we will consider temporarily removing the metric in question in order to get affected data sources up and running again.
Jan 14, 10:52 CET
Jan 15, 2026
Jan 14, 2026
Resolved -
This incident has been resolved.
Jan 14, 14:41 CET
Jan 14, 14:41 CET
Update -
We have just released a new report: Daily Metrics | Per video. This report estimates daily values from the lifetime values returned by LinkedIn. Because the daily values are estimated from the change in the lifetime values, these reports will start taking data from the day they are connected, but it is not possible to fetch historical data with these reports.
We previously released Daily Metrics | Per update.
We also previously released reports Lifetime Metrics | Per video and Lifetime Metrics | Per update, allowing for users to pull lifetime values for all sources affected by this incident, in line with the new expected behavior for this LinkedIn API.
We have now released all new reports we expect to release in line with this incident.
If you need daily or other time-sliced breakdowns for historical data we recommend that you reach out to LinkedIn directly to request support for daily or other time-sliced breakdowns for these report types in the API. We have also reached out to LinkedIn to request the time-sliced breakdowns, but you are able to provide additional motivation for this feature request. For example, LinkedIn has asked us if lack of support for time-sliced breakdowns will affect your planned AdSpend in LinkedIn, in order to better prioritize the feature request.
Dec 30, 15:11 CET
We previously released Daily Metrics | Per update.
We also previously released reports Lifetime Metrics | Per video and Lifetime Metrics | Per update, allowing for users to pull lifetime values for all sources affected by this incident, in line with the new expected behavior for this LinkedIn API.
We have now released all new reports we expect to release in line with this incident.
If you need daily or other time-sliced breakdowns for historical data we recommend that you reach out to LinkedIn directly to request support for daily or other time-sliced breakdowns for these report types in the API. We have also reached out to LinkedIn to request the time-sliced breakdowns, but you are able to provide additional motivation for this feature request. For example, LinkedIn has asked us if lack of support for time-sliced breakdowns will affect your planned AdSpend in LinkedIn, in order to better prioritize the feature request.
Dec 30, 15:11 CET
Update -
We have just released a new report: Daily Metrics | Per update. This report estimates daily values from the lifetime values returned by LinkedIn. Because the daily values are estimated from the change in the lifetime values, these reports will start taking data from the day they are connected, but it is not possible to fetch historical data with these reports.
We are also working on a report to estimate daily values for Per video.
We will update you again once it is live.
We previously released reports Lifetime Metrics | Per video and Lifetime Metrics | Per update, allowing for users to pull lifetime values for all sources affected by this incident, in line with the new expected behavior for this LinkedIn API.
We still recommend that customers reach out to LinkedIn directly to request support for daily or other time-sliced breakdowns for these report types in the API. We have also reached out to LinkedIn to request the time-sliced breakdowns, but you are able to provide additional motivation for this feature request. For example, LinkedIn has asked us if lack of support for time-sliced breakdowns will affect your planned AdSpend in LinkedIn, in order to better prioritize the feature request.
Dec 29, 16:01 CET
We are also working on a report to estimate daily values for Per video.
We will update you again once it is live.
We previously released reports Lifetime Metrics | Per video and Lifetime Metrics | Per update, allowing for users to pull lifetime values for all sources affected by this incident, in line with the new expected behavior for this LinkedIn API.
We still recommend that customers reach out to LinkedIn directly to request support for daily or other time-sliced breakdowns for these report types in the API. We have also reached out to LinkedIn to request the time-sliced breakdowns, but you are able to provide additional motivation for this feature request. For example, LinkedIn has asked us if lack of support for time-sliced breakdowns will affect your planned AdSpend in LinkedIn, in order to better prioritize the feature request.
Dec 29, 16:01 CET
Monitoring -
We have just released a new report: Lifetime Metrics | Per video.
With the previously released report Lifetime Metrics | Per update, there is now a way to pull lifetime values for all sources affected by this incident, in line with the new expected behavior for this LinkedIn API.
We are also working on rolling out reports that will estimate daily values from the lifetime values returned by LinkedIn.
We will update you again once they are live.
We still recommend that customers reach out to LinkedIn directly to request support for daily or other time-sliced breakdowns for these report types in the API. We have also reached out to LinkedIn to request the time-sliced breakdowns, but you are able to provide additional motivation for this feature request. For example, LinkedIn has asked us if lack of support for time-sliced breakdowns will affect your planned AdSpend in LinkedIn, in order to better prioritize the feature request.
Dec 23, 13:01 CET
With the previously released report Lifetime Metrics | Per update, there is now a way to pull lifetime values for all sources affected by this incident, in line with the new expected behavior for this LinkedIn API.
We are also working on rolling out reports that will estimate daily values from the lifetime values returned by LinkedIn.
We will update you again once they are live.
We still recommend that customers reach out to LinkedIn directly to request support for daily or other time-sliced breakdowns for these report types in the API. We have also reached out to LinkedIn to request the time-sliced breakdowns, but you are able to provide additional motivation for this feature request. For example, LinkedIn has asked us if lack of support for time-sliced breakdowns will affect your planned AdSpend in LinkedIn, in order to better prioritize the feature request.
Dec 23, 13:01 CET
Update -
We are currently working on a new Lifetime report for Video Metrics in line with the new expected behavior for this LinkedIn API. We are expecting to release the new Lifetime report for Video Metrics tomorrow.
We are also working on rolling out reports that will estimate daily values from the lifetime values returned by LinkedIn.
We will update you again once they are live.
Last Friday we released the new report: Lifetime Metrics | Per update.
We still recommend that customers reach out to LinkedIn directly to request support for daily or other time-sliced breakdowns for these report types in the API. We have also reached out to LinkedIn to request the time-sliced breakdowns, but you are able to provide additional motivation for this feature request. For example, LinkedIn has asked us if lack of support for time-sliced breakdowns will affect your planned AdSpend in LinkedIn, in order to better prioritize the feature request.
Dec 22, 17:16 CET
We are also working on rolling out reports that will estimate daily values from the lifetime values returned by LinkedIn.
We will update you again once they are live.
Last Friday we released the new report: Lifetime Metrics | Per update.
We still recommend that customers reach out to LinkedIn directly to request support for daily or other time-sliced breakdowns for these report types in the API. We have also reached out to LinkedIn to request the time-sliced breakdowns, but you are able to provide additional motivation for this feature request. For example, LinkedIn has asked us if lack of support for time-sliced breakdowns will affect your planned AdSpend in LinkedIn, in order to better prioritize the feature request.
Dec 22, 17:16 CET
Update -
We have just released a new report: Lifetime Metrics | Per update. We are currently working on rolling out another new Lifetime report for Video Metrics in line with the new expected behavior for this LinkedIn API.
We are also working on rolling out reports to estimate daily values from the lifetime values returned by LinkedIn.
We will update you again once they are live.
We still recommend that customers reach out to LinkedIn directly to request support for daily or other time-sliced breakdowns for these report types in the API. We have also reached out to LinkedIn to request the time-sliced breakdowns, but you are able to provide additional motivation for this feature request. For example, LinkedIn has asked us if lack of support for time-sliced breakdowns will affect your planned AdSpend in LinkedIn, in order to better prioritize the feature request.
Dec 19, 17:10 CET
We are also working on rolling out reports to estimate daily values from the lifetime values returned by LinkedIn.
We will update you again once they are live.
We still recommend that customers reach out to LinkedIn directly to request support for daily or other time-sliced breakdowns for these report types in the API. We have also reached out to LinkedIn to request the time-sliced breakdowns, but you are able to provide additional motivation for this feature request. For example, LinkedIn has asked us if lack of support for time-sliced breakdowns will affect your planned AdSpend in LinkedIn, in order to better prioritize the feature request.
Dec 19, 17:10 CET
Update -
We are currently working on rolling out new reports in line with the new expected behavior for this LinkedIn API. We will update you again once they are live.
We still recommend that customers reach out to LinkedIn directly to request support for daily or other time-sliced breakdowns for these report types in the API. We have also reached out to LinkedIn to request the time-sliced breakdowns, but you are able to provide additional motivation for this feature request. For example, LinkedIn has asked us if lack of support for time-sliced breakdowns will affect your planned AdSpend in LinkedIn, in order to better prioritize the feature request.
Dec 17, 17:22 CET
We still recommend that customers reach out to LinkedIn directly to request support for daily or other time-sliced breakdowns for these report types in the API. We have also reached out to LinkedIn to request the time-sliced breakdowns, but you are able to provide additional motivation for this feature request. For example, LinkedIn has asked us if lack of support for time-sliced breakdowns will affect your planned AdSpend in LinkedIn, in order to better prioritize the feature request.
Dec 17, 17:22 CET
Update -
We have deprecated the affected report types, since the LinkedIn API no longer returns historically consistent data for these requests.
We recommend that customers reach out to LinkedIn directly to request support for daily or other time-sliced breakdowns for these report types in the API. We have also reached out to LinkedIn to request the time-sliced breakdowns, but you are able to provide additional motivation for this feature request by sharing with LinkedIn the use cases you have been using these daily breakdowns for in your processes.
Dec 15, 16:16 CET
We recommend that customers reach out to LinkedIn directly to request support for daily or other time-sliced breakdowns for these report types in the API. We have also reached out to LinkedIn to request the time-sliced breakdowns, but you are able to provide additional motivation for this feature request by sharing with LinkedIn the use cases you have been using these daily breakdowns for in your processes.
Dec 15, 16:16 CET
Identified -
LinkedIn has updated our issue report to say they have removed the functionality for receiving daily reports from this endpoint.
Dec 15, 09:52 CET
Dec 15, 09:52 CET
Update -
We are still awaiting updates from LinkedIn, and have sent out a request for a status update on their investigation.
We have removed the Totals breakdown for the Update Metrics report from the scope after further investigation - that breakdown is working as expected, and has not been affected by the issue reported here.
Dec 11, 12:22 CET
We have removed the Totals breakdown for the Update Metrics report from the scope after further investigation - that breakdown is working as expected, and has not been affected by the issue reported here.
Dec 11, 12:22 CET
Update -
We are continuing to await updates from LinkedIn, and as we have continued to look into this issue we have noticed similar behavior in the Totals breakdown for the Update Metrics report, so we have expanded the scope here.
Dec 10, 18:20 CET
Dec 10, 18:20 CET
Update -
LinkedIn replied that they are actively debugging this issue to find the root cause and expect to send us more in depth updates in the next day or two. We will let you know once we receive additional updates.
Dec 8, 17:17 CET
Dec 8, 17:17 CET
Update -
LinkedIn has responded to our ticket that this issue has not been previously reported. We have sent them more detailed debugging information to assist with root cause analysis. We will update you when we have heard back with further information.
Dec 5, 16:26 CET
Dec 5, 16:26 CET
Investigating -
We are currently investigating an error affecting the Video Metrics report for the LinkedIn Organic connector as well as Update Metrics reports which use the Per Update breakdown.
Requests to fetch data for these reports to the LinkedIn Marketing API appear to have started returning lifetime values where previously they were returning daily values, which results in large mismatches, as those daily values get summed by Funnel to show you the total values of interactions with your posts and videos over the periods you specify.
We have filed a bug report with LinkedIn and will let you know when we hear back.
Dec 4, 17:14 CET
Requests to fetch data for these reports to the LinkedIn Marketing API appear to have started returning lifetime values where previously they were returning daily values, which results in large mismatches, as those daily values get summed by Funnel to show you the total values of interactions with your posts and videos over the periods you specify.
We have filed a bug report with LinkedIn and will let you know when we hear back.
Dec 4, 17:14 CET
Jan 13, 2026
Resolved -
Error rates have stabilized. We now consider this issue resolved.
Jan 13, 15:27 CET
Jan 13, 15:27 CET
Monitoring -
Most data sources that were previously affected by this issue appear to have self-healed over the weekend. However, as we are still seeing intermittent stalled reports in some cases, we will continue to monitor the situation for a while before considering this incident resolved.
Jan 12, 10:19 CET
Jan 12, 10:19 CET
Investigating -
We have observed an increase in errors for data sources connected to our The Trade Desk connector. The reports we generate through their API appear to stall indefinitely, resulting in delays.
We have reached out to The Trade Desk for further investigation.
Jan 9, 13:04 CET
We have reached out to The Trade Desk for further investigation.
Jan 9, 13:04 CET
Jan 12, 2026
Jan 11, 2026
No incidents reported.
Jan 10, 2026
No incidents reported.
Jan 9, 2026
Jan 8, 2026
No incidents reported.
Jan 7, 2026
No incidents reported.
Jan 6, 2026
No incidents reported.
Jan 5, 2026
No incidents reported.
Jan 4, 2026
No incidents reported.
Jan 3, 2026
No incidents reported.