Funnel Outage History

Started Jan 15, 2026, 09:36 AM UTC· resolved Jan 16, 2026, 12:55 PM UTC

1. investigating Jan 15, 2026, 09:36 AM UTC

   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.

2. resolved Jan 16, 2026, 12:55 PM UTC

   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.

Read the full incident report →

Started Jan 14, 2026, 09:52 AM UTC· resolved Jan 16, 2026, 09:01 AM UTC

1. investigating Jan 14, 2026, 09:52 AM UTC

   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.

2. identified Jan 14, 2026, 04:08 PM UTC

   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.

3. monitoring Jan 15, 2026, 09:22 AM UTC

   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.

4. resolved Jan 16, 2026, 09:01 AM UTC

   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.

Read the full incident report →

Started Jan 09, 2026, 12:04 PM UTC· resolved Jan 13, 2026, 02:27 PM UTC

1. investigating Jan 09, 2026, 12:04 PM UTC

   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.

2. monitoring Jan 12, 2026, 09:19 AM UTC

   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.

3. resolved Jan 13, 2026, 02:27 PM UTC

   Error rates have stabilized. We now consider this issue resolved.

Read the full incident report →

Started Dec 05, 2025, 09:21 AM UTC· resolved Dec 11, 2025, 03:04 PM UTC

1. investigating Dec 05, 2025, 09:21 AM UTC

   We are currently observing elevated error rates for our Facebook Pages connector, resulting in delayed imports for most data sources. Our developers are investigating the issue.

2. identified Dec 05, 2025, 10:12 AM UTC

   We have identified that the metric "Total Video View Time (in MS)", known as "page_video_view_time" in the Page Insights API, is currently causing API requests to fail when included. As a temporary measure, we have removed this metric from our requests in order to get affected data sources up and running again. Additionally, we have reported this issue to Meta. Once the problem with the metric has been resolved on their end, we will add it back to our requests. We apologize for any inconvenience that the temporary removal of this metric may cause.

3. monitoring Dec 05, 2025, 01:02 PM UTC

   After removing the metric that was causing issues, affected data sources are starting to stabilize. We anticipate that all delayed data sources should have up-to-date data within a few hours from now. We will keep this incident open for the time being in hopes of providing an update on when the metric in question will be restored. We will post an update as soon as we receive feedback from Meta on the subject, or if we discover that the metric starts working again through our own testing.

4. monitoring Dec 08, 2025, 04:46 PM UTC

   Meta has acknowledged our issue escalation, which has been flagged by other users as well. We will let you know once we have a resolution update from Meta.

5. monitoring Dec 10, 2025, 05:12 PM UTC

   We have escalated this issue with our Meta contact and are continuing to await further updates.

6. resolved Dec 11, 2025, 03:04 PM UTC

   Meta has confirmed that the issue has been resolved on their end. After verifying this on our side, we have now restored the "Total Video View Time (in MS)" (page_video_view_time) metric in our Facebook Pages connector.

Read the full incident report →

Started Dec 04, 2025, 04:14 PM UTC· resolved Jan 14, 2026, 01:41 PM UTC

1. investigating Dec 04, 2025, 04:14 PM UTC

   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.

2. investigating Dec 05, 2025, 03:26 PM UTC

   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.

3. investigating Dec 08, 2025, 04:17 PM UTC

   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.

4. investigating Dec 10, 2025, 05:20 PM UTC

   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.

5. investigating Dec 11, 2025, 11:22 AM UTC

   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.

6. identified Dec 15, 2025, 08:52 AM UTC

   LinkedIn has updated our issue report to say they have removed the functionality for receiving daily reports from this endpoint.

7. identified Dec 15, 2025, 03:16 PM UTC

   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.

8. identified Dec 17, 2025, 04:22 PM UTC

   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.

9. identified Dec 19, 2025, 04:10 PM UTC

   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.

10. identified Dec 22, 2025, 04:16 PM UTC

    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.

11. monitoring Dec 23, 2025, 12:01 PM UTC

    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.

12. monitoring Dec 29, 2025, 03:01 PM UTC

    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.

13. monitoring Dec 30, 2025, 02:11 PM UTC

    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.

14. resolved Jan 14, 2026, 01:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Oct 28, 2025, 05:00 PM UTC· resolved Oct 29, 2025, 02:00 AM UTC

