Cool Ideas Fibre ISP - Feedback

Status
Not open for further replies.
blunt said:
I found another post saying 155.93.255.1 is CPT, @PBCool which one is best to use for CT?
Click to expand...

Who knows? :D

Code: 
D:\>nslookup 155.93.255.1 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Name:    cdns1.cpt.cisp.co.za
Address:  155.93.255.1


D:\>nslookup 154.0.1.1 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Name:    cdns1.cisp.co.za
Address:  154.0.1.1
 
PBCool said:
We have turned up a new AWS direct connect in Cape Town so please let me know if there are any issues accessing AWS services.
Click to expand...

Definately less packetloss now :D (those green-brown marks are packetloss)

1555592726997.png
 
leppie said:
Who knows? :D

Code: 
D:\>nslookup 155.93.255.1 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Name:    cdns1.cpt.cisp.co.za
Address:  155.93.255.1


D:\>nslookup 154.0.1.1 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Name:    cdns1.cisp.co.za
Address:  154.0.1.1
Click to expand...
PBCool said:
154.0.1.1 and 154.0.1.10 same across the network.
Click to expand...

thanks, I'm using 154.0.1.1, I see the pings are the same anyway. I use smartdns for certain media sites so I'm just setting up certain devices on my home network to use the smart dns and everything else CI/1.1.1.1/9.9.9.9/8.8.8.8 (via my router of course).

as I understand it, it's best I stick to using CI's DNS to get the best out of my connection, correct @PBCool ?
 
blunt said:
thanks, I'm using 154.0.1.1, I see the pings are the same anyway. I use smartdns for certain media sites so I'm just setting up certain devices on my home network to use the smart dns and everything else CI/1.1.1.1/9.9.9.9/8.8.8.8 (via my router of course).

as I understand it, it's best I stick to using CI's DNS to get the best out of my connection, correct @PBCool ?
Click to expand...
It's complicated, but basically using our DNS will use CDNs on our network for instance. So yes usually best to use your providers DNS.
 
image132 said:
Does that mean we finally have a local twitch server?
Click to expand...
Even though Twitch is owned by AWS they still have their own AS and network from what we have seen. Once AWS launches local infrastructure we might do.
 
image132 said:
Does that mean we finally have a local twitch server?
Click to expand...

Might mean we can get routed over AWS direct for Twitch which should act like a local proxy.

Might be placeboo, but getting 35Mbps and above to Twitch now at 7PM.

1555607054793.png
 
19:15 Twitch completely dead....

Edit: It's back to what it was now. Just a glitch it seems.
 
VegOtter said:
Not really. It depends on the streamer you are watching and where their ingest server is. If it is live feed, twitch will try and serve it straight from there, otherwise you will get "outdated" feed. Or at least that is how I understand it works.
Click to expand...

Nah, the actual hls live video stream is pulled from the nearest twitch CDN server, which in our case is most likely always lhr03 (UK) due to latency and BW. The ingest server has nothing to do with it. Specifically, was watching a US, (Texas) streamer, and the actual stream was being pulled from Poland, upon refresh it changes to Czech Republic, and Amsterdam, randomly. So it most likely has something to do with CISPs upstream providers... Just my guess :/

EDIT: Also I'm not complaining as throughput seems to be fine no matter which server in EU the stream is being pulled from, right now I've got 2 streams open, one is being served from Czech Republic and one from UK and they are both performing equally as well. Just wanted to point it out as it is a new behaviour that I've noticed.

video-edge-748b50.prg02.no-abs.hls.ttvnw.net
video-edge-c61b30.lhr03.no-abs.hls.ttvnw.net
 
Last edited:
Can someone in the JHB region on 1Gbit please do a speedtest to a few servers outside their region ei to CPT and DBN
 
DeatheCore said:
Nah, the actual hls live video stream is pulled from the nearest twitch CDN server, which in our case is most likely always lhr03 (UK) due to latency and BW. The ingest server has nothing to do with it. Specifically, was watching a US, (Texas) streamer, and the actual stream was being pulled from Poland, upon refresh it changes to Czech Republic, and Amsterdam, randomly. So it most likely has something to do with CISPs upstream providers... Just my guess :/

EDIT: Also I'm not complaining as throughput seems to be fine no matter which server in EU the stream is being pulled from, right now I've got 2 streams open, one is being served from Czech Republic and one from UK and they are both performing equally as well. Just wanted to point it out as it is a new behaviour that I've noticed.

video-edge-748b50.prg02.no-abs.hls.ttvnw.net
video-edge-c61b30.lhr03.no-abs.hls.ttvnw.net
Click to expand...

I'm not sure if you saw this

https://mybroadband.co.za/forum/threads/cool-ideas-fibre-isp-feedback.793061/post-23301210

So far it seems to have made a massive difference. Twitch is flawless even now, solid straight line on throughput. Twitter loads lightning fast too.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X