Supermetrics Outage History

Started Aug 26, 2026, 11:14 AM UTC· resolved Aug 26, 2026, 11:14 AM UTC

1. resolved Aug 26, 2026, 11:14 AM UTC

   Resolved - This incident has been resolved. We've deployed a fix, and saving boards is now working normally again. If you're still experiencing any issues saving boards, please refresh your browser and try again, or reach out to our support team directly. Thank you for your patience while we worked through this.

Read the full incident report →

Started Aug 21, 2026, 12:08 PM UTC· resolved Aug 21, 2026, 01:08 PM UTC

1. investigating Aug 21, 2026, 12:08 PM UTC

   We are currently experiencing an issue with the Supermetrics Hub (hub.supermetrics.com) that may affect login and access. When attempting to access the Hub, you may see a "503 Service Unavailable" error. Our team is aware of the issue and is actively working on a fix. We will update you as soon as the issue is resolved. We apologize for the inconvenience.

2. monitoring Aug 21, 2026, 12:47 PM UTC

   The Supermetrics Hub (hub.supermetrics.com) is now recovering. We are continuing to monitor the situation. We apologize for the disruption and thank you for your patience.

3. resolved Aug 21, 2026, 01:08 PM UTC

   The issue with the Supermetrics Hub (hub.supermetrics.com) has been resolved. Login and access are now working normally. We apologize for the inconvenience and thank you for your patience.

Read the full incident report →

Started Aug 06, 2026, 09:11 AM UTC· resolved Aug 07, 2026, 07:48 AM UTC

1. investigating Aug 06, 2026, 09:11 AM UTC

   We're aware of an issue affecting the Shopify connector where queries selecting multiple stores return data for only a single store ID, and the returned data is incorrect. Our team is actively investigating the root cause and will post updates here as we learn more. Thank you for your patience and understanding!

2. monitoring Aug 06, 2026, 11:03 AM UTC

   We have applied a fix to resolve this issue. For customers using Google Sheets, Data Studio, Excel or Power BI destinations, please refresh or re-run your queries to confirm that data is now returning correctly for all your stores. For customers using Data Warehouse destinations, we're scheduling backfills for the affected period to correct any historical data impacted during this window. We'll follow up once these backfills are complete. We're continuing to monitor the situation closely. If you're still experiencing issues after refreshing, please reach out to us and we'll take a closer look. Thank you for your patience while we worked through this!

3. resolved Aug 07, 2026, 07:48 AM UTC

   This incident has been resolved. Our fix has been confirmed to work and is fully deployed. Thank you for your patience while we worked through this.

Read the full incident report →

Started Jul 30, 2026, 08:30 PM UTC· resolved Jul 30, 2026, 10:03 PM UTC

1. investigating Jul 30, 2026, 08:30 PM UTC

   Supermetrics is currently experiencing service issues affecting our Data Studio destination. Some users may see a "No accounts found for the selected team" error when adding or reconnecting a data source, even though their accounts and authentication are otherwise working normally. Our teams are working to identify the problem

2. monitoring Jul 30, 2026, 09:07 PM UTC

   We've deployed a fix to resolve the service issues affecting Data Studio connectors and are closely monitoring the situation.

3. resolved Jul 30, 2026, 10:03 PM UTC

   Our team has monitored the deployed fix and the issue is now resolved for Data Studio connectors. If you have any questions or are still experiencing issues, please contact our support team.

Read the full incident report →

Started Jul 28, 2026, 02:06 PM UTC· resolved Jul 28, 2026, 03:27 PM UTC

1. identified Jul 28, 2026, 02:06 PM UTC

   We have identified a recent update to the Yahoo DSP connector that is causing queries to fail for some customers with the error “idb2b oauth2 authentication disabled”. We have isolated the root cause of this and are currently working on a fix.

2. resolved Jul 28, 2026, 03:27 PM UTC

   We have deployed a fix and seen system metrics return to normal. This incident is now resolved.

Read the full incident report →

