Is AnyDesk Down? Live status & outage reports

Service info and troubleshooting

Can't Connect to Remote Device

The most common reason is that the remote side isn't running the app or has it minimized without an active session. Check that AnyDesk is open on the target machine and that the displayed ID matches what you're typing. If the address field shows "Connecting..." indefinitely, the remote device may be behind a restrictive firewall — ask the other party to allow outbound connections on port 6568.

App Freezes or Crashes on Launch

This usually points to a corrupted installation or a conflict with antivirus software. Uninstall the client completely, clear leftover folders in AppData, then download a fresh build from the official site. If the crash persists, temporarily disable real-time protection — some endpoint security tools flag the remote-access process as suspicious and block it mid-launch.

High Latency and Laggy Sessions

• Close bandwidth-heavy applications on both ends before starting a session
• In Settings → Display, reduce color depth to "Optimize for speed"
• Switch from wireless to a wired connection if ping spikes are irregular
• Lower the remote screen resolution to cut the amount of data transmitted per frame

Black Screen Instead of Remote Desktop

The remote machine is likely running a full-screen app or a game in exclusive mode, which prevents screen capture. Ask the remote user to switch the app to windowed mode. On Windows, privacy mode may also be enabled — check Settings → Security on the remote side and turn it off.

Session Disconnects Randomly

Unstable sessions are almost always a network issue on one end. Run a continuous ping to a public DNS server on both machines to spot packet loss. If loss is above 2–3%, the problem is local infrastructure. Also check the power settings on the remote PC — sleep mode kicks in and drops the connection if the machine is left idle.

AnyDesk ID Not Generated

If the app shows no ID after launch, it failed to reach the discovery servers. Verify that your firewall isn't blocking the executable and that the service is actually running — on Windows, open Task Manager and look for the AnyDesk background process. Restarting the service through services.msc usually resolves this in seconds.