Help Wizard

Step 1



Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...


Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...


[Desktop] IPv6 support for the desktop client

Resubmitting  the same idea as:

submitted previously by @sdstrowes


It would be highly desirable to make sure that the desktop client can work on Ipv6-only networks as they are becoming operation reality (a number of large entrerprise networks like Cisco and Microsoft have piloted IPv6-only corporate networks).


As it's been mentioned in the previosuly posted incarnations of this idea, the mobile client works just fine and Fastly supports IPv6.



Updated on 2021-06-13

Hey everyone,


Thanks for bringing us your feedback in the Spotify Idea Exchange.


Your suggestion has gathered the votes necessary and your feedback is now reaching the internal teams at Spotify. They're aware of the vote count and popularity of this idea. We'll continue to monitor and check out the comments here, too.


As soon as we have any updates on its status, we'll let you know.


More info on how your feedback reaches Spotify via the Idea Exchange can be found here.

Status changed to: Up for Votes

Updated on 2019-06-18

Marked as new idea, which is a repost of this inactive idea.


My colleague cancelled his subscription because of the lack of ipv6 support of the (linux) desktop client. I'm thinking about it. IPv6 is here and very relevant. 


I voted for this and as an IT professional I'd like to fully support this. But I'm wondering what kind of insanity major plumbing work like this will cause, in terms of removal of my favorite random features. Because not all Spotify APIs or microservices can support v6 clients or for whatever reason.


What's next to go? support? Searching for Facebook friends to follow? Collaborative playlists? Showing unavailable tracks in playlists?


"Fun and exciting", like how the miserable 2015 revamp of the desktop client to Chromium wrapped garbage removed the audio volume normalization toggle for a while, caused truncation of play history for JS performance reasons, or how you no longer could change active playlists by right clicking on one in the list.


At least add IPv6 support in the CDNs you use (Akamai & Fastly) . They already support IPv6.



Facebook fully supports IPv6 (they're running IPv6-only internally, they say). can actually be used over IPv6-only, if you make your DNS to deliver the AAAA record of the CDNs that uses. There's no excuse.


This really needs to move forward!


I think the ask here is to ensure the Desktop client works in a NAT64/DNS64 environment. It does not mean Spotify service should be on IPv6, but that the desktop client can work on an IPv6 only network which has gateways to the IPv4 Internet. As someone pointed, the mobile client already works in this environment, so it is to ensure the desktop code is IP address familly agnostic.



No, the ask is to actually make Spotify service full DualStack with native IPv6. The request implies this by mentioning fastly's IPv6 capabilities.

But making the desktop client work in a IPv6-only NAT64 environment would be a first step.


@tiljes spotify has enabled IPv6 on the CDN 😁. Now the main app remains 


Can we have Spotify on Comcast Xfinity appliance?

note: Xfinity TV is an IPv6 only service.


Google is also moving to ipv6 only.