Is something fishy or is it Randburg

S

stretty

Active Member
Joined
Jan 3, 2013
Messages
88
Reaction score
3
Hi Guys

Need some pro advice.

My adsl line just got activated today, moved to Randburg from Centurion.

My DSL experience in Centurion was great, however, same line speed, different experience here.

Iv done a tracert, and want to know if there is anything I can do

C:\Users\Trevor>tracert google.co.za
Tracing route to google.co.za [216.58.223.35]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.2
2 518 ms 555 ms 453 ms 105-236-2-129-esr-lo.mtnbusiness.co.za [105.236.
2.129]
3 432 ms 494 ms 497 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178
.89]
4 392 ms 489 ms 495 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 480 ms 481 ms 438 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 379 ms 385 ms 489 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 499 ms 547 ms 580 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]

8 * 741 ms 754 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.18
7]
9 711 ms 737 ms 792 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.
13]
10 683 ms 746 ms 769 ms 209.85.255.76
11 631 ms 646 ms 691 ms 66.249.95.9
12 644 ms 762 ms 897 ms 72.14.239.129
13 639 ms 634 ms 695 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.

C:\Users\Trevor>
 
Might be something up with your exchange, I'm in Fairland and getting 205ms international and 30ms local ping, my second hop is 6ms where yours is 518ms.
 
I'm in randburg, ADSL is peachy fine.

Your exchange looks bad though. But - try with a trial account from another ISP?
I recommend crystal web.
 
i seem to be having the same issue. only after 5-6 pm till about 12pm.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Inza>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 125 ms 116 ms 116 ms rrdg-ip-esr-2.north.dsl.telkomsa.net [105.224.52
.1]
3 90 ms 84 ms 80 ms ipc-1-up.north.dsl.telkomsa.net [105.224.0.6]
4 72 ms 69 ms 69 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
5 69 ms 70 ms 76 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 90 ms 76 ms 69 ms 196.43.39.166
7 118 ms 112 ms 113 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 115 ms 53 ms 56 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
9 62 ms 61 ms 69 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

C:\Users\Inza>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 287 ms 279 ms 257 ms rrdg-ip-esr-2.north.dsl.telkomsa.net [105.224.52
.1]
3 256 ms 262 ms 235 ms ipc-1-up.north.dsl.telkomsa.net [105.224.0.6]
4 242 ms 234 ms 256 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
5 247 ms 255 ms 240 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 335 ms 333 ms 322 ms 196.43.39.166
7 342 ms 365 ms 382 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 407 ms 428 ms 426 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
9 405 ms 421 ms 438 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

C:\Users\Inza>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 292 ms 295 ms 292 ms rrdg-ip-esr-2.north.dsl.telkomsa.net [105.224.52
.1]
3 366 ms 388 ms 425 ms ipc-1-up.north.dsl.telkomsa.net [105.224.0.6]
4 392 ms 407 ms 392 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
5 446 ms 437 ms 475 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 455 ms 458 ms 462 ms 196.43.39.166
7 165 ms 176 ms 187 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 222 ms 262 ms 230 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
9 292 ms 303 ms 309 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

C:\Users\Inza>ping 155.239.255.250

Pinging 155.239.255.250 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


However as you can see its up and down. its not a constant high latency. usually its around 30-40 local. spikes to around 400, and drops then spikes then drops then spikes. Have no idea if its the exchange but the times would definitely lead to the suspicion.

Anyone lse have any idea on why it would spike so much and so randomly? or is that just general congestion spikes?

Sorry if i threadjack but also looking for answers and telkom is useless with anything regarding helping customers.

Thanks
 
I'm in Malanshof. Same problem. First hop to rrdg-ip-esr-2.north.dsl.telkomsa.net is normally 10ms. But sometimes in the evenings it jumps to 80 - 100ms. Tired other ISP's and it is the same, so I assume it's the dsl exchange.

Tried to speak to Telkom about it, but 1. the say they only make guarantees about the download speed, not the latency, and 2. when ever they send out a technician, the latency is fine. When I want to play, it's slow :-( Grrrr.
 
Code: 
                                       Packets               Pings
 Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. rrdg-ip-esr-2.north.dsl.telkomsa 12.5%    41   82.7 107.4  62.0 134.9  20.9
 2. ipc-1-up.north.dsl.telkomsa.net  12.5%    40   53.4 108.0  53.4 148.8  24.7
 3. ipc-aggr-1.north.telkomsa.net    12.5%    40   43.6 110.4  43.6 227.8  32.6
 4. cen-pr-02-be200-vl1.net.telkomsa 12.5%    40   48.0 110.8  48.0 225.4  29.9
 5. 196.25.166.225                    7.5%    40   75.6 110.1  64.9 139.3  22.4
 6. fra-ip-hsll-1-gig-7-1-0.telkom-i 10.3%    40  332.9 306.5 241.0 338.3  24.1
 7. gw-decix.de.wargaming.net         7.7%    40  323.4 312.1 247.1 378.4  26.3
 8. fr2-a9006-edge-1-be20-2000.warga  2.5%    40  322.5 310.0 259.6 372.0  21.2
 9. 92.223.124.164                    5.1%    40  281.9 304.6 258.5 332.4  21.7
10. fr2-sl-b102.worldoftanks.eu       5.1%    40  245.3 298.8 245.3 329.4  24.3
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X