Update - Our team is actively working with X to address all known issues and is closely monitoring the situation. We will continue to provide updates as soon as new information becomes available.
Thank you for your patience and understanding while we are working on this
May 05, 2026 - 12:47 EEST
Update - Our team is actively monitoring the situation. As soon as we receive any new information or updates from X, we will share them promptly.
Thank you for your patience and understanding while we’re working on this.
Apr 29, 2026 - 10:46 EEST
Update - We were informed by X that they had already deprecated multiple sets of metrics to align with the Ad Manager UI. They are also still working to restore some functionality to the API, which means some fields don’t work at the moment.
To help keep you informed about these field deprecations and known broken functionality, we put a guide together and will update it as things evolve.
Thank you for your patience and understanding!
Apr 24, 2026 - 13:26 EEST
Update - We’re continuing to monitor the fixes deployed on Monday. While improvements have been observed, some issues are still being reported and may not yet be fully resolved.
We’ve also received an update from X API support indicating that certain reporting elements are still being restored on their side, with an expected resolution by the end of the week.
We are currently evaluating the impact of these changes from X API towards our X connectors and will provide a more comprehensive update as we learn more.
We appreciate your patience and understanding!
Apr 22, 2026 - 09:41 EEST
Monitoring - We’ve rolled out fixes that appear to have resolved the missing data issue. We’re continuing to monitor the situation closely to confirm whether this has also addressed the remaining discrepancies. We’ll share further updates within the next 24 hours.
Thank you for your patience and understanding!
Apr 20, 2026 - 13:49 EEST
Update - We have identified the root cause and implemented an initial fix, resolving the issue for some affected queries. We are still working on a complete resolution and will update you once we've restored full data accuracy.
Thank you for your understanding.
Apr 20, 2026 - 05:20 EEST
Identified - After thorough investigation of reports regarding missing campaign data and discrepancies in certain metrics when compared directly to the Ad Manager platform, we have determined that the issue is stemming from X’s API. The timeline seems to suggest the issue arose when X made changes to their Ad Manager UI.
We are in active communication with X and awaiting a technical fix from their side to restore full data accuracy and are monitoring the situation closely.
We will update you as soon as we know more.
Thank you for your understanding.
Apr 17, 2026 - 11:03 EEST
Update - We are writing to provide an update on the ongoing technical issue. We have been in consistent contact with the team at X, and they have confirmed that the root cause originates within their API environment.
While the fix must be implemented on their end and are actively working on it, we are still tracking the situation closely and monitoring our systems for any changes in behaviour. We are committed to keeping you informed and will provide an update the moment new information becomes available.
Thank you for your continued patience!
Apr 21, 2026 - 13:56 EEST
Update - We are writing to share an update regarding recent changes in X’s API behavior that may be affecting your experience. Some users are currently receiving a 'no data' notification when running queries via our X Organic connector. This is a deviation from previously reported errors and is due to a change in the API’s response behaviour.
After a thorough investigation, we have identified that the root cause is stemming from X’s API. While we are working diligently to advocate for a swift resolution with their team, the final fix must be implemented on their end.
We have escalated the issue to the team on X’s side and are awaiting action from their side and we will of course update you as soon as we know more.
Thank you for your continued patience and understanding as we address this issue.
Apr 14, 2026 - 13:58 EEST
Identified - Our engineering team has confirmed that the current service degradation originates from X’s API, as suggested by our initial findings.
While we are actively exploring potential workarounds to mitigate the impact, the primary resolution requires action from X’s development team. We are monitoring the situation closely and will provide immediate updates should the performance stabilize or if a viable internal solution is identified.
We appreciate your continued patience as we address this issue.
Apr 10, 2026 - 14:49 EEST
Investigating - We are currently investigating a performance degradation within the X Organic connector that began on April 10 at 00:00 AM UTC.
This issue is specifically impacting the "Tweet engagements" report type. You may encounter the following error message: “Query failed: Could not process the query. Please try again later.”
Our engineering team is actively working on exploring potential workarounds to restore full functionality, but initial investigation indicates the error is stemming from X’s API.
We will provide further updates as soon as more information becomes available. Thank you for your patience while we resolve this.
Apr 10, 2026 - 11:33 EEST
Supermetrics
Operational
Supermetrics Status
Operational
Supermetrics Hub
Operational
Supermetrics Website
Operational
Data destinations
Operational
Supermetrics for Looker Studio
Operational
Supermetrics for Google Sheets
Operational
Supermetrics for Excel
Operational
Supermetrics API
Operational
Supermetrics for BigQuery (marketplace)
Operational
Resolved -
Following a 24-hour monitoring period, we're no longer seeing any issues with The Trade Desk connector, and the previously reported errors are no longer occurring. We're considering this incident fully resolved.
If you're still experiencing any related issues, please don't hesitate to reach out to our Support team.
Thank you for your patience as we worked to resolve this disruption.
May 22, 14:33 EEST
Monitoring -
Following careful monitoring, we're seeing a return to normal operations on The Trade Desk connector.
Permission-related errors should no longer appear, and we'll continue to closely monitor the connector's behaviour over the next 24 hours to ensure stability.
If you're still experiencing any issues, please don't hesitate to reach out to our Support team.
Thank you for your patience and understanding throughout this incident.
May 21, 15:29 EEST
Investigating -
We're currently investigating reports of an issue affecting The Trade Desk connector. The Trade Desk's API is currently returning permissions-related errors, which prevents data from being retrieved successfully via our connector.
Affected users may see error messages such as "Login failed. Missing required partner-level reporting permissions", "Couldn't validate data access eligibility. Please re-authenticate to fix the issue.", or similar permission-related messages.
Our team is actively investigating the root cause and working to identify a resolution. We'll share an update as soon as we have more information.
Thank you for your patience while we look into this.
May 21, 14:18 EEST
Resolved -
Following 24 hours of close monitoring, we're seeing a consistently high success rate and no further occurrences of the issue. We're considering this incident fully resolved.
If you're still experiencing any related problems, please don't hesitate to reach out to our Support team - we're happy to help.
Thank you for your patience throughout this disruption.
May 21, 13:46 EEST
Monitoring -
Our engineering team has deployed a fix to the underlying infrastructure, and initial indicators show that the issue has been resolved. We will continue to monitor the system closely over the next 24 hours to ensure stability and confirm full resolution.
We sincerely appreciate your patience and understanding while we worked to address this issue. If you continue to experience any problems, please don't hesitate to reach out to our support team.
May 20, 13:34 EEST
Investigating -
We are aware of an issue affecting customers running Power BI queries, which is returning the following error message:
"This query does not contain any columns with supported data types."
Additionally the navigator’s preview window will appear blank as a result of the same error.
Our engineering team is actively investigating the root cause and has prioritized this incident. We will share an update as soon as we have more information to report.
We appreciate your patience and apologize for any disruption this may be causing to your workflows.
May 20, 11:04 EEST
Resolved -
LinkedIn has resolved the issue on their end, and we have noted system metrics have returned to normal. This issue is now resolved.
May 20, 22:38 EEST
Update -
The issue is also affecting the LinkedIn Company Pages connector.
We will keep monitoring for any changes.
May 20, 16:02 EEST
Identified -
We're currently aware of an issue affecting requests to LinkedIn's API, which may cause timeouts and impact related workflows, including authentication.
This issue originates with LinkedIn's API and has been acknowledged on their official status page. Our team is actively monitoring the situation and will provide updates as the situation evolves.
We appreciate your patience and understanding while LinkedIn works to resolve this on their end.
May 20, 15:59 EEST