AnyDesk Outage History

AnyDesk experienced a service degradation that made custom client builds for macOS temporarily unavailable through their Customer Portal due to issues with an upstream provider. The incident affected the generation of macOS custom builds specifically, while other platform builds remained unaffected. The service was fully restored after 27 minutes.

AnyDesk experienced an issue where users were unable to create MacOS custom builds through the Customer Portal. The incident was classified as minor and lasted approximately 1.5 hours before being resolved.

AnyDesk experienced a major outage affecting customers in Taiwan and Hong Kong due to networking issues with an upstream provider, lasting approximately 189.6 hours. To mitigate the impact, engineers rerouted affected customers to infrastructure in Japan while working on a permanent fix. The incident was resolved when customers in Taiwan and Hong Kong were successfully routed back to their original zone.

AnyDesk experienced service degradation in India due to issues with their upstream provider, impacting remote desktop sessions in the Indian zone for 14.9 hours. The incident affected the Asia region and was caused by problems outside of AnyDesk's direct control. The service was fully restored after working with the upstream provider to resolve the connectivity issues.

AnyDesk experienced a major network outage that affected all global regions including Africa, Americas, Asia, Australia, and Europe for 53 minutes. The outage prevented users from accessing AnyDesk's remote desktop services worldwide. The incident was resolved after the team implemented a fix and monitored the results.

AnyDesk experienced performance degradation that prevented the generation of custom client builds, making some custom builds temporarily unavailable through the Customer Portal. The incident lasted approximately 125 hours (about 5 days) from February 27 to March 4, 2026. The root cause was identified and a fix was implemented to resolve the issue.

AnyDesk experienced degraded performance in South America affecting the Americas region for 52.2 hours. The team identified the root cause and implemented a fix, which was then monitored before the incident was fully resolved.