South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
There does look to have been a momentary hiccup in the Southern Region, but it looks like things are back to normal now.
Can you guys please test and advise on your current experience.
There does look to have been a momentary hiccup in the Southern Region, but it looks like things are back to normal now.
Can you guys please test and advise on your current experience.
The North IPC link is still down, so speeds in the North will still be off momentarily.
Telkom is in the process of bringing the link back up now.
In Durban, Youtube still defaults to 480p on a 20MB connection. Setting to 1080p and it hardly keeps ahead with the odd buffer.
Speedtest is fine with 17 down and 0.8 up.
Could you please run a traceroute to Afrihost.com, I just want to make sure you are resolving to the local Google cache.
Looks like I'm going to the UK and back to JHB. Why is hop #5 so high, is that Rosebank?
C:\Users\Me>tracert www.youtube.com
Tracing route to youtube-ui.l.google.com [74.125.233.0]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 6 ms 6 ms 105-236-14-1-esr-lo.mtnbusiness.co.za [105.236.14.1]
3 16 ms 16 ms 16 ms 41.181.221.218
4 16 ms 16 ms 16 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
5 222 ms 222 ms 222 ms rb-cr-2.za--rb-dca-2.za-b.mtnns.net [196.44.0.155]
6 222 ms 222 ms 221 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
7 214 ms 214 ms 215 ms ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.114]
8 221 ms 221 ms 240 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.187]
9 221 ms 222 ms 222 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.13]
10 226 ms 224 ms 230 ms 209.85.255.76
11 197 ms 197 ms 198 ms 66.249.95.9
12 198 ms 197 ms 197 ms 72.14.237.239
13 197 ms 197 ms 197 ms jnb01s07-in-f0.1e100.net [74.125.233.0]
Trace complete.
I believe hop 5 is where the connection joins one of the undersea links.
Which region are you in?
Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 50 ms 52 ms 53 ms 41.181.221.213
4 45 ms 60 ms 39 ms 41.181.221.214
5 62 ms 59 ms 40 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
6 58 ms 45 ms 45 ms rb-dca-2.za--rb-cr-1.mtnns.net [196.44.31.122]
7 45 ms 57 ms 117 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
8 101 ms 39 ms 40 ms 196.31.220.12
9 43 ms 43 ms 51 ms 196.31.220.25
10 42 ms 45 ms 39 ms 196.31.63.206
11 47 ms 52 ms 48 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
12 93 ms 56 ms 47 ms cms-gm.afrihost.com [197.242.144.102]
Trace complete.
Pinging bbc.co.uk [212.58.244.18] with 32 bytes of data:
Reply from 212.58.244.18: bytes=32 time=228ms TTL=50
Reply from 212.58.244.18: bytes=32 time=264ms TTL=50
Reply from 212.58.244.18: bytes=32 time=301ms TTL=50
Reply from 212.58.244.18: bytes=32 time=307ms TTL=50
The circle is complete![]()
The circle is complete![]()
I am having excellent speeds. Things are really looking up*touch wood
Something strange that I have never seen is happening, however: my 2nd hop (exchange?) is coming up with Request timed out.
Code:Tracing route to afrihost.com [197.242.144.102] over a maximum of 30 hops: 1 1 ms 1 ms <1 ms 10.0.0.2 2 * * * Request timed out. 3 50 ms 52 ms 53 ms 41.181.221.213 4 45 ms 60 ms 39 ms 41.181.221.214 5 62 ms 59 ms 40 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118] 6 58 ms 45 ms 45 ms rb-dca-2.za--rb-cr-1.mtnns.net [196.44.31.122] 7 45 ms 57 ms 117 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221] 8 101 ms 39 ms 40 ms 196.31.220.12 9 43 ms 43 ms 51 ms 196.31.220.25 10 42 ms 45 ms 39 ms 196.31.63.206 11 47 ms 52 ms 48 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133] 12 93 ms 56 ms 47 ms cms-gm.afrihost.com [197.242.144.102] Trace complete.
Is that the exchange? Should I be worried?
Also, ping is a little high in comparison to other ISPs. My mates in the same area on other ISPs get 205~220ms international (gaming). I get 230 minimum and it spikes up to ~310ms every now and then.
Code:Pinging bbc.co.uk [212.58.244.18] with 32 bytes of data: Reply from 212.58.244.18: bytes=32 time=228ms TTL=50 Reply from 212.58.244.18: bytes=32 time=264ms TTL=50 Reply from 212.58.244.18: bytes=32 time=301ms TTL=50 Reply from 212.58.244.18: bytes=32 time=307ms TTL=50