Funnel Outage History
Uptime record, past incidents, and downtime history for Funnel.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| June 2026 | 0% | 27 | 27 |
| May 2026 | 32.3% | 31 | 21 |
| April 2026 | 100% | 30 | 0 |
| March 2026 | 100% | 3 | 0 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Mar 29
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
June 2026
Issues with Facebook and Instagram sources
Started: Jun 12, 2:15 PM
monitoring
Facebook appears to have implemented a fix on their side. We've had recent reports of users successfully connecting their Facebook and Instagram data sources, and new connections should now be working. We'll continue to monitor the situation but believe the issue should be resolved at this point in time.
Jun 12, 4:17 PM
investigating
There's an issue currently originating from Meta, which affects their services. Once the issue is resolved on Meta's side, the connection of new Facebook and Instagram sources will be possible again.
Feel free to follow along and monitor the progress of the incident on Facebook's official status page here: https://metastatus.com/ads-manager
Jun 12, 2:15 PM
Display & Video 360 – Data delay for YouTube reports
Started: Jun 1, 11:11 AM
monitoring
While we have not received any further correspondence from the DV360 team, we have observed that a majority of the data sources affected by this issue are now successfully managing to import new data.
We will continue to monitor the connector for a while longer before considering this issue fully resolved.
Jun 3, 7:32 AM
identified
We have received confirmation from the Display & Video 360 team that there is an ongoing technical issue causing reports containing YouTube data to be significantly delayed.
Their technical team is currently working on resolving the problem.
Jun 2, 8:50 AM
identified
We have observed that Display & Video 360 data sources that are configured to retrieve YouTube-related data, including data sources fetching custom reports that contain YouTube data, are currently struggling to import new data. From our investigation we believe this to be an issue with the DV360 API itself, as any report we attempt to generate that contains YouTube data ends up pending indefinitely.
We have reached out to the DV360 support team with our findings, and we will continue to moni...
Jun 1, 11:11 AM
May 2026
Facebook Ads sources delayed with "Service temporarily unavailable".
Started: May 21, 11:04 AM
investigating
Facebook Ads data sources, including those with the Country breakdown, have continued to download as expected since our last update, and we have not seen any further "Service temporarily unavailable" errors from the Meta API.
We are considering this incident resolved. If you experience any further issues, please reach out to support.
Thank you for your patience
May 29, 1:27 PM
investigating
We are now seeing Facebook Ads data sources downloading normally again, including those configured with the Country breakdown.
We have re-tested and can confirm that data is flowing as expected. We will continue to monitor the situation and provide further updates if anything changes.
Thank you for your patience.
May 27, 2:13 PM
investigating
We're actively working with Meta's engineering team to resolve this issue and will continue to provide updates as we learn more.
May 26, 9:05 AM
investigating
We've identified that this issue specifically affects data sources configured with the Country breakdown. Sources without this breakdown are downloading normally.
Workaround: If the Country breakdown is not essential for your reporting, you can connect a new data source without it applied to resume data imports.
We are in contact with Meta regarding this issue and will provide another update as soon as we have more information.
May 22, 11:25 AM
investigating
We are continuing to investigate this issue.
May 22, 11:24 AM
investigating
We are aware of this issue and in contact with Meta support.
We have been receiving "Service temporarily unavailable" from the Facebook Ads API since the 16th of May.
We will keep updating you on this status page.
Thank you for your patience.
/Funnel Team
May 21, 11:04 AM
Salesforce data sources — increased authentication errors
Started: May 12, 6:25 PM
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 resolv...
May 15, 3:30 PM
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...
May 12, 6:25 PM
April 2026
Increased error rates in Data Studio Connector
Started: Apr 28, 8:56 AM
identified
Over the last week we see an increase in error rates in Funnels Data Studio Connector.
These show up as 'Bandwidth quota exceeded' or as column mismatch error when loading data.
This looks to be a widespread issue on Googles side affecting many different services.
We are waiting for confirmation from Google and are looking at other ways to mitigate this issue.
Apr 28, 8:56 AM
Amazon Seller Central & Amazon Vendor Central – Delayed imports
Started: Apr 21, 2:48 PM
monitoring
We identified the issue and just deployed a fix. We are monitoring affected data sources to ensure everything works as expected.
Apr 22, 9:03 AM
investigating
We have observed an escalated number of failing import jobs for our Amazon Seller Central and Amazon Vendor Central connectors. Most data sources appear to be affected.
We are currently investigating the cause of this issue.
Apr 21, 2:48 PM
Facebook Ads - Data delays
Started: Apr 14, 1:33 PM
investigating
We are currently investigating an issue causing data delays across several Facebook Ads data sources. Our requests are receiving "Internal Server Error" responses from the Meta API.
Apr 14, 1:33 PM
X Ads and X Organic data sources in Delayed state for Subset of report types
Started: Apr 11, 11:33 AM
identified
We have continued investigating the remaining X Ads and X Organic report types affected by X's ad platform migration. This update reflects progress and current status across the outstanding areas.
Location / Country segmentation We have confirmed with X that Location / Country is no longer supported in their ad platform. We are adding a clear error message for sources using this configuration so they no longer appear active without returning data. This is consistent with X's guidance that th...
Jun 25, 12:43 PM
identified
We have deployed additional X Ads connector changes to reflect the reporting capabilities we have now confirmed after X’s ad platform migration.
As part of this update, several segmentation types that no longer return reliable data from X have been removed for new data source configurations. Existing sources using these configurations will now show a clear error message instead of continuing to appear active while returning no new data. This helps prevent silent gaps in reporting and makes...
Jun 9, 7:28 AM
identified
We have deployed connector changes earlier this week based on the reporting capabilities currently available from X following their ad platform migration.
These changes have restored downloads for many X Ads data sources that were previously delayed. We are continuing to monitor the resumed downloads closely to verify that data is complete and aligned with the selected report configurations.
As previously communicated, X has removed support for some reporting capabilities. This means that W...
Jun 4, 12:37 PM
identified
Update — June 3 ETA, connector changes from X's new API guidelines
We have received written confirmation from X on which reporting capabilities remain available following their ad stack migration. We are now updating the connector accordingly. We expect most data sources to resume downloading from June 3, 2026.
What is changing:
Sources using segmentation types that X has permanently discontinued will be set to an Error state. You will see a red error indicator on those data sources in F...
May 28, 2:16 PM
identified
We are still working with X on this issue, but there has not been any progress since our last update.
We will keep posting in this Status Page to keep you informed on the situation.
May 22, 10:25 AM
identified
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, 4:38 PM
identified
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.
...
May 7, 1:54 PM
identified
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, 1:31 PM
identified
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 ...
Apr 27, 1:42 PM
identified
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, 12:57 PM
identified
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...
Apr 19, 9:29 PM
identified
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, 3:34 PM
identified
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, 5:06 PM
identified
We are continuing to work on a fix for this issue.
Apr 13, 1:06 PM
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 s...
Apr 11, 11:33 AM
X Ads and X Organic connectors in delayed state for specific Report types
Started: Apr 11, 11:29 AM
investigating
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 woring)
The issue has been reported by multiple other vendors.
The issues started 2026-10-10.
We are working on findings ways around the issue.
See also related Status page X Ads - Missing data si...
Apr 11, 11:29 AM
Google Looker Studio - Connector not working
Started: Apr 9, 2:58 PM
monitoring
Google has informed us that: "The issue with Looker Studio has been resolved for all affected customers".
Funnels Google Looker Studio Connector are now working as normal.
We will continue to monitor the situation.
Apr 9, 4:40 PM
identified
Google has identified that some customers experience errors loading Community Connectors. They are working on mitigating the issue.
We will monitor and update when we have new information from Google.
Apr 9, 3:32 PM
investigating
There is an issue with Funnels Google Looker Studio Connector not responding and data is not loading in reports.
We are currently investigating the cause.
Apr 9, 2:58 PM
X Ads - Missing data since 26 March
Started: Apr 1, 9:41 AM
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 7, 5:55 PM
investigating
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 ...
Apr 3, 3:02 PM
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 1, 9:41 AM
March 2026
TikTok - Missing values for several Ad level fields
Started: Mar 20, 2:24 PM
monitoring
A fix has been implemented and we're monitoring the results.
Mar 24, 4:12 PM
investigating
We're aware of missing values for several Ad level fields for the TikTok connector, such as Ad status, Video ID, Ad landing page URL and more.
We're currently investigating the cause.
Mar 20, 2:24 PM
Facebook Ads missing deleted/archived ads.
Started: Mar 19, 1:53 PM
investigating
There is an active investigation into a spike in reports regarding missing data for archived or deleted Meta ads. While the system is designed to pull this historical content, a recent shift is currently obstructing these data sources.
Root cause analysis is underway to determine the scale of this Meta limitation.
Mar 19, 1:53 PM
February 2026
Facebook Ads – Import delays
Started: Feb 9, 3:56 PM
investigating
While the temporary fix is still in place and is allowing data sources to resume downloading data, we are also in the process of providing info to Meta. We are awaiting for Meta's technical feedback on the matter.
Mar 6, 2:11 PM
investigating
We are continuing to investigate the root cause of the recent data delays and are currently awaiting further technical feedback from Meta. To restore service in the meantime, we have deployed a temporary fix. While this allows data sources to resume downloading successfully, please note that a very small subset of ads will temporarily omit the bid_amount field. Most reporting delays have now been resolved and we will update when we have more information.
Feb 13, 2:30 PM
investigating
We are currently investigating an issue causing data delays across several Facebook Ads data sources. Our requests are receiving "Internal Server Error" responses from the Meta API.
This has been escalated to Meta for investigation. As this is an upstream issue on their end, we are awaiting their feedback and will provide updates as they become available.
Feb 9, 3:56 PM