Is my adsl exchange congested ?

GODZILLA99

Well-Known Member
Joined
Aug 24, 2010
Messages
211
Reaction score
0
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\WESLEY>tracert telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1. 1 ms <1 ms 1 ms 10.0.0.2
2. 59 ms 58 ms 58 ms dsl-146-0-01.telkomadsl.co.za [41.146.0.1]
3. 70 ms 70 ms 69 ms 196.43.39.162
4. 70 ms 73 ms 78 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za 196.43.23.6]
5. 73 ms 71 ms 71 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za 196.43.23.34]
6. 73 ms 72 ms 72 ms telkom.co.za [196.43.22.222]

Trace complete.

C:\Users\WESLEY>


Hi everyone can you please tell me whether my exchange is congested
because I don't know how this works.
 
It doesn't seem so. The 2nd hop is usually a lot higher (200+) if the exchange is congested. I might be wrong though.
 
59ms is high but it's not excessively so. As above, if you're getting 200+ it's bad.
 
Here is my tracert. I'm using Afrihost.

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

tracert telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 8 ms 7 ms 7 ms 105-236-1-65-esr-lo.mtnbusiness.co.za [105.236.1
.65]
3 9 ms 8 ms 8 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178
.17]
4 8 ms 8 ms 9 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 8 ms 8 ms 8 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
6 9 ms 8 ms 9 ms 41.181.139.109
7 10 ms 10 ms 9 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.1
7]
8 10 ms 10 ms 9 ms 196.43.25.137
9 9 ms 9 ms 10 ms 196.43.39.162
10 17 ms 10 ms 10 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
11 13 ms 13 ms 20 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
12 13 ms 13 ms 13 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.
 
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\WESLEY>tracert telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1. 1 ms <1 ms 1 ms 10.0.0.2
2. 59 ms 58 ms 58 ms dsl-146-0-01.telkomadsl.co.za [41.146.0.1]
3. 70 ms 70 ms 69 ms 196.43.39.162
4. 70 ms 73 ms 78 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za 196.43.23.6]
5. 73 ms 71 ms 71 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za 196.43.23.34]
6. 73 ms 72 ms 72 ms telkom.co.za [196.43.22.222]

Trace complete.

C:\Users\WESLEY>


Hi everyone can you please tell me whether my exchange is congested
because I don't know how this works.

You are in Pietermaritzburg, so first hop 60ms is a bit on the slow side, but not out of the ordinary. Your exchange is probably fine. I guess it is connected to the Durban or Cape Town IPC, which means roughly +30ms either way to ping a server in Joburg.
 
Top
Sign up to the MyBroadband newsletter
X