Is TeamViewer down?

We are currently experiencing an intermittent issue affecting the Normalized, Unmatched, and Software inventory pages within Inventory Insights. When loading these pages, a "No Data" message may be displayed. Our engineering team is actively working on a fix. We will provide a further update at 16:00 UTC.

We have identified the issue and a fix is currently being implemented. Please note there may be temporary disruptions to service and to 1E client connectivity during the fix window.

A fix has been deployed and validation confirms that data is now visible across all screens. We are continuing to monitor the platform over the weekend to ensure the issue remains resolve

We are continuing to investigate an issue affecting Software Inventory views, including Normalised Software and Source Inventory. Our engineering teams have implemented several changes aimed at improving database performance and have observed improvements in a number of affected environments. While service recovery has been seen for some customers, we are continuing to monitor the platform and validate the effectiveness of the mitigations. Some users may still experience intermittent issues or slower-than-expected performance while backend processing completes. We will provide a further update as soon as additional information becomes available. Engineers are working on this with the highest priority to ensure that platform stability returns to normal.

We are currently implementing a fix to address an ongoing service issue. During this work, customers may experience intermittent disruption to client connectivity and associated platform services. Our engineering teams are actively monitoring the implementation and working to minimise impact. We will provide a further update once the changes have been completed and service stability has been confirmed. Thank you for your patience and understanding.

The fix has been successfully implemented and service has now been restored. Following monitoring and validation, client connectivity and associated platform services are operating normally. We will continue to monitor the environment closely to ensure ongoing stability, but no further customer impact is expected at this time. Thank you for your patience while we worked to resolve this issue

We are investigating an issue affecting the DEX Platform licensing service. Affected environments are unable to retrieve licensing information, which prevents instructions from being executed on the platform and/or preventing access. Impact Single Tenancy and On-Premises environments are affected Users see the error: "Licence Error The system in unable to retrieve it's license information" when trying to log in Infrastructure logs show: VerifyActivationSignature: failed(3) If users are already in the platform Instruction execution is unavailable will be presented with Error Cannot retrieve licensing information. Please see log for details. Client connectivity is not affected Current Status Our engineering and support teams are actively investigating the root cause. An out-of-hours escalation has been triggered and the cloud engineering team has been engaged. We are working towards a resolution and will provide updates every two hours. Next Update We will provide the next update by 20:00 UTC on 27 June 2026.

We have identified the issue and teams are working towards a fix.

We have identified the root cause. The License.dll file that is used to communicate with the Licensing services has an embedded certificate, this certificate expired preventing the Coordinator service from starting. Our teams are working on the Hotfix We have resolved the issue with Single tenant SaaS Environments and have a manual fix to resolve On Prem customers prior to the hotfix being released. https://support.1e.com/portal/6/CUSTSUP/article/2668298242/Users%20are%20unable%20to%20login%20the%20Platform%20UI%20and%20the%20coordinator%20server%20will%20not%20start. Further updates will be provided 28/6/26 @10am

Our teams are busy creating suitable hotfixes for the DEX Platform. More information will be available shortly covering the various versions via the banner on the Support Portal. The manual fix is still available as the previous update The next update will be before 14:00 UTC

Our teams have created a hotfix and provided workarounds which are detailed in the following article depending on which version is being used. https://support.1e.com/portal/6/CUSTSUP/article/2668429367/Licensing.dll%20certificate%20expired:%20Users%20are%20unable%20to%20login%20to%20the%20Platform%20UI%20and%20the%20coordinator%20service%20will%20not%20stay%20running. We will continue to monitor the situation and provide an update by 13:00 UTC on Monday 29th June

Our teams are continuing work on hotfixes for the various supported versions. We have provided workarounds which are detailed in the following article depending on which version is being used. https://support.1e.com/portal/6/CUSTSUP/article/2668429367/Licensing.dll%20certificate%20expired:%20Users%20are%20unable%20to%20login%20to%20the%20Platform%20UI%20and%20the%20coordinator%20service%20will%20not%20stay%20running. We will continue to monitor the situation and provide an update by 14:00 UTC on Tuesday 30th June

This issue has now been resolved. Further details can be found here https://support.1e.com/portal/6/CUSTSUP/article/2668429367/Licensing.dll%20certificate%20expired:%20Users%20are%20unable%20to%20login%20to%20the%20Platform%20UI%20and%20the%20coordinator%20service%20will%20not%20stay%20running.

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.

This incident has been resolved.

We're currently experiencing issues with the TeamViewer Community platform, which is temporarily unavailable.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

A subset of our users are currently experiencing issues with downloading custom modules. Our engineers have not yet confirmed the underlying root cause and they are working on the identification. We will update our status page with new information as soon as possible.

This incident has been resolved.