I’ve been getting random disconnects from Qobuz lately. (“Artist not available” when I search.)
My latest one is using Arc and songs are listed as “unavailable” as I play them. 
Hi! What’s not quite right with Roon?
· Music won’t play or issues with my library
Music won’t play or issues with my library
· Streaming tracks greyed out or unavailable
Tell us what's going on
· Qobuz albums/tracks show as unavailable in Arc but they do play
Tell us about your home network
· Ubiquiti UniFi - not related here
As mentioned here
https://community.roonlabs.com/t/playing-unavailable-songs/323836
Hi @MusicD,
Thank you for your post. That’s not normal and it seems like the Qobuz API is delivering some incomplete data without triggering a disconnection error.
Just to clarify, do the same tracks (like this Genesis live album) appear as “unavailable” when you search for them in Roon, as well?
Or does this condition only affect ARC?
Does this reproduce if you’re using WiFi on the phone instead of cellular data? Qobuz authorizations always pass through Roon Server, but the audio stream is delivered directly to the phone via the Qobuz API. We’d be testing a separate network pathway by playing the track on WiFi at home in ARC.
We’ll watch for your response and escalate from there. Thank you!
Hi @Peter_Ryan3,
@MusicD has opened a case in the Support category here: Qobuz tracks show unavailable but play in ARC (ref#O43XQM)
We’re going to merge this topic thread into that one so that your post is also recorded alongside this investigation. Please stand by.
Thanks for the report.
When I searched for group Genesis in ARC only it returned “not available”.
I opened ROON and my screen had red Qobuz Login failure message (again) - before I could respond it disappeared.
I opened ARC - searched for and got Genesis - started album - a few songs in current song and subsequent songs were “unavailable” yet played fine.
Hi @connor
No. They show available as normal and play.
The album screenshot I posted now also shows as normal. At the time of posting it showed as normal in Roon.
Just appears to affect Arc.
An observation between my screenshot and @Peter_Ryan3 is that my tracks show as white text and not greyed out.
I’m yet to reproduce it again and based on Qobuz APi this year being a bit wonky, it might have been a blip affecting some users and some may not have noticed.
I’ll test/use Arc tomorrow at work where I’ll have plenty of time to observe this more.
I’ll update as and when I see something odd again.
Hello @Peter_Ryan3
Your server lost network access 89 times in the last 13 days. Not to Qobuz specifically: the failed connections were to five different providers, so this is your server’s connectivity dropping rather than anything at Qobuz’s end.
1163 Cloudflare
849 Google Cloud
252 Azure
300 Akamai
42 Cloudflare
Here is why that hits Qobuz so hard. When Roon cannot reach Qobuz to verify your login, it currently treats the service as gone and drops your entire Qobuz library, then rebuilds it once the connection returns. Your library is 3,783 tracks, and each rebuild took up to fifteen minutes. That is the red Qobuz login message you saw, and it is why tracks were labelled unavailable in ARC while still playing: the audio comes straight from Qobuz to your phone, so it plays, while the availability label depends on a library that is mid-rebuild.
Across those 13 days it added up to just under twelve hours with no Qobuz.
Rebuilding the whole library after a single failed check is wrong, and that is a defect on our side. It is logged with our development team and being worked on.
But we do not want to leave you waiting on it, because that would not fix your situation. The rebuild is the consequence. The cause is that your server keeps losing network access, and that is where this actually needs to be solved. Even with our fix in place, those 89 dropouts would still be happening.
So that is where we would like to look next:
- What is between your server and the router, please? Direct cable, a switch, a powerline adapter, anything in the path.
- When this happens, does anything else on your network lose internet at the same time, or is it only Roon?
- Does your server have a reserved or static address on the router, or is it on a normal DHCP lease?
If you can, please also try a different Ethernet cable and a different port on the router. With 89 events in 13 days you will not have to wait long to see whether it makes a difference.
@MusicD
Thanks for checking that, and your answer changes where your case goes.
You told us the same tracks looked normal in Roon at the moment ARC called them unavailable. Peter’s logs show something different: his server was repeatedly losing its connection and rebuilding his Qobuz library, which affects Roon and ARC together. Yours is not that, so it is a separate matter and it will get lost if we keep both here.
Please open a new thread for yours and link back to this one.
Thanks @vadim
It hasn’t happened since that I know of. If it happens again I will open a separate support thread.
1- Direct cable
2- Just ROON
3- reserved IP
I changed the network cable just now. So much for the golden network rule of “first check the cable” 
thanks mate
Hello @Peter_Ryan3
Ha, well, the golden rule earned its place for a reason.
Your three answers actually make the cable the right suspect. Direct cable, nothing else on the network affected, and a reserved address means the fault sits in that one link between the server and the router rather than anywhere shared. So that was the correct first move.
Now we need a couple of days. You were averaging about seven dropouts a day, so if you get through 48 hours without the red Qobuz message, that is a real result rather than luck.
You do not have to watch for it. We can see these in your logs from here. So please just tell us when it has been running for a couple of days on the new cable and we will check the count and let you know.
If it is still dropping, the next thing to try is a different port on the router, since a bad port looks identical to a bad cable from where we are sitting.
As the disconnects continue - at a lower frequency - I have also changed the router port.
(1:50PM PST August 20)
Drops seem to have stopped with new cable and new port. Device placed on old port is working fine but probably does not need the always on consistency that my Nucleus needs. Fingers crossed.
