Qobuz still messed up

@erik_squires 

Thanks for the DNS tip. I cannot change my Xfinity router. I can on my various control devices (iPhone, iPad, etc). 

@macg19 

Thank you for the update from Qobuz. Wait and see I guess.

@gkelly On jplay it fails. On roon it skips to next track. 
however, it plays directly from qobuz app on my phone and to my DAC. this points to API issues with renderers. 
jplay tells the renderer to go get this file from qobuz which triggers the api call. Roon will be performing the api call as well. 
 

when streaming using qobuz connect the renderer just becomes an end point to which the qobuz sends the data. 
another possibility why the file would play is if was cached. In example, it’s part of the Aurender conductor queue and was previously loaded into the cache. Pretty sure if the cache is cleared it won’t play anymore. 
Another possibility why it would work for some and not work for others is qobuz is steering requests to different cloud regions based on customer geographical location or other criteria. And there happens to be no issues with api calls in that region. 
 

It’s a qobuz issue and it is a repeat of the problem from 2 months ago. 

Sorry to hear.  No issues here playing Qobuz at home, in the car and on the boat.  

@bassbuyer it’s not that Qobuz doesn’t work at all. It’s only certain tracks that won’t play  and there are no issues playing from qobuz app.

for more details, from the Jplay thread April 9 2026:

Hi everyone,

I wanted to share an update on the Qobuz playback issues that many of you have been experiencing over the past two weeks or so. To be clear upfront: this is a Qobuz-side issue, not a JPLAY bug. I’ve been receiving a lot of support requests about tracks that won’t play, playback stopping mid-album, "error sending action to renderer" messages, and similar symptoms — and they all trace back to the same root cause.

Qobuz has officially confirmed the incident to their partners. Here’s what they shared initially:

"We have identified a technical issue affecting the availability of certain audio files on our API. The problem specifically concerns files larger than 50MB. It results in a size mismatch error between the requested and received data, linked to a partial object caching issue. Our technical team is currently investigating to identify the root cause and the scope of impacted files."

And an update from yesterday:

"We have identified the source of the playback errors: it is a caching anomaly with our CDN provider. In practice, some distribution servers are hosting a corrupted or incomplete file. Since each audio quality corresponds to a separate recording, switching quality often allows you to fall back on a healthy file and work around the issue. Our teams are currently listing the affected tracks and carrying out a gradual cache purge. The situation should be resolved very shortly."

A few practical takeaways:

- The issue mainly affects files larger than 50MB, which is why hi-res tracks (24/96 and above) are hit the hardest while CD-quality content is mostly unaffected.

- As a workaround, switching the streaming quality from 24/192 to 24/96 or even 16/44 (CD) can often help — each quality level is a separate file on Qobuz’s CDN, so a different quality may give you a healthy copy.

- Qobuz is performing a gradual cache purge, so affected tracks should start working again progressively over the coming days. (fingers crossed)

- There’s nothing we can fix on the JPLAY side — this needs to be resolved by Qobuz at the CDN level.

Thanks everyone for your patience. I’ll post another update once Qobuz confirms everything is back to normal.

Marcin