· Music won’t play or issues with my library
· Streaming tracks greyed out or unavailable
· Qobuz-Tracks won't play
· Router has no impact ... since RoonARC shows the same behaviour...
@Timo_B_Schluessel, welcome to the Roon community.
I have merged your post into this thread since this is a known issue.
· Music stops playing unexpectedly
· *All of my Zones* are affected.
· The issue affects *multiple/all* file formats.
· *Only streaming* music is affected.
· Qobuz
· Logging out and back in had no impact, the issue remains
· Problem occurred April 5, 2026. Examples are Second movement of Brahms Violin Concerto in D, violin soloist Janine Jansen, released Nov 13, 2015 and Third movement of Beethoven Violin Concerto in D, violin soloist Midori, released Oct 14, 2020. Problem tracks will play using the Qobuz app on a Windows 11 computer. I just noticed that the high res version of another problem track did not play in Roon but the available (in this case) CD quality track did play.
· Nucleus One connected to Unifi Dream Machine Pro router and 2 Watson Madison Streaming Dacs connected with balaced cables to 2 Moon integrated amps
Roon streams music from Qobuz to 2 Madison Streaming Dacs connected by balanced cables to Moon integrated amps. Classical Compositions (multiple tracks) quit because some tracks will not play. Examples are Second movement of Brahms Violin Concerto in D, violin soloist Janine Jansen, released Nov 13, 2015 and Third movement of Beethoven Violin Concerto in D, violin soloist Midori, released Oct 14, 2020. Problem tracks will play using the Qobuz app on a Windows 11 computer. I just noticed that the high res version of another problem track did not play in Roon but the available (in this case) CD quality track did play.
Nucleus One connected to Unifi Dream Machine Pro router and 2 Watson Madison Streaming Dacs connected with balaced cables to 2 Moon integrated amps
· The queue is skipping tracks
· *All of my Zones* are affected.
· The issue affects *multiple/all* file formats.
· *Only streaming* music is affected.
· Qobuz
· Logging out and back in had no impact, the issue remains
· Just now. 20.00
· Macbook Air '25
Some tracks wont play, but I checked Qobuz and Lightning and they are fine. I tried logging out, restarting the modem/internet etc and it didn't make any difference.
Asus
There is a known, ongoing issue with Qobuz that leads to unplayable tracks. This affects predominantly (but not always) 3rd-party services. Qobuz and Roon are working on this. The relevant official tracking thread for this issue is pinned to the top of the Support category and the latest update is this:
Previously, the issue also made Roon unresponsive because it couldn’t recover if it encountered such an unplayable track. This part was fixed in a recent Roon update. Make sure to update to the latest Roon version:
Oh please Qobuz, this has gotten really tiring and frustrating. Please fix this.
I don’t have any other streaming service. This is what I use.
The latest Roon update 2.64 (build 1646) has not completely resolved all the issues with playing tracks from Qobuz sources.
I had a track that paused after 6:33 of playback and would not continue, at least when something can’t play it skips to the next one and doesn’t stop playback altogether as prior to this update. Thanks for that. I’ll keep an eye on this thread.
I have 3 zones wired to different Mesh nodes and one USB zone from the Asus 13 pro i7 NUC R.O.C.K streaming concurrently from Qobuz playlists via Roon so I have a good control base.
Did you read the release notes? The latest Roon update doesn’t claim to resolve Qobuz issues, because it’s still a Qobuz backend issue, one that Qobuz needs to fix. All that the Roon update does is handle Qobuz failure more gracefully, by advancing to the next track from a failed one, instead of hanging indefinitely. That’s all it claims to do, and that is indeed what it does now.
I wasn’t expecting all the Qobuz playback issues to be resolved, only that now the tracks that won’t play are now being skipped which is better, basically I was only providing my observations. I had not had a track pause mid playback before now, and the tracks that are skipping are sometimes the same or different than the ones what would not play before. Totally understand that it is the Qobuz source API related & not a Roon issue.
I’m happy that the playback queue is no longer interrupted other than when MacArthur Park paused @ 6:33 mins and would not continue.
Well it is still not fixed, Qobuz probably thinks that customers are just an annoying side effect of the streaming business. We should be compensated for all the trouble they cause. for it is not the first major incident, it is one of many. Trying to contact Qobuz is an effort without reaction. Maybe that is the French way?
· None of the above quite fits
· None of these quite match
· After the latest update my playlists continue to re-start the song I selected and does not continue to the next song.....
· I got Rock running without problems since I installed Roon.
The problem started after I installed the update on 7 April.
Playlist only uses the song you selected and does not continue with the next songs. Tried to use the same playlist on Qobuz without problems. Help!
I’m experiencing the same issues.
Now tracks that got stuck are just being skipped.
It happens very frequently and almost on any album I play there’s at least one track that skips.
No issues when playing them from Qobuz directly or though Qobuz Connect.
Very frustrating.
At least I have Tidal to compensate for these skipped tracks.
Skipping the files that cannot be reach is better than the infinite loop.
But I consider this has a patch since the QoBuz app is using the same api call is able to play all the tracks without any issues.
Skipping track should not be the final solution. That issue need to be fix fast and consider a high priority.
The issue is upstream from Roon, and is caused by changes Qobuz made to their infrastructure. Roon issued an update to gracefully deal with this underlying issue, but it was never conveyed as a fix.
It apparently is NOT just a Qobuz issue. I’m now seeing the exact same thing when trying to play music from Tidal via Roon.
While I most certainly could be wrong, this appears to be a Roon issue and I just got off the phone with a friend and he is having the same thing.
Maybe Roon is trying to emulate Microsoft such that every new update creates new issues. I built my room to play music, and not debug other folks software. Time to start looking for another streaming device that works.
—————
[Moderator note: Support request submitted…]
Then the issue you are experiencing is a different issue. The one in this thread is definitely a Qobuz issue.
I’d recommend that you head to the Support category and open a new tech support request by clicking Get Help
SYMPTOM
My streaming client (Roon Server 2.64 build 1646, running on Ubuntu Server 24.04) logs show repeated “UnrecoverableError” failures in Roon’s internal streaming cache (FTMSI-B) when attempting to fetch the initial data block (block 0) from your Akamai CDN. Errors have been logged hundreds of times per day across multiple weeks. Playback typically self-heals after one or two retries, but results in audible track skips.
-–
DIAGNOSTICS COMPLETED
1. Network path analysis (MTR, 100 cycles)
Zero packet loss end-to-end. Final Akamai edge node responds at a consistent 9-10ms with minimal jitter. The network path is completely clean.
2. DNS resolution
All three resolvers tested — local Unbound, Google (8.8.8.8), and Cloudflare (1.1.1.1) — consistently return identical IPs: 23.205.165.70 and 23.205.165.72 . DNS is functioning correctly and geo-routing me to the appropriate Miami-area edge node for my location.
3. Traffic shaping / QoS
No egress traffic shaping configured on the Roon Server host. Default fq_codel qdisc only.
4. Firewall / IDS
OPNsense with Suricata IPS — no Suricata alerts for Qobuz or Akamai traffic. Ruled out as a factor.
5. Roon version
Running current release (2.64 build 1646, updated April 1st). Errors predate this update, going back to at least March 28th — the oldest logs available.
-–
KEY FINDING: STRONG TIME-OF-DAY PATTERN
Analysis of 20 Roon log files covering March 28th through April 6th reveals a clear and consistent pattern:
- Sessions running overnight (approximately 01:00-09:00 ET): ZERO streaming errors, despite tens of thousands of active Qobuz CDN requests
- Sessions running during daytime and evening hours: Hundreds of UnrecoverableError failures per session
Specific example: A log file covering April 3rd 01:13 through 09:34 (over 8 hours of active Qobuz streaming, 54,000+ CDN-related log entries) recorded zero errors. Log files covering daytime sessions on the same and adjacent days recorded 82-204 errors each.
Network conditions, DNS resolution, server configuration, and Roon version are identical between the clean overnight sessions and the error-filled daytime sessions. The only variable is time of day.
This pattern is strongly consistent with peak-hour congestion or capacity constraints on the Miami-area Akamai edge node (a1094.dscv.akamai.net, 23.205.165.70/72) that serves Florida customers.
-–
REQUEST
I would ask that your engineering or CDN operations team investigate the capacity and performance of the a1094.dscv.akamai.net edge node during peak daytime hours (approximately 09:00-23:00 ET), specifically for initial block (block 0) fetch latency and timeout rates for Florida-region customers.
I am happy to provide full Roon log excerpts or any additional diagnostic output if it would help your investigation.
Thank you for your attention to this.
Qobuz uses Akamai, and there is a known issue affecting their service, and subsequently Roon. I shall merge your post with the primary thread.
Moreover, I’d be grateful if you do not piggyback on someone else’s support request when your issue is unrelated to theirs. Thank you.
I’ve got the same issue regarding some tracks on Qobuz that won’t load and play thru ROON, I’m somewhat surprised that the issue is with Qobuz since the same tracks are playing normally thru Qobuz in my car…
