Skip to main content

I have quite a few playlists saved in the Sonos app. Most include tracks I searched and saved from Napster to my Sonos playlist. A few days ago, none of those tracks would play. An error message ‘lost connection to Napster’ would pop up and every Napster-derived track would be skipped over until the Sonos app reached a track sourced from a different streaming service. 

I did the usual stuff — cut the Napster connection, rebooted everything, reauthorized Napster, yadda yadda.

Nothing worked. I reached out to Napster. Here’s what I got back:

Hello, 
 
We understand how frustrating it must be to discover that playlists you’ve carefully built over time are no longer accessible. Those collections matter, and we sincerely apologize for the disruption this has caused.

Napster is currently undergoing a significant transition. As part of this change, our traditional music catalog is no longer available. Unfortunately, this means that the saved artists, albums, and songs in your playlists have been removed from our platform.”

I’m not entirely sure what this means, but it may be that Napster-derived content saved in Sonos playlists will no longer be available. Can a Sonos moderator or other knowledgable source advise what’s going on?

Hey ​@chambolle, welcome back!

I am sorry to hear about the issue you are experiencing while trying to listen to your Sonos Playlists that include Napster tracks.

There is an ongoing playback issue in regard to the Napster music service within Sonos, which you can keep track of from our Sonos Status page.

I’m not entirely sure what this means, but it may be that Napster-derived content saved in Sonos playlists will no longer be available. Can a Sonos moderator or other knowledgable source advise what’s going on?

We are working with Napster in order to resolve this issue as soon as possible and I’ll reply on this thread as soon as I have an update.

Thank you for your patience.


Hello ​@chambolle,

I’ve got notified that the Napster outage within the Sonos App has been resolved. Can you confirm that you no longer have this issue?