Supermetrics Outage History

Supermetrics degraded · 3 active incidents View live status →

Supermetrics had 47 outages in the last 2 years totaling 1468h 49m of downtime — averaging 1.9 incidents per month.

There were 47 Supermetrics outages since May 28, 2024 totaling 1468h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.supermetrics.com

Critical May 20, 2026

Service disruption: LinkedIn Ads, May 20, 2026

Detected by Pingoru
May 20, 2026, 12:59 PM UTC
Resolved
May 20, 2026, 07:38 PM UTC
Duration
6h 38m
Affected: LinkedIn AdsLinkedIn Company Pages
Timeline · 3 updates
  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 →

Minor May 20, 2026

Service disruption: Power BI, May 20, 2026

Detected by Pingoru
May 20, 2026, 08:04 AM UTC
Resolved
May 21, 2026, 10:46 AM UTC
Duration
1d 2h
Affected: Supermetrics for Power BI
Timeline · 3 updates
  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 →

Minor April 22, 2026

Service disruption: BigQuery, April 22, 2026

Detected by Pingoru
Apr 22, 2026, 12:22 PM UTC
Resolved
Apr 22, 2026, 04:27 PM UTC
Duration
4h 5m
Affected: Supermetrics for BigQuery (Hub)
Timeline · 3 updates
  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 →

Minor April 2, 2026

Increased error rates with X Ads connector

Detected by Pingoru
Apr 02, 2026, 01:19 PM UTC
Resolved
Apr 02, 2026, 05:15 PM UTC
Duration
3h 55m
Affected: X Ads
Timeline · 3 updates
  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 →

Critical April 2, 2026

Service disruption in Google Sheets and Looker Studio

Detected by Pingoru
Apr 02, 2026, 07:27 AM UTC
Resolved
Apr 03, 2026, 12:27 PM UTC
Duration
1d 4h
Affected: Supermetrics for Looker StudioSupermetrics for Google Sheets
Timeline · 6 updates
  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 →

Critical March 26, 2026

Service disruption: X Organic March 26, 2026

Detected by Pingoru
Mar 26, 2026, 07:39 AM UTC
Resolved
Mar 30, 2026, 07:51 AM UTC
Duration
4d
Affected: X Organic
Timeline · 3 updates
  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 →

Minor March 23, 2026

Shopify Connector - Degraded Performance

Detected by Pingoru
Mar 23, 2026, 02:33 PM UTC
Resolved
Apr 02, 2026, 11:47 AM UTC
Duration
9d 21h
Affected: Shopify
Timeline · 5 updates
  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 →

Minor March 20, 2026

Service disruption: Looker Studio, March 20, 2026

Detected by Pingoru
Mar 20, 2026, 01:04 PM UTC
Resolved
Mar 20, 2026, 04:14 PM UTC
Duration
3h 9m
Affected: Supermetrics for Looker Studio
Timeline · 3 updates
  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 →

Minor March 6, 2026

Service disruption: Supermetrics Hub, March 6th, 2026

Detected by Pingoru
Mar 06, 2026, 01:28 PM UTC
Resolved
Mar 06, 2026, 01:36 PM UTC
Duration
8m
Affected: Supermetrics Hub
Timeline · 2 updates
  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 →

Critical March 4, 2026

Service Disruption: Instagram Insights, March 4th, 2026

Detected by Pingoru
Mar 04, 2026, 01:03 PM UTC
Resolved
Mar 06, 2026, 12:17 PM UTC
Duration
1d 23h
Affected: Instagram Insights
Timeline · 3 updates
  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 →

Major February 3, 2026

Service disruption: Google Analytics 4, February 3, 2026

Detected by Pingoru
Feb 03, 2026, 09:51 AM UTC
Resolved
Feb 05, 2026, 08:56 AM UTC
Duration
1d 23h
Affected: Google Analytics 4
Timeline · 5 updates
  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 →

Critical January 26, 2026

Service Disruption: Supermetrics Website (Pricing Page), January 26th, 2026

Detected by Pingoru
Jan 26, 2026, 12:54 PM UTC
Resolved
Jan 26, 2026, 01:31 PM UTC
Duration
37m
Affected: Supermetrics Website
Timeline · 2 updates
  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 →

