Snapshot 20528
Normalized text
Scripts and page chrome removed; this is what change detection compares.
{
"pages": [
{
"end_time": "2026-09-30T23:59:59+02:00",
"months": [
{
"incidents": [
{
"code": "1vxy6hd9g7m9",
"impact": "none",
"message": "ChatGPT is now working again and can connect to Funnel's MCP.",
"name": "MCP for ChatGPT unavailable",
"timestamp": "Sep \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e09:20\u003c/var\u003e - Sep \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e14:22\u003c/var\u003e CEST"
}
],
"name": "September",
"year": 2026
},
{
"incidents": [
{
"code": "5jl331sd3fs2",
"impact": "none",
"message": "TikTok have confirmed on their end that the underlying issue is resolved, and our monitoring shows that all data sources are successfully importing data once again.",
"name": "TikTok – Delayed imports",
"timestamp": "Aug \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e10:02\u003c/var\u003e - Aug \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e10:26\u003c/var\u003e CEST"
}
],
"name": "August",
"year": 2026
},
{
"incidents": [],
"name": "July",
"year": 2026
}
],
"start_time": "2026-07-01T00:00:00+02:00",
"time_zone": "Stockholm"
},
{
"end_time": "2026-06-30T23:59:59+02:00",
"months": [
{
"incidents": [
{
"code": "hcc0k4jllbrq",
"impact": "none",
"message": "This incident has been resolved.",
"name": "Issues with Facebook and Instagram sources",
"timestamp": "Jun \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e16:15\u003c/var\u003e - Jun \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e10:26\u003c/var\u003e CEST"
},
{
"code": "ggtj8xkxpbhg",
"impact": "none",
"message": "We have received confirmation from the DV360 team that the issue has been resolved.",
"name": "Display \u0026 Video 360 – Data delay for YouTube reports",
"timestamp": "Jun \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e13:11\u003c/var\u003e - Jun \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e10:03\u003c/var\u003e CEST"
}
],
"name": "June",
"year": 2026
},
{
"incidents": [
{
"code": "dytly07hsw9f",
"impact": "none",
"message": "This incident has been resolved.",
"name": "Facebook Ads sources delayed with \"Service temporarily unavailable\".",
"timestamp": "May \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e13:04\u003c/var\u003e - May \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e15:51\u003c/var\u003e CEST"
},
{
"code": "dsyj3s7hzrzf",
"impact": "none",
"message": "Closing this issue, since its related to the larger issue around X new ad platform",
"name": "X Ads - Missing data since 26 March",
"timestamp": "Apr \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e11:41\u003c/var\u003e - May \u003cvar data-var='date'\u003e28\u003c/var\u003e, \u003cvar data-var='time'\u003e16:15\u003c/var\u003e CEST"
},
{
"code": "g0pf84k6rp8c",
"impact": "none",
"message": "We are pleased to confirm that the Salesforce authentication errors have been fully resolved. All affected data sources should now be reconnected and downloading data as expected. Thank you for your patience on the matter.",
"name": "Salesforce data sources — increased authentication errors",
"timestamp": "May \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e20:25\u003c/var\u003e - May \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e14:45\u003c/var\u003e CEST"
}
],
"name": "May",
"year": 2026
},
{
"incidents": [
{
"code": "d7bh0n7b1hzr",
"impact": "none",
"message": "Google has reported that the issue has been fixed and we have not seen any new errors in our logs.\nWe will continue to monitor but we now consider this issue to be resolved.",
"name": "Increased error rates in Data Studio Connector",
"timestamp": "Apr \u003cvar data-var='date'\u003e28\u003c/var\u003e, \u003cvar data-var='time'\u003e10:56\u003c/var\u003e - Apr \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e10:42\u003c/var\u003e CEST"
},
{
"code": "z227dfrd2483",
"impact": "none",
"message": "We've worked together with Meta to address the delays affecting Facebook Ads data sources and Facebook Ads data should be processing as expected without errors or gaps. Should you notice any issues, please don't hesitate to reach out.",
"name": "Facebook Ads - Data delays",
"timestamp": "Apr \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e15:33\u003c/var\u003e - Apr \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e15:28\u003c/var\u003e CEST"
},
{
"code": "6q1ncqkgwn8l",
"impact": "none",
"message": "This issue is resolved. Data sources that have experienced delays as a result of this incident will be up-to-date within a few hours.",
"name": "Amazon Seller Central \u0026 Amazon Vendor Central – Delayed imports",
"timestamp": "Apr \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e16:48\u003c/var\u003e - Apr \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e12:52\u003c/var\u003e CEST"
},
{
"code": "xp4x761pfskd",
"impact": "none",
"message": "Closing issue since the correction made 6th of March. \nWe still see a handful of sources not working with the correction due to the complexity. But this is handled as support issues",
"name": "Facebook Ads – Import delays",
"timestamp": "Feb \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e16:56\u003c/var\u003e - Apr \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e16:13\u003c/var\u003e CEST"
},
{
"code": "2rps0jbb7vnq",
"impact": "none",
"message": "Postmortem: \nThe issue was due to a change of download schedule for TikTok that resulted in long download cues. \n\nWe have implemented observability and gardrails for this type of issue happen again",
"name": "TikTok - Missing values for several Ad level fields",
"timestamp": "Mar \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e15:24\u003c/var\u003e - Apr \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e14:48\u003c/var\u003e CEST"
},
{
"code": "c7vzzqxyjfx1",
"impact": "none",
"message": "We have continued work on the remaining X Ads and X Organic report types affected by X’s ad platform migration. This update covers two areas now resolved and what remains under investigation.\n\nResolved\nX Organic Tweet Activity\nX Organic Tweet Activity metrics are working again. We have validated downloads on multiple sources, including a comparison against pre-incident historical exports with no metric mismatches. Organic data collection has resumed for affected sources. We will continue monitoring for stability.\n\nLocation / Country segmentation\nAs confirmed with X, Location / Country is no longer supported in their ad platform. We have removed Location / Country from the source configuration so it cannot be selected for new sources. Existing sources using this segmentation will receive a clear error when X returns no breakdown data, with guidance to pause the source (to retain historical data) or use Location / Metro Area as the supported alternative. This is consistent with X’s guidance that supported segmentation types going forward are Age, Gender, Platforms, and Location / Metro Area.\n\nOngoing investigation\nAge segmentation\nX has stated that Age-segmented reports are operational, and we shipped a fix in June so renamed age buckets are no longer dropped. However, we continue to see a pattern where some sources return incomplete data — specifically, campaigns with hollow breakdown payloads that can block an entire download. We are working with X to confirm expected behavior and are preparing a connector change to skip zero-activity hollow entries so valid data from other campaigns is not lost.\n\nPlatforms segmentation\nWe continue to monitor Platforms-segmented reports where data does not always match expectations. Investigation is ongoing; we will update when scope and handling are confirmed.\n\nCampaign-level budget optimization (LINE_ITEM)\nReports for campaigns using line-item budget optimization can still return HTTP 200 with all metrics null at every entity level. X previously acknowledged this as a known issue; we are still awaiting confirmation of a fix.\n\nReach \u0026amp; Frequency reports\nSince early July, X’s Reach \u0026amp; Frequency API has rejected date windows longer than 7 days, which affects sources configured with longer attribution windows. We are investigating options and will update once we have a stable path forward.\n\nLookback boundary\nA lookback boundary remains in place at the start of April 2026 for X Ads. X’s reporting APIs do not make migration-period data available for reliable re-fetching, so Funnel will not attempt to re-download paid ads data before this point. Historical data already collected in Funnel remains available. X Organic is not subject to this same restriction — validated organic downloads include pre-April periods.\n\nWe will continue posting updates here as each area is confirmed resolved or stabilized.",
"name": "X Ads sources in Delayed state for Subset of report types",
"timestamp": "Apr \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e13:33\u003c/var\u003e CEST"
},
{
"code": "vr0svyl1243w",
"impact": "none",
"message": "Everything working as normal, we consider this issue to be resolved.",
"name": "Google Looker Studio - Connector not working",
"timestamp": "Apr \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e16:58\u003c/var\u003e - Apr \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e10:46\u003c/var\u003e CEST"
},
{
"code": "n7xs52zcj3js",
"impact": "none",
"message": "Closing incident since we 24 of March reverted the changes that resulted in that archived and deleted ads were not returned. After monitoring the update we are back to correct behavior.",
"name": "Facebook Ads missing deleted/archived ads.",
"timestamp": "Mar \u003cvar data-var='date'\u003e19\u003c/var\u003e, \u003cvar data-var='time'\u003e14:53\u003c/var\u003e - Apr \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e21:28\u003c/var\u003e CEST"
}
],
"name": "April",
"year": 2026
}
],
"start_time": "2026-04-01T00:00:00+02:00",
"time_zone": "Stockholm"
},
{
"end_time": "2026-03-31T23:59:59+02:00",
"months": [
{
"incidents": [
{
"code": "5bc3pj0v5030",
"impact": "minor",
"message": "This incident has been resolved.",
"name": "sftp exports are delayed",
"timestamp": "Mar \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e10:51\u003c/var\u003e - Mar \u003cvar data-var='date'\u003e26\u003c/var\u003e, \u003cvar data-var='time'\u003e09:53\u003c/var\u003e CET"
},
{
"code": "30vfnvyddhsd",
"impact": "none",
"message": "We consider this issue to be resolved. Backfills for affected data sources should be completed successfully by now.\n\nIf you observe any inflated monetary values in your AppsFlyer data sources, please reach out to support for investigation.",
"name": "AppsFlyer - Data Mismatch",
"timestamp": "Mar \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e16:05\u003c/var\u003e - Mar \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e11:06\u003c/var\u003e CET"
},
{
"code": "symxsdxwjb96",
"impact": "none",
"message": "We deployed a fix over the weekend which allowed us to resume downloads again. As of March 8th, downloads are back to normal.",
"name": "TikTok - Delayed Downloads",
"timestamp": "Mar \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e15:01\u003c/var\u003e - Mar \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e11:08\u003c/var\u003e CET"
},
{
"code": "f6jzd52rvpnc",
"impact": "none",
"message": "All affected Trade Desk data sources have now fully recovered, and data imports are operating normally.\nThe issue was caused by a recent connector update that impacted API performance. The update has been reverted, and we have validated that imports are completing as expected.\nWe will continue to monitor performance closely to ensure ongoing stability.",
"name": "The Trade Desk - Delayed data source imports",
"timestamp": "Mar \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e18:09\u003c/var\u003e - Mar \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e15:53\u003c/var\u003e CET"
},
{
"code": "53q5qbn6glpk",
"impact": "none",
"message": "After confirming that they were able to replicate the issue on their end, the DV360 team have now fixed the problem. Data sources in Funnel are now up-to-date and downloading new data without interruptions.",
"name": "Display \u0026 Video 360 – Data delay for YouTube reports",
"timestamp": "Feb \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e12:07\u003c/var\u003e - Mar \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e09:39\u003c/var\u003e CET"
}
],
"name": "March",
"year": 2026
},
{
"incidents": [
{
"code": "vbhpr300k5lx",
"impact": "none",
"message": "After confirmation from several customers normal operations have been restored. We apologize for the issue and thank you for your patience.",
"name": "Unable to connect new data source connections to Funnel",
"timestamp": "Feb \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e18:32\u003c/var\u003e - \u003cvar data-var='time'\u003e20:31\u003c/var\u003e CET"
}
],
"name": "February",
"year": 2026
},
{
"incidents": [
{
"code": "9n8rc5xy1xyv",
"impact": "critical",
"message": "Export queues have remained at normal levels, and exports have been processing as expected for the past four hours.\n\nWe now consider this incident resolved. Our teams will continue with follow-up investigation to fully understand the root cause and ensure we prevent similar issues in the future.\n\nWe’re very sorry for the disruption this caused and sincerely thank you for your patience while we worked to resolve the issue.",
"name": "Delayed exports",
"timestamp": "Jan \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e10:47\u003c/var\u003e - \u003cvar data-var='time'\u003e16:42\u003c/var\u003e CET"
},
{
"code": "hcs02tflrjzr",
"impact": "none",
"message": "The Basis API is back online again. Data sources using the connector are now up-to-date.",
"name": "Basis – API outage",
"timestamp": "Jan \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e10:58\u003c/var\u003e - Jan \u003cvar data-var='date'\u003e28\u003c/var\u003e, \u003cvar data-var='time'\u003e10:01\u003c/var\u003e CET"
},
{
"code": "pksvhs45ks6x",
"impact": "none",
"message": "We’re now closing this incident, as everything has been running smoothly since yesterday.\n\nThe root cause was an update to one of our supporting libraries, which led to incorrect data being shown for a period of time. We’re adding additional safeguards and monitoring to reduce the risk of this happening again.\n\nWe sincerely apologize for any inconvenience this may have caused. We know that you rely on Funnel to make confident marketing decisions, and our commitment is that your data should always be available, accurate, and trustworthy. We fell short of that expectation in this case, and we appreciate your patience while we resolved the issue.\n\nThank you for your understanding.",
"name": "Facebook Ads incomplete data - zero metric values",
"timestamp": "Jan \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e13:22\u003c/var\u003e - Jan \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e13:54\u003c/var\u003e CET"
},
{
"code": "5mpkjv0w4ght",
"impact": "none",
"message": "We have received information from TikTok's team that this was an intended but unannounced change in their API.\n\nWe 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.",
"name": "TikTok Organic – Delayed imports for some data sources",
"timestamp": "Jan \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e10:36\u003c/var\u003e - Jan \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e13:55\u003c/var\u003e CET"
},
{
"code": "7tt6bfctd5yn",
"impact": "none",
"message": "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.",
"name": "Snapchat – Delayed imports",
"timestamp": "Jan \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e10:52\u003c/var\u003e - Jan \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e10:01\u003c/var\u003e CET"
},
{
"code": "27mcsjcg8l2c",
"impact": "major",
"message": "This incident has been resolved.",
"name": "LinkedIn Organic - Data Definition Error - Video Metrics Report \u0026 Per Update breakdown on Update Metrics Report",
"timestamp": "Dec \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e17:14\u003c/var\u003e - Jan \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e14:41\u003c/var\u003e CET"
},
{
"code": "sqr2n8llz3x5",
"impact": "none",
"message": "Error rates have stabilized. We now consider this issue resolved.",
"name": "The Trade Desk – Delayed imports",
"timestamp": "Jan \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e13:04\u003c/var\u003e - Jan \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e15:27\u003c/var\u003e CET"
}
],
"name": "January",
"year": 2026
}
],
"start_time": "2026-01-01T00:00:00+01:00",
"time_zone": "Stockholm"
},
{
"end_time": "2025-12-31T23:59:59+01:00",
"months": [
{
"incidents": [
{
"code": "7dp3r6r2bgcp",
"impact": "none",
"message": "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.",
"name": "Facebook Pages – Import delays",
"timestamp": "Dec \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e10:21\u003c/var\u003e - Dec \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e16:04\u003c/var\u003e CET"
}
],
"name": "December",
"year": 2025
},
{
"incidents": [],
"name": "November",
"year": 2025
},
{
"incidents": [
{
"code": "vgc7jks1kx41",
"impact": "none",
"message": "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.",
"name": "Latency of exports",
"timestamp": "Oct \u003cvar data-var='date'\u003e28\u003c/var\u003e, \u003cvar data-var='time'\u003e18:00\u003c/var\u003e - \u003cvar data-var='time'\u003e18:00\u003c/var\u003e CET"
},
{
"code": "nrcn8nscw8qd",
"impact": "critical",
"message": "This incident has been resolved.",
"name": "AWS Outage Impacting Funnel Availability",
"timestamp": "Oct \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e11:57\u003c/var\u003e - Oct \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e09:51\u003c/var\u003e CEST"
},
{
"code": "p3swffw9lwjq",
"impact": "none",
"message": "The incident affecting Facebook Ads data imports that began on July 17th has now been resolved ✅\n\nOver 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.\n\nThroughout 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.\n\nA 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.\n\nWe 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.",
"name": "Facebook Ads Intermittent Data Delays",
"timestamp": "Jul \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e14:54\u003c/var\u003e - Oct \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e16:49\u003c/var\u003e CEST"
},
{
"code": "z5lhlrh07sgs",
"impact": "none",
"message": "As the errors have yet to resurface, we believe this to be resolved.",
"name": "Quora – Delayed imports",
"timestamp": "Oct \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e15:05\u003c/var\u003e - Oct \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e16:37\u003c/var\u003e CEST"
}
],
"name": "October",
"year": 2025
}
],
"start_time": "2025-10-01T00:00:00+02:00",
"time_zone": "Stockholm"
}
]
}