Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

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

Loading issue...

Loading ongoing issues...

VIEW ALL

Fastly CDN is returning non-working IPs, causing timeouts, but just for our Company

Fastly CDN is returning non-working IPs, causing timeouts, but just for our Company

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.

 

 

 

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.

 

 

Reply

 

 

Similar post made for same issue in other community forum

 

 

 

Plan

 

Free/Premium

 

Country

 

US (Texas)

 

 

 

Device

 

Any browser

 

 

 

Operating System

 

Windows 10

 

 

 

My Question or Issue

Reply
5 Replies

What service provider are you on?  I'm experiencing the same on Xfinity.  Seems others are as well: https://forums.xfinity.com/conversations/your-home-network/xfinity-internet-blocking-spotify/676529b...

Connections are normal from Verizon.  However, VPN connections also experience the throttling.

Oh wait duh this is a DNS propagation issue.  XFinity has a long TTL.  DNS set to 1.1.1.1 or 8.8.8.8 works, looks like XFinity (75.75.75.75) evicts in a few days.

It's the place I work for, don't nec want to give the company name but our ISPs aren't XFinity, Verizon and ATT I think.

 

I don't think it's TTL, as when I query Spotify/Fastly's own authoritative DNS servers, they give me the dead IPs.

 

 

Same issue in Utah. DNS gives me 199.232.66.251 but that server is completely dead.
Changing hosts file to force resolve to 199.232.214.251 fixes the issue.

thanks, unfortunately, I run the proxy servers at the company, plus I don't want to take that on, lol

 

Suggested posts