Major January 26, 2026

Service Disruption: Google Analytics 4, January 26th, 2026

Detected by Pingoru
Jan 26, 2026, 09:28 AM UTC
Resolved
Jan 27, 2026, 12:17 PM UTC
Duration
1d 2h
Affected: Google Analytics 4
Timeline · 2 updates
  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 →

Minor December 10, 2025

Service disruption: Custom Data Import, December 10, 2025

Detected by Pingoru
Dec 10, 2025, 01:22 PM UTC
Resolved
Dec 10, 2025, 02:04 PM UTC
Duration
42m
Affected: Custom Data Import
Timeline · 4 updates
  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 →

Critical December 5, 2025

Service Disruption: Service Outage due to Cloudfare incident, December 5th, 2025

Detected by Pingoru
Dec 05, 2025, 09:11 AM UTC
Resolved
Dec 05, 2025, 04:10 PM UTC
Duration
6h 58m
Affected: Supermetrics for Looker StudioSupermetrics for Google SheetsSupermetrics HubSupermetrics for ExcelSupermetrics WebsiteSupermetrics APISupermetrics for BigQuery (marketplace)Supermetrics for SnowflakeSupermetrics for Azure SynapseSupermetrics for Azure StorageSupermetrics for Amazon RedshiftSupermetrics for Amazon S3Supermetrics for Google Cloud StorageSupermetrics UploaderSupermetrics for BigQuery (Hub)
Timeline · 3 updates
  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 →

Minor November 18, 2025

Service disruption: Impacted services due to Cloudflare incident, November 18, 2025

Detected by Pingoru
Nov 18, 2025, 12:53 PM UTC
Resolved
Nov 19, 2025, 07:53 AM UTC
Duration
19h
Affected: Supermetrics StatusSupermetrics for Looker StudioAdformSupermetrics for Google SheetsSupermetrics HubAdjustSupermetrics for ExcelAdobe AnalyticsSupermetrics WebsiteSupermetrics APIAdRollSupermetrics for BigQuery (marketplace)AdtractionSupermetrics for SnowflakeAffluentSupermetrics for Azure SynapseAhrefsSupermetrics for Azure StorageApple Public DataSupermetrics for Amazon RedshiftApple Search AdsSupermetrics for Amazon S3AwinSupermetrics for Google Cloud StorageBambuserSupermetrics UploaderBing Webmaster ToolsCampaign MonitorSupermetrics for BigQuery (Hub)CallRailCapterra PPCCapterra ReviewsClockifyCriteoCustom Data ImportFacebook AdsFacebook InsightsFacebook Political AdsFacebook Public DataG2 ReviewsGlassdoor ReviewsGoogle Ad ManagerGoogle AdSenseGoogle AdsGoogle Analytics 4Google AnalyticsGoogle BigQueryGoogle Campaign Manager 360Google Display & Video 360Google My BusinessGoogle Play ReviewsGoogle Search Ads 360Google Search ConsoleGoogle TrendsHarvestHubSpotIndeed ReviewsInstagram InsightsInstagram Public Data 2KlaviyoLinkedIn AdsLinkedIn Company PagesLiveIntentMailchimpMicrosoft AdvertisingMozOmnisendOptimizelyOutbrain Amplify APIPartnerizePiano Analytics (AT Internet)Pinterest AdsPinterest OrganicPinterest Public DataPiwik PROPrisjaktQuantcastQuora AdsRakuten AdvertisingReadpeakReddit AdsSearchmetricsSemrush AnalyticsSendinblueShopifySimplesatSmarpSnapchat MarketingSnowflakeSpotify AdsStackAdaptStripeTaboolaThe Trade DeskTikTok AdsTripadvisor ReviewsTumblr Public DataTwitter Public DataVimeo Public DataVKontakte Public DataX AdsX OrganicX PremiumYahoo DSPYahoo Native AdsYandex DirectYandex MetricaYelp ReviewsYextYouTube
Timeline · 3 updates
  1. investigating Nov 18, 2025, 12:53 PM UTC

    We’re aware of the Cloudflare incident and that it may be impacting Supermetrics’ services.

  2. monitoring Nov 18, 2025, 03:02 PM UTC

    A fix has been implemented, and we believe the incident is now resolved. We will continue to monitor for errors to ensure all services are back to normal. Please reach out to Support if you continue to experience any other issues. Thank you for your patience and understanding.

  3. resolved Nov 19, 2025, 07:53 AM UTC

    This matter is now considered resolved, and performance is fully restored. Thank you for your patience and understanding.

