Fastly CDN is returning non-working IPs, causing timeouts, but just for our Company
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Labels:
-
Dead CDN nodes
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page