1. resolved Oct 31, 2025, 01:27 PM UTC

   We experienced delayed exports due to an outage from AWS from 18:00 - 03:00 CET on the 28th of October in us-east-1. This outage affected several of our services which resulted in the delays. The services were back online as soon as the outage was fixed by AWS.

Read the full incident report →

Started Oct 20, 2025, 09:57 AM UTC· resolved Oct 23, 2025, 07:51 AM UTC

1. monitoring Oct 20, 2025, 09:57 AM UTC

   Earlier today, Funnel experienced a period of complete downtime due to a widespread AWS service disruption in the US-EAST-1 region, which impacted multiple AWS services including DynamoDB: https://health.aws.amazon.com/health/status As a result, the Funnel app was unavailable for approximately two hours. AWS has since implemented mitigations and reports that most services are recovering. Funnel is now operational again, but you may continue to experience some delays in data source updates and data exports as systems work through remaining backlogs. We are closely monitoring the situation and continuing to do everything we can to bring Funnel back to its normal performance. We’ll post further updates here as recovery progresses. We sincerely apologize for the inconvenience and appreciate your patience while we ensure everything is fully restored. (edited) No components were marked as affected by this incident.

2. monitoring Oct 20, 2025, 10:28 AM UTC

   AWS is reporting continued signs of recovery: “We continue to observe recovery across most of the affected AWS services. Global services and features that rely on US-EAST-1 have also recovered. We continue to work towards full resolution and will provide updates as we have more information to share.” As systems stabilize, some Funnel processes may still experience degraded performance, including: - Access to the Funnel app - Scheduled exports - Retrieval of new data Our team is actively working to restore full performance as quickly as possible. We appreciate your patience as services return to normal.

3. monitoring Oct 20, 2025, 02:03 PM UTC

   We’re continuing to monitor the ongoing AWS incident. While we’re seeing gradual recovery, Funnel services are not yet performing as expected. Downloads and exports have started to recover, but some users may still experience delays or errors in the app. Our team is closely tracking the situation and working to restore full functionality as soon as possible.

4. monitoring Oct 21, 2025, 05:10 AM UTC

   AWS has resolved the underlying issue in the us-east-1 region and systems have been stable for several hours. Funnel is operational again, though some background processing (such as data syncing and exports) may still be slower than normal. We will continue to monitor performance closely and post another update if there are any further impacts.

5. monitoring Oct 21, 2025, 11:30 AM UTC

   Most Funnel services have now returned to normal. The Data Sources page is the main area still affected. Right now, you may see an outdated view of your Data Sources. You can still add, remove, and edit sources, and these actions work as expected. However, changes will not immediately appear on the Data Sources page. Newly added sources will show in Data Explorer and Exports, while removed sources will not. We are working to restore the page to normal operation and will provide an update once it is fully resolved.

6. monitoring Oct 21, 2025, 01:58 PM UTC

   The issues affecting the Data Sources page have now been resolved. We are continuing to monitor all systems closely to ensure that all functionality is fully back to normal.

7. monitoring Oct 22, 2025, 07:02 AM UTC

   After resolving the Data Sources page issues, we have not received any further reports of issues and are therefore considering this incident closed. We sincerely apologize for any inconvenience this may have caused and appreciate your patience throughout the process.

8. resolved Oct 23, 2025, 07:51 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 01, 2025, 01:05 PM UTC· resolved Oct 02, 2025, 02:37 PM UTC

1. identified Oct 01, 2025, 01:05 PM UTC

   We have observed an increased rate of errors affecting Quora data sources, causing many scheduled imports to fail. We have identified the Quora API endpoint/request that is causing these errors, and have reached out to Quora for further troubleshooting.

2. monitoring Oct 02, 2025, 08:14 AM UTC

   The request errors we were experiencing appear to have stopped happening. We will continue to monitor the Quora connector to make sure everything works as it should before we consider this incident resolved.

3. resolved Oct 02, 2025, 02:37 PM UTC

   As the errors have yet to resurface, we believe this to be resolved.

Read the full incident report →

Started Aug 26, 2025, 12:51 PM UTC· resolved Sep 01, 2025, 01:42 PM UTC

1. identified Aug 26, 2025, 12:51 PM UTC

   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.