Read the full incident report →

Major November 4, 2025

Service disruption: Multiple data destinations, November 4, 2025

Detected by Pingoru
Nov 04, 2025, 01:30 PM UTC
Resolved
Nov 05, 2025, 02:45 PM UTC
Duration
1d 1h
Affected: Supermetrics for Looker StudioSupermetrics for Google SheetsSupermetrics for ExcelSupermetrics APISupermetrics for BigQuery (marketplace)Supermetrics for SnowflakeSupermetrics for Azure SynapseSupermetrics for Azure StorageSupermetrics for Amazon RedshiftSupermetrics for Amazon S3Supermetrics for Google Cloud StorageSupermetrics for BigQuery (Hub)
Timeline · 3 updates
  1. identified Nov 04, 2025, 01:30 PM UTC

    We are investigating an isolated incident causing erroneous "License Expired" notifications for valid customers across multiple data destinations. A fix has been deployed and is currently underway across the affected infrastructure. The impact is limited specifically to customers who encountered and reported this erroneous notification earlier today. Customers logging in now or executing queries are not affected by this incident and should experience normal service functionality. The estimated down time is estimated to be a maximum of an hour.

  2. monitoring Nov 04, 2025, 03:19 PM UTC

    The fix that we have deployed to all affected infrastructure has finished and we are seeing positive results back in our monitoring. In case you are still facing the error, please do not hesitate to reach out to our Support. We will monitor the issue for an additional 24 hours. Thank you for your patience and understanding.

  3. resolved Nov 05, 2025, 02:45 PM UTC

    After a monitoring period of 24 hours we have determined the issue is no longer reproducible and no new issues related to the deployment of the fix have been detected. We are confident the issue has been resolved, but in case you have any questions or are still experiencing issues related to this incident, please contact our Support team. Thank you for your understanding in this matter.

Read the full incident report →

Minor November 4, 2025

Service disruption: Instagram Insights, November 4, 2025

Detected by Pingoru
Nov 04, 2025, 12:31 PM UTC
Resolved
Nov 07, 2025, 11:20 AM UTC
Duration
2d 22h
Affected: Instagram Insights
Timeline · 3 updates
  1. identified Nov 04, 2025, 12:31 PM UTC

    Meta is currently experiencing an issue that is impacting our Instagram Insights connector. This issue causes the “Views” metric to return 0 for Reels. The issue has been flagged to Meta and we are awaiting their identification or solution of the root cause. We will closely monitor the issue and post any updates on our status page.

  2. monitoring Nov 06, 2025, 08:49 AM UTC

    A fix has been implemented by Meta and we are closely monitoring the results for any additional issues. To retrieve data for the "Views" field for Reels, kindly refresh the impacted queries or dashboard. For Data Warehouse products, please execute a backfill for the runs that were affected. Please reach out to Support in case you are still experiencing any issues or have any questions.

  3. resolved Nov 07, 2025, 11:20 AM UTC

    After a monitoring period, the issue caused by Meta that affected our Instagram Insights connector has been resolved. The Instagram Insights connector is now retrieving data for the “Views” field for Reels as expected. For any impacted date range where Views was reporting as 0, please refresh your impacted queries or dashboard or execute a backfill for any Data Warehouse solution. We are always available to assist you by contacting us through our Support team. Thank you for your understanding and patience.

Read the full incident report →

Minor October 24, 2025

Service disruption: Supermetrics Pricing page, October 23, 2025

