Roon ARC experiences severe lag and responsiveness issues on LTE (ref#0M55G9)

Support
1

What app are you having the slowness issue with?

· ARC

What kind of performance/speed issue are you experiencing?

· The app takes a long time to respond to commands

Please try to reboot your Roon Server

· No, the issue is still the same even immediately after a reboot

Please try to reboot your networking gear (Router/Switches/etc.)

· No, the issue is still the same even after a reboot

Is there any change in behavior if you try to navigate to Roon Settings -> Library and set both Background and On-Demand Audio Analysis to Throttled or Off?

· No, the issue is still the same

Does the issue happen on multiple Roon Remotes (controllers) or just one?

· I only have one Roon remote to test with

Please try to restart your Roon Remote (controller) app

· No, the issue is still the same even after a restart

What is the operating system of your Roon Remote (controller)?

· iOS

Reinstall Mobile Roon Remote App

· No, I am still having the issue even after reinstalling

Router Domain Name System (DNS) change

· I was able to change my router's DNS servers but it did not help

What is the operating system of your Roon Server host machine?

· Roon on a NAS (Synology, QNAP, ASUSTOR)

Describe the issue

Roon ARC often becomes extremely laggy and slow to respond. It can take anywhere from 2 seconds to 30 seconds for it to respond to a touch event. When trying to play music, it will sometimes start playing (several seconds after pressing the button) but stop after 10-20 seconds. Sometimes painstakingly enabling offline mode (this takes MINUTES with the slowness) makes things go fast again. But then after restarting ARC starts in offline mode and can be slow again. This happens most often when there is no Wi-Fi (only LTE connectivity).

Dear Roon Team, please understand that this is a deal-breaker. Roon ARC overall has an abysmal reliability record. It also sometimes refuses to start saying "There is an issue with your roon server" (there is no issue) and telling me to go to the Roon app to fix the issue (good luck with that if I'm abroad traveling). Disconnecting from the server and reconnecting again (logging in) magically fixes the issue for a while. This, together with the occasional slowness, means that I cannot count on ARC to work.

Dear Roon Team, you wrote "Our mission is to delight music lovers, and if there’s anything we could be doing better, we want to hear about it." — so you're hearing about it.

Describe your network setup

UniFi network equipment + routers, DiskStation running Roon server.

2

Having gone through the whole reporting process, my impression is that much of it does not apply to ARC at all, and some questions should have a “not relevant” answer (DNS servers are unlikely to cause ARC to stutter and lag).

3

Hello @Jan_Rychter ,

Thanks for reaching out. When the issue next occurs, please note the exact time + date of the occurace. We’ll enable ARC diagnostics to see if there is anything we can gather for clies.

Also, to check the server side, can you please use these instructions to access your Roon Server logs, upload a set to the below link, and let us know once uploaded?

https://workdrive.zohoexternal.com/collection/8i5239cc05950ac07456889838d9319545a82/external

4

Ok, I have just reproduced the issue by turning off Wi-Fi and starting ARC. It is 2026-01-06 19:09 CET (UTC+1). Hope this helps.

5

As for server logs, I have Roon installed on a Synology NAS. Unfortunately, your instructions do not show where the logs are located (the screenshot doesn’t show the full path anywhere); I tried to find them manually but was unable to.

6

Hi @Jan_Rychter,

Logs will be housed within the RoonServer folder that holds the database. This will commonly be RoonServerDB in File Station if you installed Roon using the standard Roon on NAS instructions for Synology.

7

Hi @Jan_Rychter,

Please let us know if we can assist further in gathering logs - unfortunately, our team is quite limited without this crucial information. Thanks!

8

This thread is now closing due to inactivity/lack of response. You can reactivate the conversation by simply submitting a new tech support request here if you require additional support.

Thank you!