Nikkel
Expert Member
Did some random tests this morning just for interest sake... Ookla speedtest results were all over the place but got consistent results with MyBB speedtests
Just a question: Why does the 2nd hop time out on the trace routes? (not in the know just to gain some more knowledge)

http://netgauge.ookla.com/share/532503862.png
http://netgauge.ookla.com/share/532504173.png
C:\Windows\system32>ping bras.afrihost.com
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 11ms, Average = 11ms
C:\Windows\system32>tracert afrihost.com
Tracing route to afrihost.com [104.20.30.244]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * 14 ms 12 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 14 ms 12 ms 12 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 15 ms 20 ms 12 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 13 ms 12 ms 12 ms 41.164.52.40
7 34 ms 33 ms 33 ms 172.18.1.162
8 34 ms 34 ms 34 ms cloudflare.ixp.joburg [196.46.25.198]
9 34 ms 35 ms 35 ms 104.20.30.244
Trace complete.
C:\Windows\system32>tracert google.com
Tracing route to google.com [169.1.2.87]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 12 ms 11 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 14 ms 12 ms 12 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 12 ms 12 ms 11 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 14 ms 12 ms 12 ms 169-1-21-9.ip.afrihost.co.za [169.1.21.9]
7 12 ms 12 ms 12 ms 169-1-2-87.ip.afrihost.co.za [169.1.2.87]
Trace complete.
Just a question: Why does the 2nd hop time out on the trace routes? (not in the know just to gain some more knowledge)

http://netgauge.ookla.com/share/532503862.png
http://netgauge.ookla.com/share/532504173.png
C:\Windows\system32>ping bras.afrihost.com
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 11ms, Average = 11ms
C:\Windows\system32>tracert afrihost.com
Tracing route to afrihost.com [104.20.30.244]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * 14 ms 12 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 14 ms 12 ms 12 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 15 ms 20 ms 12 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 13 ms 12 ms 12 ms 41.164.52.40
7 34 ms 33 ms 33 ms 172.18.1.162
8 34 ms 34 ms 34 ms cloudflare.ixp.joburg [196.46.25.198]
9 34 ms 35 ms 35 ms 104.20.30.244
Trace complete.
C:\Windows\system32>tracert google.com
Tracing route to google.com [169.1.2.87]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 12 ms 11 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 14 ms 12 ms 12 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 12 ms 12 ms 11 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 14 ms 12 ms 12 ms 169-1-21-9.ip.afrihost.co.za [169.1.21.9]
7 12 ms 12 ms 12 ms 169-1-2-87.ip.afrihost.co.za [169.1.2.87]
Trace complete.