Detected by Pingoru
Oct 24, 2025, 05:47 AM UTC
Resolved
Oct 24, 2025, 06:17 AM UTC
Duration
30m
Affected: Supermetrics Website
Timeline · 2 updates
  1. investigating Oct 24, 2025, 05:47 AM UTC

    We are currently investigating reports of an Internal 500 Error being returned when attempting to access the Supermetrics Pricing Page. This issue is limited to users in the JAPAC (Japan and Asia-Pacific) region only. Other regions are unaffected.

  2. resolved Oct 24, 2025, 06:17 AM UTC

    The fix has been successfully implemented and resolved. We're pleased to report that the Supermetrics pricing page is working now without any issues. This matter is now considered resolved, and performance is fully restored. Thank you for your patience and understanding.

Read the full incident report →

Minor October 1, 2025

Service disruption: Reddit Ads, October 1st, 2025

Detected by Pingoru
Oct 01, 2025, 07:04 AM UTC
Resolved
Oct 02, 2025, 08:08 AM UTC
Duration
1d 1h
Affected: Reddit Ads
Timeline · 3 updates
  1. investigating Oct 01, 2025, 07:04 AM UTC

    We are currently investigating a widespread issue affecting connections in the Reddit Ads connector. This is prompting the reauthentication process in certain cases, which always returns the errors “We couldn't connect to data source with your credentials: Data Source Error: Forbidden” or “Error: Reddit Ads failure (Insufficient authentication sсореs.)”. Our initial investigation is showing that these errors are affecting all queries made with the connector. As we determine the root cause of the incident, we are also exploring possible workarounds.

  2. monitoring Oct 01, 2025, 07:33 AM UTC

    A fix has been deployed by our team to mitigate the issue. You may be prompted with a new error “Error: Reddit Ads failure (Authentication failed (403 Forbidden): Please re-authenticate your connection due to recent Reddit Ads API permission changes.)” due to the application of this fix. Reauthenticating the connection should resolve this new error. We are closely monitoring any further issues, but please do not hesitate to reach out to our Support team in case the issue is insisting.

  3. resolved Oct 02, 2025, 08:08 AM UTC

    The fix has been successfully implemented and monitored. After confirming with customer feedback, we are pleased to report that no further issues have been observed. This matter is now considered resolved, and performance is fully restored. If you however are still experiencing issues or have any further questions, our Support team is available to assist you in any way possible. Thank you for your patience and understanding.

Read the full incident report →

Critical September 26, 2025

Service disruption: 9/26/2025 - Google Sheets sidebar requiring some users to enter Captcha

Detected by Pingoru
Sep 26, 2025, 04:59 PM UTC
Resolved
Sep 29, 2025, 02:29 AM UTC
Duration
2d 9h
Affected: Supermetrics for Google Sheets
Timeline · 4 updates
  1. investigating Sep 26, 2025, 04:59 PM UTC

    We are currently investigating an issue where some users are being asked to enter a Captcha code to launch the Google Sheets sidebar. If you have any questions, please reach out to our Support team at the link below. https://support.supermetrics.com/support/tickets/new

  2. identified Sep 26, 2025, 05:23 PM UTC

    The error causing some users to see a Captcha when launching the Supermetrics Sidebar has been traced back to an issue that is currently being investigated by Google. An issue tracker for the matter can be found here - https://issuetracker.google.com/issues/447566703?pli=1 We are continuing to work with our partners at Google to ensure this is resolved as swiftly as possible.

  3. monitoring Sep 26, 2025, 09:12 PM UTC

    While Google has not confirmed a fix, we have seen system performance return to normal. We have also noted many (non-Supermetrics) users on Google forums report a restoration of services. We are continuing to monitor closely for any updates. If errors continue for you, please alert our support team so that we can assist further.

  4. resolved Sep 29, 2025, 02:29 AM UTC

    Google has indicated that the issue should be resolved now. Please reach out to our Support team if you're still experiencing issues.

Read the full incident report →

Notice August 4, 2025

Security Notice: Unintended sharing of reports through Looker Studio