Started Jul 24, 2026, 09:57 PM UTC· resolved Jul 29, 2026, 08:38 AM UTC

1. investigating Jul 24, 2026, 09:57 PM UTC

   We are aware of an issue affecting scheduled refreshes (automatic triggers) in Supermetrics for Google Sheets. Affected users may see "Refresh failed: Please contact support" with a status of "Unable to connect" in the Manage Schedules panel. Manual refreshes from the sidebar continue to work normally. Our engineering team is actively investigating the root cause. We will provide an update as soon as we have more information.

2. resolved Jul 29, 2026, 08:38 AM UTC

   We've deployed a fix for the issue affecting scheduled Google Sheets refreshes and have confirmed that refreshes are completing normally. The root cause was identified as increased latency for triggers scheduling, which caused some runs to time out and fail. This incident is now resolved. If you continue to experience issues with a scheduled refresh, please contact support and reference this incident. Thank you for your patience and understanding!

Read the full incident report →

Started Jun 03, 2026, 02:50 PM UTC· resolved Jun 04, 2026, 05:46 AM UTC

1. investigating Jun 03, 2026, 02:50 PM UTC

   We're aware of an issue currently affecting the Shopify connector around authentication and queries, resulting in an error "The requested resource could not be found” This issue originates with Shopify’s API and we're communicating with them for a resolution on this. Our team is actively monitoring the situation and will provide updates as the situation evolves. We appreciate your patience and understanding while the issue is being addressed.

2. monitoring Jun 03, 2026, 04:24 PM UTC

   We have an update that Shopify has resolved this issue on their end and the connector functionality should be back to normal. We will continue to monitor the system closely over the next 24 hours to ensure stability and confirm full resolution. Thank you for your patience. If you continue to experience any problems, please don't hesitate to reach out to our support team.

3. resolved Jun 04, 2026, 05:46 AM UTC

   After monitoring the situation and confirming the fix on Shopify's end, we're happy to report this issue is now resolved. If you're still experiencing any problems, please do not hesitate to reach out to our Support team. Thank you for your patience, and we apologize for any inconvenience this may have caused.

Read the full incident report →

Started May 21, 2026, 11:18 AM UTC· resolved May 22, 2026, 11:33 AM UTC

1. investigating May 21, 2026, 11:18 AM UTC

   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.

2. monitoring May 21, 2026, 12:29 PM UTC

   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.

3. resolved May 22, 2026, 11:33 AM UTC

   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.

Read the full incident report →

Started May 20, 2026, 12:59 PM UTC· resolved May 20, 2026, 07:38 PM UTC

1. identified May 20, 2026, 12:59 PM UTC

   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.

2. identified May 20, 2026, 01:02 PM UTC

   The issue is also affecting the LinkedIn Company Pages connector. We will keep monitoring for any changes.

3. resolved May 20, 2026, 07:38 PM UTC

   LinkedIn has resolved the issue on their end, and we have noted system metrics have returned to normal. This issue is now resolved.

Read the full incident report →

Started May 20, 2026, 08:04 AM UTC· resolved May 21, 2026, 10:46 AM UTC

1. investigating May 20, 2026, 08:04 AM UTC

   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.

2. monitoring May 20, 2026, 10:34 AM UTC

   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.

3. resolved May 21, 2026, 10:46 AM UTC

   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.

Read the full incident report →

Started Apr 22, 2026, 12:22 PM UTC· resolved Apr 22, 2026, 04:27 PM UTC

1. investigating Apr 22, 2026, 12:22 PM UTC

   We’ve received multiple reports of duplicated rows/data appearing within the refresh window for BigQuery destinations. Our team is currently investigating the issue and working to identify the root cause. We’ll provide further updates as soon as more information becomes available. Thank you for your patience and understanding!

2. investigating Apr 22, 2026, 04:17 PM UTC

   This issue has now been resolved. Any affected runs have been re-ran to remove any duplicate rows.

3. resolved Apr 22, 2026, 04:27 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 17, 2026, 08:03 AM UTC· resolved Jun 02, 2026, 02:36 AM UTC

