-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Will you be subscribing to the new Disney+ R49 streaming package?
Cool Ideas Fibre ISP - Feedback
- Thread starter paulosouthafrica
- Start date
- Status
Just an update from my side, things are starting to work after waiting overnight. I did some more digging and it seems it might be the change of routes with hitting Akamai CDN which has previous issues with SSL. I'm guessing I might be hitting a different one of their edge servers compared to being on Google DNS / previous provider.
Honestly I'm not sure, I haven't changed any configurations and after constant refreshes on my devices through the course of the night, they just started resolving. I noticed on my desktop that this affected Adobe CC, Steam and Apple.com, all 3 systems which use strong SSL and break otherwise.
Also did a benchmark overnight for DNS and Google DNS is showing up as being much faster on average. Not surprising considering their size but curious to know if there's any reason for using the CISP DNS server over Google DNS? Guessing maybe better local lookups/routing?
I'll give it a few days and then see again since it's still a bit up and down. Just posting here in case anyone else ever experiences issues.
On the positive, after moving to CISP web calls and general browsing has felt snappier, so I'm excited to be on the network.
Honestly I'm not sure, I haven't changed any configurations and after constant refreshes on my devices through the course of the night, they just started resolving. I noticed on my desktop that this affected Adobe CC, Steam and Apple.com, all 3 systems which use strong SSL and break otherwise.
Also did a benchmark overnight for DNS and Google DNS is showing up as being much faster on average. Not surprising considering their size but curious to know if there's any reason for using the CISP DNS server over Google DNS? Guessing maybe better local lookups/routing?
I'll give it a few days and then see again since it's still a bit up and down. Just posting here in case anyone else ever experiences issues.
On the positive, after moving to CISP web calls and general browsing has felt snappier, so I'm excited to be on the network.
- Joined
- Jan 11, 2016
- Messages
- 16,423
- Reaction score
- 5,715
Basically using an Open DNS like Googles in the past would bypass any on-net caching, it's always recommended to use your providers DNS resolver.
We have an akamai cluster on net, that being said all of your traces either route to a cluster overseas or directly to Apples network. The CDN providers manage this kind of thing, so might have just been a temporary issue.
Cheers for that! I see you mentioned 'in the past', wonder if it's still as applicable now.
Anyways, thanks for the troubleshooting, have a good Friday. Appreciate all the help as always!
- Joined
- Jan 11, 2016
- Messages
- 16,423
- Reaction score
- 5,715
Yes so many of them now have the "CDN related" entries which should help with connecting you to the correct source, but it is still always better to use your providers DNS.
Have you guys run tests using 1.1.1.1 as your DNS? I could swear browsing is snappier since I switched.
Tinuva
The Magician
In Cape Town 1.1.1.1 easily outperform 8.8.8.8 both in dns response times and directing us to an akamai cluster in Cape Town instead of JHB.
- Joined
- Jan 11, 2016
- Messages
- 16,423
- Reaction score
- 5,715
Well 8.8.8.8 is only hosted in JHB, which is why you would have a ~20ms overhead obviously
. Whereas Cloudflare is national now with their caches.
Tinuva
The Magician
True that. But also look at 9.9.9.9 which is in CPT too.Well 8.8.8.8 is only hosted in JHB, which is why you would have a ~20ms overhead obviously
Lets look at the CDN from these:
CISP 155.93.255.1 (fastest from dnsbench)
Code:
root@monitor ~ # dig cdn.steampowered.com @155.93.255.1 +short
storefront.akamai.steamstatic.com.edgesuite.net.
a1189.g1.akamai.net.
154.0.14.7
154.0.14.9
root@monitor ~ # ping -c4 154.0.14.7
PING 154.0.14.7 (154.0.14.7) 56(84) bytes of data.
64 bytes from 154.0.14.7: icmp_seq=2 ttl=58 time=31.9 ms
64 bytes from 154.0.14.7: icmp_seq=3 ttl=58 time=30.3 ms
64 bytes from 154.0.14.7: icmp_seq=4 ttl=58 time=40.0 ms
--- 154.0.14.7 ping statistics ---
4 packets transmitted, 3 received, 25% packet loss, time 3002ms
rtt min/avg/max/mdev = 30.367/34.104/40.009/4.226 msCloudFlare 1.0.0.1
Code:
root@monitor ~ # dig cdn.steampowered.com @1.0.0.1 +short
storefront.akamai.steamstatic.com.edgesuite.net.
a1189.g1.akamai.net.
197.84.130.19
197.84.130.25
root@monitor ~ # ping -c4 197.84.130.19
PING 197.84.130.19 (197.84.130.19) 56(84) bytes of data.
64 bytes from 197.84.130.19: icmp_seq=1 ttl=58 time=2.32 ms
64 bytes from 197.84.130.19: icmp_seq=2 ttl=58 time=2.15 ms
64 bytes from 197.84.130.19: icmp_seq=3 ttl=58 time=2.10 ms
64 bytes from 197.84.130.19: icmp_seq=4 ttl=58 time=2.02 ms
--- 197.84.130.19 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 2.028/2.155/2.328/0.119 ms9.9.9.9
Code:
root@monitor ~ # ping -c4 9.9.9.9
PING 9.9.9.9 (9.9.9.9) 56(84) bytes of data.
64 bytes from 9.9.9.9: icmp_seq=1 ttl=59 time=4.17 ms
64 bytes from 9.9.9.9: icmp_seq=2 ttl=59 time=2.18 ms
64 bytes from 9.9.9.9: icmp_seq=3 ttl=59 time=2.10 ms
64 bytes from 9.9.9.9: icmp_seq=4 ttl=59 time=2.80 ms
--- 9.9.9.9 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 2.103/2.815/4.175/0.832 ms
root@monitor ~ # dig cdn.steampowered.com @9.9.9.9 +short
storefront.akamai.steamstatic.com.edgesuite.net.
a1189.g1.akamai.net.
23.215.102.48
23.215.102.10
root@monitor ~ # ping -c4 23.215.102.48
PING 23.215.102.48 (23.215.102.48) 56(84) bytes of data.
64 bytes from 23.215.102.48: icmp_seq=1 ttl=51 time=272 ms
64 bytes from 23.215.102.48: icmp_seq=2 ttl=51 time=272 ms
64 bytes from 23.215.102.48: icmp_seq=3 ttl=51 time=272 ms
64 bytes from 23.215.102.48: icmp_seq=4 ttl=51 time=273 ms
--- 23.215.102.48 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 272.534/272.828/273.564/0.564 msAnd so, CloudFlare wins not only in benchmark, but also at good CDN results for Akamai.
- Joined
- Jan 11, 2016
- Messages
- 16,423
- Reaction score
- 5,715
Yeah so resolution speed looks to almost be identical, and our DNS will point to our on-net cluster in JHB as preference. Akamai used to offer a distributed model of clusters but now have moved to a more "Google model" where they will rather just upgrade a single cluster and expect you to carry the traffic via longhaul. It's actually strange it's pointing you to use an Mweb cluster.
Hi Paul,
Did Netflix not route to Local on net server/cdn "akamai" at CISP?
Seems to be routing international now!
netflix.co.za
Tracing route to netflix.co.za [52.210.7.69]
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 10 | 10 | 0 | 0 | 1 | 0 |
| 155.93.246.1 - 0 | 10 | 10 | 1 | 1 | 4 | 1 |
| 154.0.1.125 - 0 | 10 | 10 | 1 | 1 | 4 | 1 |
| 154.0.1.13 - 0 | 10 | 10 | 1 | 1 | 4 | 1 |
| 154.0.3.106 - 0 | 10 | 10 | 142 | 142 | 143 | 142 |
| 195.66.225.175 - 0 | 10 | 10 | 142 | 154 | 249 | 143 |
| 54.239.100.216 - 0 | 10 | 10 | 142 | 152 | 164 | 147 |
| 54.239.101.99 - 0 | 10 | 10 | 142 | 142 | 145 | 143 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| 54.239.41.212 - 0 | 10 | 10 | 151 | 152 | 154 | 152 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| 52.93.7.168 - 0 | 10 | 10 | 153 | 169 | 181 | 153 |
| 52.93.101.103 - 0 | 10 | 10 | 151 | 152 | 155 | 151 |
| 52.93.101.126 - 0 | 10 | 10 | 154 | 168 | 183 | 154 |
| 52.93.36.175 - 0 | 10 | 10 | 151 | 152 | 155 | 152 |
| 176.32.106.133 - 0 | 10 | 10 | 152 | 152 | 155 | 152 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Using CISP DNS here in Cape Town.
DNS Servers . . . . . . . . . . . : 155.93.255.1
154.0.1.1
Did Netflix not route to Local on net server/cdn "akamai" at CISP?
Seems to be routing international now!
netflix.co.za
Tracing route to netflix.co.za [52.210.7.69]
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 10 | 10 | 0 | 0 | 1 | 0 |
| 155.93.246.1 - 0 | 10 | 10 | 1 | 1 | 4 | 1 |
| 154.0.1.125 - 0 | 10 | 10 | 1 | 1 | 4 | 1 |
| 154.0.1.13 - 0 | 10 | 10 | 1 | 1 | 4 | 1 |
| 154.0.3.106 - 0 | 10 | 10 | 142 | 142 | 143 | 142 |
| 195.66.225.175 - 0 | 10 | 10 | 142 | 154 | 249 | 143 |
| 54.239.100.216 - 0 | 10 | 10 | 142 | 152 | 164 | 147 |
| 54.239.101.99 - 0 | 10 | 10 | 142 | 142 | 145 | 143 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| 54.239.41.212 - 0 | 10 | 10 | 151 | 152 | 154 | 152 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| 52.93.7.168 - 0 | 10 | 10 | 153 | 169 | 181 | 153 |
| 52.93.101.103 - 0 | 10 | 10 | 151 | 152 | 155 | 151 |
| 52.93.101.126 - 0 | 10 | 10 | 154 | 168 | 183 | 154 |
| 52.93.36.175 - 0 | 10 | 10 | 151 | 152 | 155 | 152 |
| 176.32.106.133 - 0 | 10 | 10 | 152 | 152 | 155 | 152 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Using CISP DNS here in Cape Town.
DNS Servers . . . . . . . . . . . : 155.93.255.1
154.0.1.1
- Joined
- Jan 11, 2016
- Messages
- 16,423
- Reaction score
- 5,715
It depends on the content, it doesn't mean "all" Akamai traffic would come from the on-net cluster.
- Joined
- Jan 11, 2016
- Messages
- 16,423
- Reaction score
- 5,715
Correct we only have edge clusters, although they peer at NAP.
This what you refering too?
https://companies.mybroadband.co.za/blog/2013/10/04/content-giant-akamai-sets-up-in-south-africa/
- Joined
- Jan 11, 2016
- Messages
- 16,423
- Reaction score
- 5,715
Yerp.
Tinuva
The Magician
Thats probably to be expected. Netflix's servers in JHB is for streams, not per say their website.
- Status