2. resolved Sep 01, 2025, 01:42 PM UTC

   The Shopping24 connector has now been reconnected to the new Shopping24 API and is working as expected. However, existing authentication tokens are no longer valid due to the API change. Action required: To resume data retrieval, users need to request a new API token from their Shopping24 account manager and reconnect their Data Sources in Funnel with this new token. Emails with instructions have been sent to all Funnel users who currently have active Shopping24 Data Sources, ensuring they are aware of the required action.

Read the full incident report →

Started Aug 26, 2025, 09:59 AM UTC· resolved Aug 27, 2025, 10:14 AM UTC

1. monitoring Aug 26, 2025, 09:59 AM UTC

   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.

2. resolved Aug 27, 2025, 10:14 AM UTC

   All affected sources have returned to normal operations.

Read the full incident report →

Started Aug 20, 2025, 01:02 PM UTC· resolved Aug 20, 2025, 01:39 PM UTC

1. monitoring Aug 20, 2025, 01:02 PM UTC

   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.

2. resolved Aug 20, 2025, 01:39 PM UTC

   All systems have now recovered.

Read the full incident report →

Started Aug 15, 2025, 10:01 AM UTC· resolved Aug 19, 2025, 09:29 AM UTC

1. identified Aug 15, 2025, 10:01 AM UTC

   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.

2. monitoring Aug 16, 2025, 10:48 AM UTC

   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.

3. monitoring Aug 18, 2025, 02:01 PM UTC

   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.

4. monitoring Aug 19, 2025, 09:29 AM UTC

   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.

5. resolved Aug 19, 2025, 09:29 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 05, 2025, 09:35 AM UTC· resolved Aug 06, 2025, 07:57 AM UTC

1. monitoring Aug 05, 2025, 09:35 AM UTC

   We have observed an increase in delayed data sources for the following connectors: Amazon Advertising Amazon DSP Apple Search Ads Campaign Manager 360 Criteo Display & Video 360 Finance Ads LinkedIn Microsoft Ads Naver Pinterest Reddit Snapchat Teads The Trade Desk TikTok X Ads Yahoo Japan Search After some investigation, we found the root cause to be a bug in our data storage service stemming from a code deploy around 14:00 (2:00 PM) CEST yesterday. The bug has now been fixed, and we are currently monitoring data sources that were affected by these delays. We are expecting all affected data sources to recover by this afternoon CEST, roughly 4-8 hours from now.

2. resolved Aug 06, 2025, 07:57 AM UTC

   Data sources affected by this bug should now be up-to-date and performing as expected. We consider this issue resolved.

Read the full incident report →

Started Jul 25, 2025, 01:38 PM UTC· resolved Jul 28, 2025, 09:07 AM UTC

1. investigating Jul 25, 2025, 01:38 PM UTC

   We are seeing elevated error rates for Yelp data sources. It appears that reports generated through the Yelp API get stuck in processing and never complete, causing delays. We are investigating the issue and trying to determine if there is any mitigation that can be done on our end.

2. resolved Jul 28, 2025, 09:07 AM UTC

   Data sources seem to be downloading normally once again. We are considering this resolved.

Read the full incident report →

Started Jul 25, 2025, 12:54 PM UTC· resolved Oct 10, 2025, 02:49 PM UTC

1. investigating Jul 25, 2025, 12:54 PM UTC

   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.

2. investigating Jul 28, 2025, 10:03 AM UTC

   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.

3. investigating Jul 29, 2025, 08:16 AM UTC

   Meta has responded to our ticket, requesting additional information to aid in debugging the issue from their side.

4. investigating Jul 30, 2025, 09:43 AM UTC

   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%.

5. investigating Aug 01, 2025, 03:03 PM UTC

   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.

6. investigating Aug 05, 2025, 03:11 PM UTC

   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.

7. investigating Aug 07, 2025, 02:12 PM UTC

   Update: Today half as many sources were affected as were the previous two days. We are continuing to monitor for further improvements.

8. investigating Aug 14, 2025, 02:29 PM UTC

   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).

9. investigating Aug 15, 2025, 05:07 PM UTC

   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.

10. investigating Aug 27, 2025, 10:18 AM UTC

    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.

11. investigating Sep 12, 2025, 11:20 AM UTC

    We are continuing to monitor this issue and escalate the issue with our Meta contacts. Together we are actively debugging to find a root cause to the issue. The issue is continuing to behave non-deterministically: affecting different sources each day. The total number of sources affected per day is fluctuating between a bit less than one in 1000 to one in 10,000.

