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

[1223386036]

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.

[dbdq]

Same with us (in Texas)

> nslookup open.spotifycdn.com

Name: tls130rtt.spotifycdn.map.fastly.net
Addresses: 2a04:4e42:1b::763
151.101.114.251
Aliases: open.spotifycdn.com

[1223386036]

oh weird, does it ping for you?

other spotify fastly nodes ping/accept connections on port 443, this one doesn't for us

[dbdq]

It did respond to ping but is not responding on 443

[dbdq]

It doesn't respond on port 80 either for what it's worth

[1223386036]

so, from my home computer (nothing to do w my company), on NordVPN, it allows connections on 443 now?

telnet 151.101.114.251 443

Trying 151.101.114.251...

Connected to 151.101.114.251.

Escape character is '^]'.

^]

telnet> q

Connection closed.

[1223386036]

in case anyone's wondering, the spotifycdn we were getting changed to a working node

no idea why, but i'm at least happy for this