Resolved -
Google has resolved the issue and we've seen system performance return to normal. This incident is now resolved.
Apr 3, 15:27 EEST
Update -
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.
Apr 2, 13:44 EEST
Update -
We are continuing to monitor for any further issues.
Apr 2, 11:22 EEST
Monitoring -
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.
Apr 2, 11:06 EEST
Update -
We are continuing to investigate this issue.
Apr 2, 10:29 EEST
Investigating -
We're currently experiencing issues that are impacting Supermetrics services in Google Sheets and Looker Studio.
Our teams are working to identify the problem.
Apr 2, 10:27 EEST
Resolved -
This incident is now resolved.
Apr 2, 20:15 EEST
Monitoring -
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.
Apr 2, 18:11 EEST
Investigating -
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.
Apr 2, 16:19 EEST
Resolved -
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.
Apr 2, 14:47 EEST
Monitoring -
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.
Apr 1, 12:04 EEST
Update -
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.
Mar 27, 15:45 EET
Identified -
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.
Mar 25, 10:22 EET
Investigating -
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.
Mar 23, 16:33 EET
Resolved -
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.
Mar 30, 10:51 EEST
Identified -
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.
Mar 26, 12:03 EET
Investigating -
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.
Mar 26, 09:39 EET
Resolved -
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.
Mar 20, 18:14 EET
Monitoring -
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.
Mar 20, 17:20 EET
Investigating -
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.
Mar 20, 15:04 EET