12. investigating Sep 26, 2025, 08:55 AM UTC

    We are continuing to monitor this issue and escalate the issue with our Meta contacts. Together we are actively debugging to find a root cause to the issue. The issue is continuing to behave non-deterministically: affecting different sources each day. The total number of sources affected per day is fluctuating between a bit less than three in 1000 to one in 10,000, but without any straightforward pattern.

13. investigating Oct 03, 2025, 02:36 PM UTC

    We know many of you rely on Facebook Ads data for reporting and decision-making, and we understand how frustrating it is when that data isn’t reliable. We want to be transparent about what’s happening and what we’re doing to help. Some customers are currently experiencing errors when pulling data from the Facebook Ads API. Unfortunately, these errors are inconsistent: some sources fail on certain days while others continue to work, and the pattern is not predictable. This makes the issue disruptive, even though it affects a relatively small number of customers and sources each day. Meta’s guidance is to make smaller API requests, but our testing shows that request size is not always the cause, sometimes smaller requests succeed, and other times they don’t. Because of this, we are implementing alternative ways of fetching data and introducing enhanced authentication methods to improve stability. We are actively working on these changes now and expect to provide an update next week on their effectiveness. In the meantime, if you experience failures, retrying may sometimes resolve them, but we recognize this is not a long-term solution. Thank you for your patience while we work to make this more stable. We know how important this data is to your business, and addressing this remains a top priority for us.

14. resolved Oct 10, 2025, 02:49 PM UTC

    The incident affecting Facebook Ads data imports that began on July 17th has now been resolved ✅ Over the past several weeks, a small number of customers experienced inconsistent errors when downloading data from the Facebook Ads API. The issue was unpredictable, affecting different data sources and customers on different days. Throughout this time, our Connector Team has been actively investigating the issue, testing multiple workarounds, and collaborating closely with Meta’s engineering team to share detailed findings from our side. While several fixes were introduced along the way, the root cause wasn’t fully clear until last week, when our engineers identified the final workaround needed to restore stability. A permanent fix was deployed to production on October 6th, and since then, all Facebook data sources have been updating reliably again. Any new errors that occur are unrelated to this incident. We truly appreciate your patience and understanding while we worked through this. We know how important reliable Facebook Ads data is for your reporting and decision-making, and we’re glad to confirm that everything is now back to normal.

Read the full incident report →

Started Jul 22, 2025, 02:22 PM UTC· resolved Jul 29, 2025, 09:16 AM UTC

1. identified Jul 22, 2025, 02:22 PM UTC

   The increased error rate we observed recently for The Trade Desk data sources has resurfaced, causing further delays for most data sources. We have received the following correspondence from a representative at The Trade Desk: "This is a platform wide issue we are currently working through. There is nothing for you to do right now other than wait for our system to catch up. We expect to be fully caught up in the next day or so." We will continue to monitor affected data sources.

2. monitoring Jul 23, 2025, 09:27 AM UTC

   We are continuing to monitor affected data sources. We are seeing some signs of improvement, but most data sources are still experiencing delayed imports.

3. monitoring Jul 24, 2025, 11:54 AM UTC

   We are still seeing signs of degraded performance for The Trade Desk data sources. We will continue to monitor the situation.

4. monitoring Jul 28, 2025, 09:11 AM UTC

   We are seeing that significantly fewer data sources are affected by the aforementioned delays, though some appear to still run into the issue with reports getting stuck on occasion. We will continue to monitor all The Trade Desk data sources closely until we feel able to consider the issue resolved.

5. resolved Jul 29, 2025, 09:16 AM UTC

   Error rates for The Trade Desk appear to have stabilized. We will consider this issue resolved.

Read the full incident report →

Started Jul 14, 2025, 05:39 PM UTC· resolved Jul 15, 2025, 01:39 PM UTC

1. investigating Jul 14, 2025, 05:39 PM UTC

   We have recently received reports from users that the Data Explorer is no longer loading. Our team is currently investigating the issue and will continue to post updates as soon as we have more information.

2. monitoring Jul 14, 2025, 06:08 PM UTC

   The team has identified the issue and the Data Explorer tool should be loading again properly. We'll continue to monitor the progress of the update and follow up with more information as soon as we have more insights to share

3. resolved Jul 15, 2025, 01:39 PM UTC

   After careful monitoring and no recent reports of the Data Explorer not loading, the issue is now resolved.

