- Joined
- Jan 11, 2016
- Messages
- 16,273
- Reaction score
- 5,605
Indeed.Edge connect.
That is interesting.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Indeed.Edge connect.
That is interesting.
Non-authoritative answer:
r-live-cache.akamaized.net canonical name = a1075.dscw16.akamai.net.
Name: a1075.dscw16.akamai.net
Address: 2.16.244.16
Name: a1075.dscw16.akamai.net
Address: 2.16.244.11
Name: a1075.dscw16.akamai.net
Address: 2.16.244.17
Name: a1075.dscw16.akamai.net
Address: 2.16.244.10
Name: a1075.dscw16.akamai.net
Address: 2.16.244.42
Name: a1075.dscw16.akamai.net
Address: 2.16.244.41
Name: a1075.dscw16.akamai.net
Address: 2.16.244.35
Name: a1075.dscw16.akamai.net
Address: 2.16.244.33
Name: a1075.dscw16.akamai.net
Address: 2.16.244.18
*************** % nslookup r-live-cache.akamaized.net
Server: 1.1.1.1
Address: 1.1.1.1#53
Non-authoritative answer:
r-live-cache.akamaized.net canonical name = a1075.dscw16.akamai.net.
Name: a1075.dscw16.akamai.net
Address: 197.80.130.136
Name: a1075.dscw16.akamai.net
Address: 197.80.130.129
Name: a1075.dscw16.akamai.net
Address: 197.80.130.121
Name: a1075.dscw16.akamai.net
Address: 197.80.130.82
Name: a1075.dscw16.akamai.net
Address: 197.80.130.97
Name: a1075.dscw16.akamai.net
Address: 197.80.130.131
Name: a1075.dscw16.akamai.net
Address: 197.80.130.73
Name: a1075.dscw16.akamai.net
Address: 197.80.130.72
Name: a1075.dscw16.akamai.net
Address: 197.80.130.75
*********** nslookup r-live-cache.akamaized.net
Server: 1.1.1.1
Address: 1.1.1.1#53
Non-authoritative answer:
r-live-cache.akamaized.net canonical name = a1075.dscw16.akamai.net.
Name: a1075.dscw16.akamai.net
Address: 2.16.244.10
Name: a1075.dscw16.akamai.net
Address: 2.16.244.27
Name: a1075.dscw16.akamai.net
Address: 2.16.244.24
Name: a1075.dscw16.akamai.net
Address: 2.16.244.18
Name: a1075.dscw16.akamai.net
Address: 2.16.244.49
Name: a1075.dscw16.akamai.net
Address: 2.16.244.41
Name: a1075.dscw16.akamai.net
Address: 2.16.244.33
Name: a1075.dscw16.akamai.net
Address: 2.16.244.48
Name: a1075.dscw16.akamai.net
Address: 2.16.244.26
Your ISP probably doesn't have any on net clusters, I could be wrong. So it's a different situation.Im Not with Cool Ideas or AH, but what I found interesting is that its been switching between the two a few times and hour.
The below 15 minutes apart each. Note my ISP uses 1.1.1.1 as default DNS.
Code:Non-authoritative answer: r-live-cache.akamaized.net canonical name = a1075.dscw16.akamai.net. Name: a1075.dscw16.akamai.net Address: 2.16.244.16 Name: a1075.dscw16.akamai.net Address: 2.16.244.11 Name: a1075.dscw16.akamai.net Address: 2.16.244.17 Name: a1075.dscw16.akamai.net Address: 2.16.244.10 Name: a1075.dscw16.akamai.net Address: 2.16.244.42 Name: a1075.dscw16.akamai.net Address: 2.16.244.41 Name: a1075.dscw16.akamai.net Address: 2.16.244.35 Name: a1075.dscw16.akamai.net Address: 2.16.244.33 Name: a1075.dscw16.akamai.net Address: 2.16.244.18 *************** % nslookup r-live-cache.akamaized.net Server: 1.1.1.1 Address: 1.1.1.1#53 Non-authoritative answer: r-live-cache.akamaized.net canonical name = a1075.dscw16.akamai.net. Name: a1075.dscw16.akamai.net Address: 197.80.130.136 Name: a1075.dscw16.akamai.net Address: 197.80.130.129 Name: a1075.dscw16.akamai.net Address: 197.80.130.121 Name: a1075.dscw16.akamai.net Address: 197.80.130.82 Name: a1075.dscw16.akamai.net Address: 197.80.130.97 Name: a1075.dscw16.akamai.net Address: 197.80.130.131 Name: a1075.dscw16.akamai.net Address: 197.80.130.73 Name: a1075.dscw16.akamai.net Address: 197.80.130.72 Name: a1075.dscw16.akamai.net Address: 197.80.130.75 *********** nslookup r-live-cache.akamaized.net Server: 1.1.1.1 Address: 1.1.1.1#53 Non-authoritative answer: r-live-cache.akamaized.net canonical name = a1075.dscw16.akamai.net. Name: a1075.dscw16.akamai.net Address: 2.16.244.10 Name: a1075.dscw16.akamai.net Address: 2.16.244.27 Name: a1075.dscw16.akamai.net Address: 2.16.244.24 Name: a1075.dscw16.akamai.net Address: 2.16.244.18 Name: a1075.dscw16.akamai.net Address: 2.16.244.49 Name: a1075.dscw16.akamai.net Address: 2.16.244.41 Name: a1075.dscw16.akamai.net Address: 2.16.244.33 Name: a1075.dscw16.akamai.net Address: 2.16.244.48 Name: a1075.dscw16.akamai.net Address: 2.16.244.26
Funny thing is i HEARD never checked myself that Tiktok also uses Akamai and i use to often get "your network is unstable" in the app meanwhile my wifi speed tests on 5GHZ are 100/100... Last few days i have not gotten any alertsSpotify has been working like magic the last few days![]()


