Update - We are continuing to monitor this issue and escalate the issue with our Meta contacts. The issue is continuing to behave non-deterministically: affecting different sources each day.
There is a general pattern with more sources affected on Mondays than on Fridays, which was the opposite when the total rate was higher, indicating that at least one, but not all, of several incipient factors may have been mitigated by Meta.

Aug 27, 2025 - 12:18 CEST
Update - Today we saw a halving again of the rate of affected sources, putting the rate at less than one in every 10,000 sources. We are continuing to monitor this issue and escalate the issue with our Meta contacts. The issue is continuing to behave non-deterministically: affecting different sources each day.
Aug 15, 2025 - 19:07 CEST
Update - This week the number of affected sources has been relatively stable at the rate observed at the end of last week: about half the rate seen previous weeks.

Previous weeks we have also seen less sources affected on Mondays than on other weekdays, but that was not true this week. This indicates that a periodic effect has been resolved, while we are still seeing at least one other, non-periodic, effect that is responsible for the residual (and that when the incident began we were observing the combined effects).

Aug 14, 2025 - 16:29 CEST
Update - Update: Today half as many sources were affected as were the previous two days. We are continuing to monitor for further improvements.
Aug 07, 2025 - 16:12 CEST
Update - We have received additional confirmation on our support ticket with Meta that they are actively investigating the sustained rise in errors we have been seeing since July 17th.

Following the pattern we observed last week, this Monday morning half as many sources were affected. Tuesday morning we observed around the same rate as we observed most of last week. This is a behavior pattern consistent with a load dependent error pathway.

Aug 05, 2025 - 17:11 CEST
Update - We have escalated this issue with internal stakeholders at Meta in addition to regular support, to expedite remediation. Today we have less than half as many sources experiencing issues as last Friday, and last weekend many of those sources were able to receive at least partial updates, perhaps due to lower total load on Meta systems over the weekends.

We understand that many of you are putting together end of month reporting, and this has been a disruption to your processes. We are continuing to experiment to see if there are any additional mitigations we can apply from our side, while also continuing to make our normal requests to the Meta servers for updated data.

Aug 01, 2025 - 17:03 CEST
Update - Update: Less than one in ten thousand sources have been persistently affected by this issue. The other sources affected by this issue (around one in every thousand) have been affected intermittently, experiencing some data updates, but not as many as usual.

We are continuing to request data for all affected sources, but the Facebook Ads API is not returning the data reliably. We are actively collaborating with Meta's support team, providing detailed debug logs and source examples to assist in their investigation.

Of the sources affected on Friday, more than 85% have returned to normal operations, and the total number of delayed sources has been reduced over 30%.

Jul 30, 2025 - 11:43 CEST
Update - Meta has responded to our ticket, requesting additional information to aid in debugging the issue from their side.
Jul 29, 2025 - 10:16 CEST
Update - We implemented several mitigations on Friday, and today 76% of the affected sources have returned to normal operations. We are still investigating further mitigations to remediate the remaining affected sources. We filed a bug with Meta on Friday to better understand the API behavior change, but Meta has not yet responded.
Jul 28, 2025 - 12:03 CEST
Investigating - Starting on July 17th, we noticed an issue affecting less than one in every thousand Facebook Ads sources. The issue results in failed data pulls.

These sort of data pull issues usually resolve on their own within one to two days, however this issue has persisted for over a week. The issue is intermittent, with some sources downloading data for one data pull and not the next.

Greater than 85% of the affected sources have been able to update data in the last two days, and greater than 95% of the affected sources have been able to pull updated data in the last three days, however these updates are not as reliable or consistent as usual for the affected sources, so affected sources are experiencing delays.

We are currently investigating the cause of the issue, but have so far not been able to find any unique traits shared by only the affected data sources, nor differences in our environment between the runs which succeed compared to those which fail for the affected sources to point to the source of the non-deterministic behavior.

Jul 25, 2025 - 14:54 CEST
Identified - We are currently experiencing an issue with the Shopping24 connector. Due to an API version change on the platform side, data has not been updating since 12 August 2025.

Our team is actively working on a rebuild of the connector to restore data downloads. Since the connector is declarative, we expect the rebuild to take less time than usual, and we will provide updates here as soon as more information is available.

Thank you for your patience and understanding.

Aug 26, 2025 - 14:51 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
Aug 31, 2025

No incidents reported today.

Aug 30, 2025

No incidents reported.

Aug 29, 2025

No incidents reported.

Aug 28, 2025

No incidents reported.

Aug 27, 2025
Resolved - All affected sources have returned to normal operations.
Aug 27, 12:14 CEST
Monitoring - Some users may be experiencing delays with data downloads for Google Ads sources.

A fix has been deployed, and we are monitoring the situation as the systems return to normal.
We apologize for any inconvenience this may have caused.

Aug 26, 11:59 CEST
Aug 26, 2025

Unresolved incident: Shopping24 connector outage.

Aug 25, 2025

No incidents reported.

Aug 24, 2025

No incidents reported.

Aug 23, 2025

No incidents reported.

Aug 22, 2025

No incidents reported.

Aug 21, 2025

No incidents reported.

Aug 20, 2025
Resolved - All systems have now recovered.
Aug 20, 15:39 CEST
Monitoring - Funnel queries started failing after buggy code was deployed at around 14:30 CEST, the deploy has been reverted and we are currently waiting for systems to recover.
Aug 20, 15:02 CEST
Aug 19, 2025
Resolved - This incident has been resolved.
Aug 19, 11:29 CEST
Update - We are no longer seeing any new Facebook Ads Data Sources affected by the token errors that originated from recent changes on Meta’s side.

A small number of sources (several dozen) are still unable to download data due to the token error. To restore these, users will need to reconnect the affected sources directly in the Funnel app, as this is the only available resolution.

With that, the incident is considered resolved. Thank you for your patience and understanding while we worked through this issue.

Aug 19, 11:29 CEST
Update - We have taken all possible steps on our side to reconnect the Facebook Ads Data Sources affected by the recent token errors originating from Meta’s side. The issue is now largely resolved. However, a handful of Data Sources in the EU and a few dozen in the US are still unable to download data due to these token errors.

To restore them, affected users will need to reconnect their sources.

Aug 18, 16:01 CEST
Monitoring - Most Facebook Ads sources have now fully recovered. A very small number of sources in the US remain affected, which can be resolved by reconnecting the credentials. No customers outside the US are impacted.

The incident appears to have originated from an interruption on Meta’s side, which likely triggered false token/login errors and temporarily blocked sources from running in Funnel. While Meta has not confirmed details, the timing strongly suggests a link to their earlier service disruption.

We continue to monitor closely and support customers still experiencing issues.

Aug 16, 12:48 CEST
Identified - Since 14 August 2025, we have seen some Facebook Ads data sources fail with the error “You cannot access the app till you log in to www.facebook.com and follow the instructions given”. This issue stems from a change on Meta’s side that requires certain accounts to re-login, even when tokens remain valid. As a result, affected sources stop importing data.

We are doing all we can to mitigate the impact for our customers and are proactively addressing the issue caused by Meta’s change. Our engineering team is bulk-triggering download jobs for all affected sources to restore imports, staggering these runs to avoid exceeding Meta’s API limits.

Backfills are temporarily paused to prioritise ongoing data imports. Around 20% of sources have been processed so far, and we will continue until all are complete.

Aug 15, 12:01 CEST
Aug 18, 2025
Aug 17, 2025

No incidents reported.