Detected by Pingoru
Aug 04, 2025, 04:25 PM UTC
Resolved
Sep 02, 2025, 10:02 AM UTC
Duration
28d 17h
Affected: Supermetrics for Looker Studio
Timeline · 2 updates
  1. identified Aug 04, 2025, 04:25 PM UTC

    We are currently aware of a data security related issue with Looker Studio where some users may see reports listed which are not related to their company. After initial investigation and collaboration with the Looker Studio team at Google, this has been confirmed to be a Google issue and unrelated to Supermetrics. We have found that this can occur for users who use any Looker Studio template (not just Supermetrics Templates) where when making a copy of the template if the new report is set to “public” visibility this report could appear for other users who made copies of the same template. We are currently actively working with our partners at Google to resolve this issue, but in the meantime we suggest checking your sharing settings for your Looker Studio dashboards and avoiding using the “public” sharing setting. The bug report we have submitted to Google can be found here - https://issuetracker.google.com/issues/436116937

  2. resolved Sep 02, 2025, 10:02 AM UTC

    We're pleased to inform you that Google has confirmed the resolution of the reported issue. Our team has also conducted testing from our side and we can confirm that the issue is no longer occurring. We hope this update clarifies the situation. For any additional questions or if you require further assistance, please feel free to reach out to our dedicated Support team.

Read the full incident report →

Minor July 14, 2025

Service disruption: Shopify connector

Detected by Pingoru
Jul 14, 2025, 03:24 AM UTC
Resolved
Jul 14, 2025, 04:00 AM UTC
Duration
35m
Affected: Shopify
Timeline · 2 updates
  1. investigating Jul 14, 2025, 03:24 AM UTC

    We're currently experiencing an issue with the Shopify connector affecting only Google Sheets and Looker Studio where the queries are failing. We are investigating this issue and will update you as soon as we know more. Thank you for your understanding and patience.

  2. resolved Jul 14, 2025, 04:00 AM UTC

    The issue was related to internal infrastructure, and it has been resolved now. Please reach out to our Support team in case you are still experiencing issues.

Read the full incident report →

Minor July 3, 2025

Service disruption: Prisjakt, July 3rd, 2025

Detected by Pingoru
Jul 03, 2025, 01:05 PM UTC
Resolved
Jul 04, 2025, 01:33 PM UTC
Duration
1d
Affected: Prisjakt
Timeline · 3 updates
  1. investigating Jul 03, 2025, 01:05 PM UTC

    We are currently investigating an ongoing issue with the Prisjakt connector. Prisjakt has made changes to the API on their side which has caused connectivity issues for our connector. We have reached out to Prisjakt to investigate and mitigate the issue. Our apologies for any inconvenience caused, we will in the meantime also investigate options for a workaround. Thank you for your patience in advance!

  2. monitoring Jul 03, 2025, 02:46 PM UTC

    After making adjustments and deploying these to our connector, the issue seems to have been resolved. We are actively monitoring for any issues but we have every indication that everything is currently in working order. Please reach out to our Support team in case you are still experiencing issues.

  3. resolved Jul 04, 2025, 01:33 PM UTC

    We have monitored the situation and have not detected or had reports of any additional issues. We therefore consider this matter to be resolved, but please do not hesitate to contact us through our Support team in case you are experiencing any issues. Thank you for your understanding and patience during this matter.

Read the full incident report →

Minor June 13, 2025

Service disruption: Microsoft Advertising, June 13, 2025

Detected by Pingoru
Jun 13, 2025, 04:34 PM UTC
Resolved
Jun 14, 2025, 12:03 PM UTC
Duration
19h 28m
Affected: Microsoft Advertising
Timeline · 3 updates
  1. investigating Jun 13, 2025, 04:34 PM UTC

    We are currently experiencing a partial degradation of the service where access tokens seem to invalidate after a short period of time. We are currently investigating this with priority and will update you as soon as we know more. Thank you for your understanding and patience.

  2. monitoring Jun 13, 2025, 09:34 PM UTC

    A fix has been deployed and we are currently monitoring the results.

  3. resolved Jun 14, 2025, 12:03 PM UTC

    The fix that was applied yesterday evening has shown to be effective and no further issues have been observed. This incident is now resolved. If you continue to experience any issues with authentication related to the Microsoft Advertising connector, please reach out to our Customer Support team.

Read the full incident report →