· Can’t reach my Server, remotes or ARC
· Other ARC issues
· When using Arc’s daily mix (Qobuz streaming as source), the first track plays with no problem, but all subsequent tracks buffer indefinitely.
· 1gbs fiber connection with Ethernet connected host. No VPN.
Thank you for your post.
Does this occur regardless of whether you’re using cellular data or WiFi?
Are you playing through CarPlay/Android Auto or are you using the phone system output (speakers, headphones, etc)?
Did this only start occurring recently?
We’ll watch for your reply and promptly respond. Thank you!
The issue occurs with WiFi and cellular connections.
It occurs using android auto and system output.
This has been an ongoing issue for about the last 6 months.
Please note the first song plays fully without any issues and as such I suspect the issue lays in metadata and not a playback device or network connectivity issue.
Hey @Matthew_Ten_Eyck,
Thanks for the additional information! If you could, please update all your Roon devices, including your remotes and Roon Server to the latest build. There have been meaningful fixes to discovery and connectivity in recent releases that may help here.
If updating doesn’t help, please reproduce the issue and share the specific track name the next time you experience the issue and we’ll review a fresh diagnostic report for additional analysis.
Thank you! 
Issue persists after updating to latest version of Roon.
When trying to play tracks from my “Genesis Mix” daily mix, the first two tracks play successfully, however the playback stops after there.
The next two tracks in the list (tracks 3 and 4 with 1 being the track at the top of the list) are “Leave it” by “Yes” and “Across the Universe (2021 Mix)” by” the Beatles”. These tracks generate a “poor connection” warning when playback is invoked as part of continuing the mix or by skipping to the next track.
Playback is however sometimes possible if invoked by selecting the track directly in the list after playback has already been attempted and failed.
The behavior is somewhat inconsistent except that the first track almost always plays without issue.
Hello @Matthew_Ten_Eyck.
Thank you for the update
To get this resolved, we need to provide our R&D team and Qobuz with a precise “log trail” to see exactly where the handshake is failing.
The next few times this happens, please record the following details for each failure:
With these specific “breadcrumbs,” our engineers can pull the diagnostic logs from your server and match them to the exact second the error occurred. This will allow them to see if the delay is happening within the Roon ARC app, your home server’s connection, or at the Qobuz API level.
Once we have 3 or 4 fresh examples, we’ll package everything up for a deep-dive analysis. Standing by for your next update!
Attempted using a 5g connection. All times stated are UTC -6.
13 May 2026 17:59 “Little wing” by Sting, Gill Evans
13 May 2026 18:02 “Good Times Roll” by The Cars
13 May 2026 18:03 “Salvation” by Elton John
13 May 2026 18:05 “The last DJ (Album Version)” by Tom Petty
Hello @Matthew_Ten_Eyck,
Thank you for providing those precise timestamps and track details. That level of detail is exactly what we look for.
Unfortunately, we are hitting a bit of a snag on our end. Your Roon Server’s diagnostic logs are currently not reaching our cloud servers, which means we aren’t able to automatically pull that data to see the exact point of failure during those timestamps.
I am reaching out to our R&D team right now to find out if there is an alternative method for us to manually extract these specific ARC-to-Qobuz logs from your setup.
While we wait for their input on the best way to retrieve your logs, it would be incredibly helpful to test a couple of network variables. Could you please let us know if you experience this exact same buffering behavior in either of these scenarios:
This will help us determine if the issue is tied specifically to how your mobile carrier is handling the Roon/Qobuz stream. Thank you for your continued patience while we work around this log issue!