1. identified Apr 17, 2026, 08:03 AM UTC

   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.

2. identified Apr 20, 2026, 02:20 AM UTC

   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.

3. monitoring Apr 20, 2026, 10:49 AM UTC

   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!

4. monitoring Apr 22, 2026, 06:41 AM UTC

   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!

5. monitoring Apr 24, 2026, 10:26 AM UTC

   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. Please see the guide here: https://docs.supermetrics.com/docs/x-ads-twitter-field-changes-april-29-2026 Thank you for your patience and understanding!

6. monitoring Apr 29, 2026, 07:46 AM UTC

   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.

7. monitoring May 05, 2026, 09:47 AM UTC

   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. The Data Warehouse standard table group will be updated on May 7, 2026. For more details and upcoming updates, please check out public article: https://docs.supermetrics.com/docs/x-ads-twitter-field-changes-april-29-2026 Thank you for your patience and understanding while we are working on this

8. resolved Jun 02, 2026, 02:36 AM UTC

   While we are still working with X to resolve some known issues, the X Ads connector is stable enough to consider this resolved. If you are affected by the known issues - such as demographic segments or reach fields not working- please watch our known issues guide: https://docs.supermetrics.com/docs/x-ads-twitter-field-changes-april-29-2026. We will post updates to the article as these issues are resolved. If you are still experiencing discrepant data, especially with data around late March/early April, please reach out to our support team. Thank you for your patience throughout this disruption.

Read the full incident report →

Started Apr 10, 2026, 08:33 AM UTC· resolved Jul 22, 2026, 09:26 AM UTC

1. investigating Apr 10, 2026, 08:33 AM UTC

   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.

2. identified Apr 10, 2026, 11:49 AM UTC

   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.

3. identified Apr 14, 2026, 10:58 AM UTC

   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.

4. identified Apr 21, 2026, 10:56 AM UTC

   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!

5. resolved Jul 22, 2026, 09:26 AM UTC

   We are writing to confirm that the technical issue with X Organic connector has now been resolved. After our continued monitoring and follow-up with X, we can confirm the issue has been addressed on their end. Our systems are showing normal behavior and data is flowing as expected. If you are still experiencing any issues, please don't hesitate to reach out to our support team. Thank you for your patience throughout this process!

Read the full incident report →

Started Apr 02, 2026, 01:19 PM UTC· resolved Apr 02, 2026, 05:15 PM UTC

1. investigating Apr 02, 2026, 01:19 PM UTC

   We are aware of elevated error rates with the X Ads API which is affecting the X Ads connector. We are currently monitoring the situation closely and will provide updates as soon as they are available.

2. monitoring Apr 02, 2026, 03:11 PM UTC

   Success rates with the X Ads connector have returned to normal. We are continuing to monitor the connector closely to ensure there are no further issues.

3. resolved Apr 02, 2026, 05:15 PM UTC

   This incident is now resolved.

Read the full incident report →

Started Apr 02, 2026, 07:27 AM UTC· resolved Apr 03, 2026, 12:27 PM UTC

1. investigating Apr 02, 2026, 07:27 AM UTC

   We're currently experiencing issues that are impacting Supermetrics services in Google Sheets and Looker Studio. Our teams are working to identify the problem.

2. investigating Apr 02, 2026, 07:29 AM UTC

   We are continuing to investigate this issue.

3. monitoring Apr 02, 2026, 08:06 AM UTC

   We’re now seeing normal system behavior. Preinstalled add-ons are launching as expected, and script execution performance has returned to normal. We will continue to monitor closely.

4. monitoring Apr 02, 2026, 08:22 AM UTC

   We are continuing to monitor for any further issues.

5. monitoring Apr 02, 2026, 10:44 AM UTC

   We’ve received a confirmation from Google that an issue on their side has impacted Google Sheets add-ons and Looker Studio extensions. They are actively working on a fix, and we will continue to monitor the situation closely in the meantime.

