Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Plan
Premium
Country
US
Device
Windows App or through Edge browser
Operating System
Windows 10
My Question or Issue
Connecting to Spotify,
We connect (info gained from Chrome Dev Tools) to open.spotify.com, which refers to open.spotifycdn.com, which we can't connect to.
open.spotifycdn.com points to (currently) tls130rtt.spotifycdn.map.fastly.net
From other places on the internet, this name resolves to viable content servers for Spotify, such as 199.232.214.251 or 146.75.74.251.
From our company's internet address space, it resolves to the nonworking IP 151.101.114.251. Attempting to connect to 151.101.114.251 over port 443 (from anywhere I can probe from on the internet) times out, and it seems like this is a defunct part of Spotify's Fastly CDN service.
Fastly CDN is returning non-working IPs, causing timeouts, but just for our Company
What I'm really wondering is if Spotify engineering can check their Fastly console/GUI, look for 151.101.114.251, and see if it should still exist, if its down, why we are pointed to it.