Well, what everyone is doing is opening command prompt and typing in: tracert URL
The tracert shows the latency to each device on the way to the URL that you are connecting to.
Usually the first hop is from your PC to the router, second is to the exchange, third is onto the Afrihost Network.
The second step in the trace route (tracert) often times out due to the new software Telkom installed on their exchange.
In order to get a direct latency report from you to the exchange, use this command in command prompt: ping bras.afrihost.com
The numbers you want: 1ms for a cable to router (hop 1) or <2ms for WiFi (depending on configuration).
<10ms for the second hop / pinging bras.afrihost.com
<40ms for the third hop but this depends on where you are located, in my case Cape Town.
Any hops after that, hopefully not over 200ms if international traffic.
How to copy paste from command prompt:
right-click > select all > enter
Now you can paste it anywhere else.
Use the [code ] code here [/ code] if posting on MyBroadband.
You can also use the Zeratul tools,
Is it my line (Checks if you have congestion/fault) and
one to check if you are having bad latency on the ISP side.
EDIT:
An example of a tracert from me with some comments:
Code:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>tracert afrihost.com
Tracing route to afrihost.com [41.181.185.18]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms home.gateway.pace.net [192.168.1.1] < local network, this is WiFi (slightly congested due to me downloading)
2 * * * Request timed out. <telkom's new software does not allow the exchange to respond to tracerts.
3 33 ms 9 ms 29 ms cpt-up1.ip.adsl.co.za [169.1.5.105] < hop onto Afrihost's network.
4 56 ms 78 ms 32 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 46 ms 29 ms 36 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 37 ms 37 ms 24 ms 41.164.52.40
7 76 ms 46 ms 150 ms 172.18.32.33
8 11 ms 11 ms 12 ms mtnns-2.cinx.net.za [196.223.22.31]
9 13 ms 13 ms 11 ms ^C < you can hit ctrl-c in order to end a tracert/ping in command prompt.
C:\WINDOWS\system32>
EDIT 2:
Quick way to open command prompt:
Hit the windows key and r at the same time. This will open a box called "Run". Type in: cmd
Hit enter.
EDIT 3:
Me pinging my exchange:
Code:
C:\Users\Johnatan56>ping bras.afrihost.com <note that I could also use ping ADDRESS -t which will keep the ping test going until ended with ctrl-c.
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms 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 = 10ms, Maximum = 16ms, Average = 11ms
Sign up with Google