6. resolved Apr 03, 2026, 12:27 PM UTC

   Google has resolved the issue and we've seen system performance return to normal. This incident is now resolved.

Read the full incident report →

Started Mar 26, 2026, 07:39 AM UTC· resolved Mar 30, 2026, 07:51 AM UTC

1. investigating Mar 26, 2026, 07:39 AM UTC

   We are currently seeing failures affecting the X Organic connector. According to the X status page, there is an ongoing incident that started on March 24 at 02:00 UTC. Our internal monitoring confirmed this issue after we began observing a spike in failed requests today, starting at approximately 03:00 UTC. Connector queries may fail with the following error message: "Error: X Organic (Twitter) failure (Data Source Error: Service Unavailable)" We will share more details as soon as they are available. Our support team is available for any possible questions you may have. Thank you for your patience and understanding.

2. identified Mar 26, 2026, 10:03 AM UTC

   We’re seeing clear signs of recovery, with success rates improving and queries starting to function again. However, since the issue on X’s side is still ongoing, we’re continuing to monitor the situation before confirming full resolution.

3. resolved Mar 30, 2026, 07:51 AM UTC

   Following a period of monitoring, we’re pleased to confirm that the X Organic connector has fully recovered and is operating normally. We sincerely appreciate your patience and understanding while we worked to resolve the issue. If you have any questions or notice anything unexpected, please don’t hesitate to reach out to our Support Team - we’re here to help.

Read the full incident report →

Started Mar 23, 2026, 02:33 PM UTC· resolved Apr 02, 2026, 11:47 AM UTC

1. investigating Mar 23, 2026, 02:33 PM UTC

   We are seeing increased levels of the error "Your request could not be completed at this time. If you continue to see this message, please contact our support team with the date and time of the issue.(Supermetrics request ID: ). If you experience this error, please wait some time and try again. We are currently investigating this issue and will provide an update as soon as possible.

2. identified Mar 25, 2026, 08:22 AM UTC

   We have identified a cause of the reported issue. We will provide further updates as soon as the fix is live or as new information becomes available. We appreciate your continued patience and understanding as we work to resolve this permanently.

3. identified Mar 27, 2026, 01:45 PM UTC

   We are currently in the process of implementing a series of improvements that are aimed to enhance the stability of the connector and specifically mitigating any existing issues that are currently being experienced. We expect these enhancements to restore optimal performance once fully deployed. Our team is currently on track to complete the rollout early next week to ensure a seamless transition. We apologize for any inconvenience this might cause and we appreciate your understanding and patience as we work to resolve these issues.

4. monitoring Apr 01, 2026, 09:04 AM UTC

   We’ve rolled out a series of improvements to improve overall connector stability, and performance should no longer be affected by the recent issues. Our team is continuing to closely monitor the connector to ensure it remains fully operational. We apologize for any inconvenience this might cause and we appreciate your understanding and patience as we work to resolve this permanently.

5. resolved Apr 02, 2026, 11:47 AM UTC

   We're pleased to confirm that the issue affecting the Shopify connector has been resolved. We sincerely appreciate your patience and understanding while we worked to resolve the issue. If you have any questions or notice anything unexpected, please don’t hesitate to reach out to our Support Team - we’re here to help.

Read the full incident report →

Started Mar 20, 2026, 01:04 PM UTC· resolved Mar 20, 2026, 04:14 PM UTC

1. investigating Mar 20, 2026, 01:04 PM UTC

   We are currently experiencing an uptick in "Address Unavailable" errors in Looker Studio dashboards. Our team is fully engaged in diagnosing the root cause and is currently developing a fix to mitigate the impact. We will share more details as soon as they are available. In the meantime, please feel free to reach out with any specific questions. Thank you for your patience and understanding.

2. monitoring Mar 20, 2026, 03:20 PM UTC

   Our engineering team has successfully identified the root cause of the issue and a fix has been applied. We are currently monitoring the situation to ensure full stability. Should you continue to experience any issues, please don't hesitate to contact our support team.