Read the full incident report →

Started Jul 10, 2025, 06:52 AM UTC· resolved Jul 11, 2025, 10:47 AM UTC

1. identified Jul 10, 2025, 06:52 AM UTC

   We are experiencing issues when authenticating new credentials to the Salesforce Marketing Cloud connector. Existing authenticated sources remain unaffected, but any attempts to add new credentials are failing.

2. resolved Jul 11, 2025, 10:47 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 26, 2025, 09:33 AM UTC· resolved Jun 28, 2025, 11:24 AM UTC

1. investigating Jun 26, 2025, 09:33 AM UTC

   Since approximately 08:00 CEST today, we have seen an increase in query error rates. This affects both the Funnel App and Scheduled Exports.

2. monitoring Jun 26, 2025, 03:27 PM UTC

   A number of mitigating changes have been deployed, and error rates are currently back to normal.

3. resolved Jun 28, 2025, 11:24 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 25, 2025, 10:49 AM UTC· resolved Jun 26, 2025, 07:14 AM UTC

1. investigating Jun 25, 2025, 10:49 AM UTC

   Since approximately 08:00 CET today, we have not been receiving updated data from the Meta (Facebook Ads) API. This is affecting scheduled data refreshes across all Facebook Ads sources. We are continuing to investigate the issue and have also reached out to Meta for further clarification.

2. investigating Jun 26, 2025, 07:14 AM UTC

   We’re pleased to inform you that the earlier disruption on Meta’s side affecting the Ads Insights API has been fully resolved as of this morning. According to Meta’s official status update: “We have recovered from an earlier outage impacting Ads Insights API, and services have now been restored. We apologise for any inconvenience that this may have caused.” – Meta, 25 June 2025, 07:07 AM GMT+2 https://metastatus.com/marketing-api Our systems are now receiving data as expected. Thank you for your patience while we monitored and investigated this issue. If you continue to experience any anomalies, please don’t hesitate to reach out.

3. resolved Jun 26, 2025, 07:14 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2025, 09:28 PM UTC· resolved Jun 13, 2025, 07:17 AM UTC

1. investigating Jun 12, 2025, 09:28 PM UTC

   Currently Google is reporting issues with their cloud services across all regions in the world. This in turn has lead to Google BigQuery and Cloud exports from Funnel to fail. Google is aware of the situation and investigating on their end. You can follow along on the status of Google Cloud Services here on Google's status page: https://status.cloud.google.com/

2. resolved Jun 13, 2025, 07:17 AM UTC

   Google have resolved the incident on their side and we have stopped seeing issues.

Read the full incident report →

Started Jun 05, 2025, 12:06 PM UTC· resolved Jun 12, 2025, 11:44 AM UTC

1. identified Jun 05, 2025, 12:06 PM UTC

   We've identified an issue for our Unity Ads connector that keeps us from being able to download data. If you are affected by this issue, please reach out to support and they'll put you in touch with our developers.

2. resolved Jun 12, 2025, 11:44 AM UTC

   The issue was a planned update of the Unity Ads API that we unfortunately missed. The issue itself has been resolved but you need to connect new sources in order to keep receiving data.

Read the full incident report →

Started May 30, 2025, 02:35 PM UTC· resolved Jun 12, 2025, 11:45 AM UTC

1. investigating May 30, 2025, 02:35 PM UTC

   YouTube is currently having a disruption in their API and we receive errors a subset of our data sources when we request data. This is causing delays in our downloads. As this is a bug on the YouTube side we will monitor the situation and update if there are any changes.

2. monitoring Jun 03, 2025, 09:50 AM UTC

   We have noticed a significant decrease in errors of this type. We will continue to monitor previously affected data sources before considering this fully resolved.

3. resolved Jun 12, 2025, 11:45 AM UTC

   The downloads seem to be working as expected again.

Read the full incident report →

Started May 15, 2025, 04:21 PM UTC· resolved May 26, 2025, 11:23 AM UTC

1. investigating May 15, 2025, 04:21 PM UTC

   We are currently experiencing an issue with displaying data from Google Sheet sources in the Data Explorer. We are investigating the problem.

2. investigating May 15, 2025, 04:52 PM UTC

   We have deployed a fix and we are currently monitoring the results.

3. resolved May 26, 2025, 11:23 AM UTC

   This incident has been resolved.

Read the full incident report →