Just use CISP DNS it resolves to their caches and avoids Optinet and their kak cachesI've had terrible Akamai speeds since the dual cable break a few weeks back.
I've tried multiple DNS, and each seems to have its own issues.
Using either Cloudflare 1.1.1.1 or Google 8.8.8.8, from my experience, has been dreadful for services that utilize Akamai content.
There must be some super screwed Akamai servers that have not re-enabled the upstream syncing or something because the experience of late has been nothing short of infuriating.
It's honestly nothing short of completely broken.
How can one expect this performance on two of the most popular DNS providers?
View attachment 1604060
Just use CISP DNS it resolves to their caches and avoids Optinet and their kak caches
A lot of people don't realise ISP's have a DNS so they can actually help steer your traffic to cache's etc where the big guys like Google/Cloudflare don't actually utilize it, its just there whether it runs well or not...Yeah. Cloudflare doesn't actually make the internet "faster" as they claim...
172.66.1.120, tracert is as follows:Tracing route to 172.66.1.120 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms terran.mordritch.com [192.168.1.1]
2 2 ms 2 ms 2 ms 100-100-101-60.loopback [100.100.101.60]
3 2 ms 2 ms 2 ms loopback0.tri-jb3-dc21-a21-cr.cisp.co.za [154.0.0.75]
4 2 ms 2 ms 2 ms lo0.terjhb1br1.cisp.co.za [154.0.0.82]
5 3 ms 3 ms 3 ms 196-60-9-75.ixp.joburg [196.60.9.75]
6 2 ms 2 ms 3 ms 197.234.240.5
7 2 ms 2 ms 2 ms 172.66.1.120
HI there, apologies for the delay.This is happening again as of a week or so ago.
When watching Windows' Resource Monitor, it seems to be slow when downloading from172.66.1.120, tracert is as follows:
Code:Tracing route to 172.66.1.120 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms terran.mordritch.com [192.168.1.1] 2 2 ms 2 ms 2 ms 100-100-101-60.loopback [100.100.101.60] 3 2 ms 2 ms 2 ms loopback0.tri-jb3-dc21-a21-cr.cisp.co.za [154.0.0.75] 4 2 ms 2 ms 2 ms lo0.terjhb1br1.cisp.co.za [154.0.0.82] 5 3 ms 3 ms 3 ms 196-60-9-75.ixp.joburg [196.60.9.75] 6 2 ms 2 ms 3 ms 197.234.240.5 7 2 ms 2 ms 2 ms 172.66.1.120
Thank you for confirming, are you able to share a NSlookup to Spotify? As I believe it should pull from our Akamai cache,Yes, my computer's DNS is set to my pfSense firewall which is set to do DNS forwarding and it's DNS servers are:
154.0.1.1
154.0.1.10
Unfortunately not, but what you could do is add IPVFOO to your browser, and listen/download songs via the web browser and it should show you, in real time, the CDN's in use.I could do a nslookup to spotify.com, but I don't think that necessarily correlates with the hostnames they are using for the song downloads. I don't know offhand how I might work out what hostname they use for that, do you by any chance?

Tracing route to a2-21-98-11.deploy.static.akamaitechnologies.com [2.21.98.11]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 2 ms 2 ms 100-100-101-60.loopback [100.100.101.60]
3 2 ms 2 ms 2 ms loopback0.tri-jb3-dc21-a21-cr.cisp.co.za [154.0.0.75]
4 2 ms 2 ms 2 ms lo0.terjhb1br1.cisp.co.za [154.0.0.82]
5 11 ms 11 ms 6 ms 196-60-11-85.ixp.joburg [196.60.11.85]
6 2 ms 2 ms 2 ms a2-21-98-11.deploy.static.akamaitechnologies.com [2.21.98.11]
I'd be interested in a tracert from you to the IPs it's hitting.To chip in here on CISP CT and my Spotify is working perfect
Strange, I see that's to Akamai as opposed to our ON-Net Cache directly.It seems it is actually using Akamai (maybe it varies), speeds don't seem great, but maybe they're normal.
View attachment 1830073
Here is an nslookup:
Code:Tracing route to a2-21-98-11.deploy.static.akamaitechnologies.com [2.21.98.11] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 2 ms 2 ms 2 ms 100-100-101-60.loopback [100.100.101.60] 3 2 ms 2 ms 2 ms loopback0.tri-jb3-dc21-a21-cr.cisp.co.za [154.0.0.75] 4 2 ms 2 ms 2 ms lo0.terjhb1br1.cisp.co.za [154.0.0.82] 5 11 ms 11 ms 6 ms 196-60-11-85.ixp.joburg [196.60.11.85] 6 2 ms 2 ms 2 ms a2-21-98-11.deploy.static.akamaitechnologies.com [2.21.98.11]