3. resolved Mar 20, 2026, 04:14 PM UTC

   The issue causing "Address Unavailable" errors in Looker Studio dashboards has been resolved. Our engineering team identified the root cause, applied a fix, and has confirmed full stability through monitoring. If you continue to experience any issues, please contact our support team.

Read the full incident report →

Started Mar 06, 2026, 01:28 PM UTC· resolved Mar 06, 2026, 01:36 PM UTC

1. investigating Mar 06, 2026, 01:28 PM UTC

   We are currently experiencing performance degradation, resulting in slowness when accessing Supermetrics Hub. Our engineering team is actively investigating the issue to identify the root cause and implement a fix. We apologize for any inconvenience this may be causing and appreciate your patience. We will provide an update as soon as more information is available.

2. resolved Mar 06, 2026, 01:36 PM UTC

   The performance degradation affecting Supermetrics Hub has been resolved. Users should no longer experience slowness when accessing the platform. We apologize for any inconvenience this may have caused. Thank you for your patience.

Read the full incident report →

Started Mar 04, 2026, 01:03 PM UTC· resolved Mar 06, 2026, 12:17 PM UTC

1. investigating Mar 04, 2026, 01:03 PM UTC

   We are currently aware of an issue affecting our Instagram Insights data source. Customers have reported encountering the following error: “Unable to fetch data from profile xxx, the profile may no longer exist or the permissions have changed.” Our team is actively investigating the issue, and we will update with you as soon as more information becomes available. Thank you for your patience!

2. identified Mar 04, 2026, 05:04 PM UTC

   Our engineering team has investigated and identified that the issue appears to be caused by a bug on Meta’s side. We have reported this issue to Meta and will update here with any significant developments. Thank you for your patience and understanding!

3. resolved Mar 06, 2026, 12:17 PM UTC

   The issue affecting the Instagram Insights data source appears to be resolved and the situation has stabilized. Although we have not yet heard back from Meta regarding the bug ticket submitted yesterday, we've monitored and seen positive results as the problem is no longer impacting any of our customers. Based on this, we are marking the incident as resolved. We apologize for any inconvenience this may have caused. Thank you for your patience.

Read the full incident report →

Started Feb 03, 2026, 09:51 AM UTC· resolved Feb 05, 2026, 08:56 AM UTC

1. investigating Feb 03, 2026, 09:51 AM UTC

   We are currently experiencing reduced functionality with the Google Analytics 4 connector in multiple destinations. We are investigating this with priority to mitigate the impact and restore full functionality. We will update you as soon as we have more information. Thank you for your patience.

2. monitoring Feb 03, 2026, 10:03 AM UTC

   We have determined there was an issue within our infrastructure that made queries fail for Google Analytics 4. We have deployed a fix to mitigate the issue and are currently monitoring the situation to confirm there are no more errors occurring. We will monitor the situation for 24 hours. Thank you for your understanding.

3. identified Feb 03, 2026, 12:18 PM UTC

   We have identified a recurrence of the previously reported issue. Our technical team is currently finalizing a secondary resolution for deployment. We will provide further updates as soon as the fix is live or as new information becomes available. We appreciate your continued patience and understanding as we work to resolve this permanently.

4. monitoring Feb 03, 2026, 03:28 PM UTC

   We are pleased to report that the initial issue has been resolved, and system performance has returned to normal levels. Our team is currently monitoring the environment for the next 24 hours to ensure continued stability. A final permanent patch is scheduled for deployment in the short term to ensure long-term stability.. We sincerely appreciate your patience and continued support as we worked to resolve this matter.

5. resolved Feb 05, 2026, 08:56 AM UTC

   Following a period of extended monitoring, we can confirm that all systems have returned to normal and no further errors have been detected. We sincerely apologize for any inconvenience this may have caused. Should you have additional questions or experience any further disruptions, please do not hesitate to contact our Support Team. Thank you for your patience as we worked to resolve this issue.

Read the full incident report →

