Looking for an update now? Check the current status, or follow Funnel for future changes.
100%of 83 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
October 2026
100%
31
0
September 2026
100%
30
0
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Aug 17Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.
Legacy Incident Archive
14 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
April 2026
X Ads - Missing data since 26 March
Source not attested
Last archived state: resolved
View archived record details
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
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 ...
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.
March 2026
TikTok - Missing values for several Ad level fields
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we're monitoring the results.
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.
Facebook Ads missing deleted/archived ads.
Source not attested
Last archived state: resolved
View archived record details
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.
February 2026
Facebook Ads – Import delays
Source not attested
Last archived state: resolved
View archived record details
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.
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.
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.
