Major incident
AnyDesk: Partial outage - Taiwan and Hong Kong
Apr 28, 2026, 11:20 UTC
started
08:51 UTC
resolved May 6, 2026
7 days 21 h
duration
Affected: Asia
Current status of AnyDesk: Operational — live AnyDesk status
Timeline
- Apr 28, 2026, 11:20 UTCinvestigatingWe are currently facing degraded performance in our Asia zone, specifically Taiwan and Hong Kong. Engineers are investigating and a further update will be provided once a root cause has been identified. We apologise for any inconvenience caused.
- Apr 28, 2026, 11:59 UTCidentifiedDue to networking issues associated with one of our upstream providers, to reduce customer impact we will be re-routing customers from Taiwan and Hong Kong to our infrastructure in Japan.
- Apr 30, 2026, 18:22 UTCidentifiedOur engineering teams continue to work on the issue
- May 6, 2026, 08:51 UTCresolvedThis incident has been resolved. Customers in Taiwan and Hong Kong are now routed back to their original zone.
Updates as published by AnyDesk (original).
Other services with incidents at the same time
- Contentful 11:59 UTC · Issues accessing spaces/environments in the Contentful web app
- Tenable 11:38 UTC · Vulcan Platform: Partial Service Disruption: Connector Triggers (EU)
- CloudAMQP 10:27 UTC · Backend slow/unresponsible
More AnyDesk incidents
- July 13, 2026 Outage - my.anydesk II
- June 27, 2026 Major outage - my.anydesk II
- June 16, 2026 REST API Outage
- May 22, 2026 Service Degradation - macOS Custom Client Builds