Started Jan 26, 2026, 12:54 PM UTC· resolved Jan 26, 2026, 01:31 PM UTC

1. investigating Jan 26, 2026, 12:54 PM UTC

   We are currently aware of an issue affecting the Supermetrics website, particularly the pricing page (https://supermetrics.com/pricing). Our team is actively investigating to identify the root cause and implement a fix. We will update this page as soon as we have more information. Thank you for your patience and understanding.

2. resolved Jan 26, 2026, 01:31 PM UTC

   We are pleased to inform you that the issue affecting our Pricing Page has been resolved. You can now view pricing information and purchase Supermetrics subscriptions as usual. We apologize for any inconvenience this may have caused and thank you for your patience.

Read the full incident report →

Started Jan 26, 2026, 09:28 AM UTC· resolved Jan 27, 2026, 12:17 PM UTC

1. investigating Jan 26, 2026, 09:28 AM UTC

   We are currently investigating a potential permission-related issue with our Google Analytics 4 connector. Some customers may encounter the following error when running Google Analytics 4-related queries or reports that include a filter on pagePath: “Error: Google Analytics 4 failure Your query returned a data fetch error: 403 – User does not have sufficient permissions for this property.” If you encounter this error, please try re-running your query or reducing the date range to see if it resolves the issue. We'll provide an additional update as soon as we have more information. Thank you for your patience and understanding.

2. resolved Jan 27, 2026, 12:17 PM UTC

   We are pleased to share a confirmed workaround for this issue: re-running your query with a reduced date range and removing today’s date from the range. This helps resolve this permission-related issue with our Google Analytics 4 connector. Please note that while this workaround is effective in most cases, it may not resolve the issue in all scenarios. Our team continues to work closely with Google to have the issue acknowledged and fully resolved on the API side. We apologize for any inconvenience this may have caused. If you continue to experience issues after applying the workaround, please reach out to our Support team, and we will be happy to assist you further. Thank you for your patience and understanding.

Read the full incident report →

Started Dec 10, 2025, 01:22 PM UTC· resolved Dec 10, 2025, 02:04 PM UTC

1. investigating Dec 10, 2025, 01:22 PM UTC

   We are currently experiencing an issue with some Custom Data Import functionality. All spreadsheet-formatted files (XLS, XLSX, XLSB, ODS) are currently failing when processing. CSV file processing continues to function normally, and querying of previously imported files is unaffected. We are investigating the root cause and potential workarounds and will provide an update as soon as possible. Thank you for your understanding and patience.

2. monitoring Dec 10, 2025, 01:51 PM UTC

   A fix has now been implemented, and our team is closely monitoring to confirm everything is operating as expected. Thank you for your patience and understanding.

3. monitoring Dec 10, 2025, 01:54 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Dec 10, 2025, 02:04 PM UTC

   The issue causing import failures has now been resolved. Since some files were not processed during the interruption, you may need to recover those files. To do this, please log in to the Supermetrics Hub and open Custom Data Import to identify any imports marked as failed. In case of failures, please follow these steps to recover the failed files: + Open the affected import. + Go to the Files tab. + Download the files that failed to process. + Re-upload the file to the import. If you need any help along the way, our team is here to support you.

Read the full incident report →

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

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

   We are currently experiencing a widespread service disruption across the Supermetrics platform due to an external incident with Cloudflare. This issue may cause failures or degraded performance in various areas of our service. We will update this page as soon as we know more.

2. monitoring Dec 05, 2025, 09:24 AM UTC

   Cloudflare has implemented a fix, and we are beginning to see Supermetrics services recovering. We will continue to monitor for errors to ensure all systems return to normal. If you continue to experience any issues, please reach out to Support. Thank you for your patience and understanding.

3. resolved Dec 05, 2025, 04:10 PM UTC

   Cloudflare has confirmed that their fix is working and that the incident has been resolved. You can find more details on Cloudflare's incident on their status page here: https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q If you continue to experience any issues, please reach out to Support. Thank you for your patience and understanding.

Read the full incident report →