I have similar problems… Can I suggest ROON focuses research and development on sorting these matters that really downgrade end-user experience, rather than developing projects such as ARC which I personally am not interested in and cannot see the point of… 
3 Likes
I had similar ongoing for around 6 months and tried EVERYTHING with no change turns out it was my ISP something to do with their local cache settings. I was locked in a contract so couldn’t change ISP so had to deal with the usual denial etc. after 10 emails and no results I reached out to social media chat group related to that ISP and it was fixed in days. If I had the choice I would have simply researched a decent ISP and changed as it would have saved me a lot of agrovation.
hope this helps
1 Like
Rather than guessing what the problem is (OP has this problem before all the TP-Link network switches) can we try to gather some factual information about what the issue seems like?
- Grab any data on server when that happens. Has the RAAT flow de-synchronized? Has the player lost the connection ? Is there is issue with the source ? At least this will allow everyone to not throw ideas at where the problem is not.
- Ideally grabbing a sniffer trace - isolating that traffic - of when this happens. Using wireshark or tcpdump. There we can see if there is packet loss, or anything else like Spanning Tree.
I am not convinced that QoS - even poorly configured - has anything to do with this and I’d rather have “facts” over “stories”. OP has spent a significant amount of time documenting every detail, I want to help. Personally I have no issue at all, and I also have a NAIM Mu-so 2.
2 Likes
My first guess was also switches and router.
I have dumb TP-Link-gigabit-switches and my router is a FritzBox 6391, which is for cable.
Cat6 wiring at home - never any Roon trouble at all.
1 Like
Errrr why did Harman buy Roon. I don’t know?
I feel for you I really do - I’ve been struggling with similar for nearly four hundred years now. Just to say ChatGPT is surprisingly good at reading and interpreting the Roon logs. Hope that helps …
2 Likes
UPDATE. Firstly, as the integrity of network connection to my kitchen end point was questioned, I tested it with my ethernet cable tester and no faults were indicated.
I’ve replaced the the three network switches with NETGEAR GS 305 as recommended above. On starting up I had no dropouts in the Music room (promising) but when I moved to the kitchen, over 90 minutes there were 5 1-second dropouts and one lengthy dropout which didn’t restart without my intervention (not so promising). I then thought that, having pulled apart my network and rebuilt it with the new switches perhaps a full re-boot was required. So I powered off the whole network and attached units and left it unpowered for about an hour. After powering up, I also reinstalled the Roon software on my Nucleus One and restarted it. I had zero dropouts in the Music Room and, importantly, zero dropouts in the Kitchen. Lets see if repeats this performance this evening.
3 Likes
Hello @Geoff_Bishop,
Thank you for the update and for documenting your network overhaul so clearly. It’s encouraging to hear that the full network reboot and switch replacement to the Netgear GS305s (which are known for their transparency with Roon) resulted in a clean session last night.
We’ve also noticed several other users joining this thread with similar symptoms. As we can see from Geoff’s detailed schematic and troubleshooting, “dropouts” are almost always a result of specific local networking configurations rather than a broad Roon Server bug. Because every home network is unique—involving different routers, switches, and ISP configurations—it is impossible to troubleshoot multiple users in a single thread.
For other users experiencing dropouts: Please create a separate support topic. This allows us to track your specific hardware and logs individually so we can provide the same level of focused investigation we are giving Geoff.
For @Geoff_Bishop: Please keep us posted on how the system performs over the next few days. If the dropouts do return, we need to move from general observation to surgical precision. To isolate the exact bottleneck, please provide:
- The exact timestamp (to the minute) when a dropout occurs.
- The name of the track and artist that was playing at that moment.
Without a precise “moment of impact,” it is incredibly difficult to differentiate between a network buffer error, a slow cloud stream from Qobuz/Tidal, or a hardware handshake issue in the logs.
We’ll be standing by for your update!
Well, after initial improvement (I thought/hoped), the dropouts have now returned. This evening I had a major dropout in the Music Room where Roon did not resume/restart the album and I had to restart it manually. Later, the very same thing happened in the Kitchen. (Note: I have never used Apple Airplay or Bluetooth in my system and I have made sure that neither of these are activated in any part of my network just in case there is a chance they could cause interference).
I had a new experience today. I opened a Hi res version of an album from Qobuz but it wouldn’t play; I switched to the ripped CD version of the same album (in my Roon Nucleus SSD) and it played immediately.
Regarding your advice about future events, is “the exact timestamp” simply the time on my watch or is it from event logs? If the latter, I need some guidance on how to access these.
Since I’ve had dropout problems for years during which time all the endpoints, my Roon server/core, router and network have been replaced and the dropouts persist, I find hard to accept that the problem isn’t with Roon itself.
Watch, but ideally down to the minute, and let them know the time zone
Hi @Geoff_Bishop,
Thank you for the report! From a fresh Roon Server diagnostic report, I can confirm you’re unfortunately running into a separate, known issue in relation to Qobuz playback. The good news here is that our team is already working on a fix, but this would explain why you ran into issues playing a Qobuz version of an album and had no issues with the local version.
Here is the tracking thread surrounding this Qobuz issue:
Below is a detailed dropout report over several days. In most cases, short dropouts resumed play after about 1 sec. Longer dropouts (3 seconds) resumed play but often skipped to the next track. Dropouts marked as “Permanent” didn’t restart automatically and I had to manually press the play button. Dropouts occurred both with Qobuz streaming and local ripped CD play. I haven’t included days when there were no dropouts or just one 1 second dropout. Timing is UK.
Sorry formatting lost during copy/paste
`Roon Dropouts
Session 1. 26/3/2026 – all ripped CDs (48kHz/16bit) played from Nucleus One internal SSD; no streaming. Kitchen NAIM Mu-so2
TIME Duration Action Album Track
1856 Permanent Manual restart play Beatles/Sgt Pepper 3
1903 Permanent Manual restart play 4
1909 1 sec 6
1914 1 sec 8
1926 Permanent Manual restart play 12
1936 Permanent Manual restart play Jayhawks/Back Roads and …. 1
1953 1 sec 5
2004 Permanent Manual restart play 8
Session 2. 27/3/2026 –Qobuz streaming. Music Room NAIM Uniti Star
TIME Duration Action Album Track
1700 No dropouts HAIM/I Quit
Session 3. 27/3/2026 –Qobuz streaming. Kitchen NAIM Mu-so2
TIME Duration Action Album Track
1905 1 sec HAIM/I Quit 14
1906 3 sec Auto restarted on next track 15
1955 1 sec
Session 4. 29/3/2026 –Qobuz streaming. Kitchen NAIM Mu-so2
TIME Duration Action Album Track
1830 Play wouldn’t start Switched to ripped CD; played immediately Clapton/Slowhand
reverted to Qobuz streaming for next album
1845 Permanent Manual restart play Clapton/Pilgrim 2
1852 Permanent Manual restart play 3
1900 1 sec 4
1903 1 sec Auto restarted on next track 5
1906 1 sec 7
`
I’m getting really annoyed now. Today I rebooted my whole network. When I’d done that in the past it has improved performance and reduced dropouts. Not this time. Dropouts are worse than ever and there are fewer one second pauses and more prolonged dropouts which don’t remedy themselves and require manual intervention. I see from another thread (referred to above) that dropouts may be caused by Qobuz and that Roon is in discussion with them about a remedy. However. I’m also getting dropouts when playing ripped CDs from my local storage (SSD in Roon Nucleus); how can Qobuz be responsible for that? I agonised for some time about replacing my third party Roon Core with a Roon Nucleus One based on the fear of putting all my eggs in one basket. I’m beginning to think I made the wrong decision.
A miracle! No dropouts today in both the music room and the kitchen while streaming Qobuz.. It really makes you realise how much dropouts impair you listening g experience. Have Roon and Qobuz found a solution?
1 Like
And Qobuz may be making progress on their side, too, according to some reports in the main tracking thread. Though probably not yet fully fixed.
However, if you had dropouts „for years“, the current Qobuz issue and its solution may not be the whole story. Nevertheless, it’s good if this can be gotten out of the way to let you see if any issues remain after this.
Today I played only local music. For the first hour, no dropouts, then there two but only 1 second or less; hiccups rather than dropouts. So I’m still optimistic.
I guess it’s progress, but even this should not happen if everything is really right. I have used Roon for nearly 6 years and didn’t have a dropout ever - just as a baseline for the expectation level.
Early on in this thread I was advised to ungroup my music room and kitchen end points, which I did and left them ungrouped during the subsequent investigation of my dropout problems (above). A few days ago my dropout problem seemed to have disappeared so I decided to re-group the two end points. Wrong decision!. Subsequently I was plagued with frequent dropouts (some lengthy) on both endpoints. So I ungrouped them again and, guess what, not a single dropout on either end point today. Does anyone know what’s going on? Will the upcoming new version of Roon solve my problems?
1 Like
Try turning off all dsp including volume leveling to all.endpoints, and then test the group again with cd 44.1 resolution content only.
Personally I never connect endpoints directly to the router. Suggest connecting the kitchen to one of the other switches or get a switch of its own connected to another switch.
I have switched the connection from the router to network switch 1 but this has made no difference.
Despite making all the changes in the above thread, when I switch on, from day-to-day I never know if I’ll get dropouts or not. It could be zero or one or two or numerous and of varying lengths . Can happen on one or both endpoints and with streamed (Qobuz) and/or local music.
So I’m no further forward. Will the new Version of Roon to be released next week help?
1 Like