Telkom Internet Capped/Uncapped User Feedback (Pt2)

Tracing route to jb1-google-gw.net.telkomsa.net [105.187.249.22]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms home.gateway [10.0.0.2]
2 9 ms 10 ms 8 ms wblv-ip-esr-3.south.dsl.telkomsa.net [105.224.80
.1]
3 177 ms 181 ms 176 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 160 ms 162 ms 161 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]

5 224 ms 219 ms 221 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]

6 212 ms 217 ms 221 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]

7 211 ms 210 ms 207 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]


Trace complete.
Click to expand...

#latencymustfall
 
Big Bean said:
#latencymustfall
Click to expand...

Hmmm

[Tracing route to jb1-google-gw.net.telkomsa.net [105.187.249.22]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 6 ms 5 ms 5 ms ipc-1-up.east.dsl.telkomsa.net [105.229.0.5]
4 24 ms 19 ms 5 ms ipc-1-up.east.dsl.telkomsa.net [105.229.0.6]
5 12 ms 5 ms 6 ms ipc-aggr-2.east.dsl.telkomsa.net [105.229.0.13]

6 19 ms 19 ms 19 ms jb1-pr-01-te8-3.net.telkomsa.net [105.187.249.2]

7 41 ms 40 ms 32 ms jb1-pr-01-te8-3.net.telkomsa.net [105.187.249.2]

8 19 ms 19 ms 19 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]
Click to expand...
 
Yep... here we go. :mad:


tracert durban.spdtst.saix.net

Tracing route to ndn-ip-dlr-1-1.telkom-ipnet.co.za [196.25.42.118] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 119 ms 115 ms 120 ms wbs-ip-hsll-2-gi3-1-0-vl102.telkom-ipnet.co.za [105.226.0.29]
4 108 ms 114 ms 117 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
5 110 ms 110 ms 105 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
6 98 ms 102 ms 103 ms 196.25.190.209
7 118 ms 117 ms 116 ms 196.43.51.246
8 163 ms 163 ms 158 ms 196.25.42.106
9 172 ms 169 ms 165 ms 196.25.42.118

Trace complete.
 
ghostR said:
run a tracert to a cs server, let's see where the latency is coming in for you.
Click to expand...

mine just times out check this:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 15 ms 14 ms 13 ms ipc-up-2.north.telkomsa.net [105.228.0.5]
4 15 ms 13 ms 13 ms ipc-up-2.north.telkomsa.net [105.228.0.6]
5 14 ms 13 ms 13 ms ipc-aggr-2.north.telkomsa.net [105.228.0.13]
6 14 ms 14 ms 13 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]
7 16 ms 16 ms 16 ms mweb.jb1.napafrica.net [196.46.25.145]
8 15 ms 15 ms 15 ms 101.bu-ether5.vic-pe-1.optinet.net [197.80.7.9]
9 15 ms 14 ms 16 ms bu-ether3.mca-pe-1.optinet.net [197.80.4.37]
10 16 ms 15 ms 15 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
 
Last edited:
Another CS server:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 14 ms 14 ms 13 ms ipc-up-2.north.telkomsa.net [105.228.0.5]
4 15 ms 14 ms 14 ms ipc-up-2.north.telkomsa.net [105.228.0.6]
5 43 ms 15 ms 14 ms ipc-aggr-2.north.telkomsa.net [105.228.0.13]
6 15 ms 15 ms 15 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]
7 18 ms 16 ms 16 ms optinet.jb1.napafrica.net [196.46.25.120]
8 35 ms 34 ms 34 ms 197-80-4-194.jhb.mweb.co.za [197.80.4.194]
9 36 ms 37 ms 36 ms bu-ether2.tis-pe-2.optinet.net [197.80.4.253]
10 39 ms 36 ms 36 ms bu-ether1.vic-pe-2.optinet.net [197.80.4.8]
11 37 ms 38 ms 38 ms te0-0-0-3.vic-p-1.optinet.net [197.80.7.65]
12 36 ms 38 ms 37 ms te0-0-0-0.cpt-p-2.optinet.net [197.84.4.46]
13 36 ms 34 ms 34 ms vl12.cpt-hscore-2.optinet.net [197.84.5.254]
14 37 ms 36 ms 35 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
15 35 ms 34 ms 33 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.

again with the timeouts... In the server im roughly getting 500ping tonight...
 
ghostR said:
You are on the east IPC... The problem is in cape town and surrounds.
Click to expand...

Yeah but I've also been having problems these last few weeks, it seems to have only rectified itself late last night/early this morning.
 
ghostR said:
Clearly if users have noticed it here... And now proof has been provided... Something should be done by TI, right?
Click to expand...


why don't mybroadband post an article about it should make an interesting read
maybe then telkom will do something about it
 
Wholesale still isn't able to deliver the full IPC upgrade now, but they are busy upgrading to provide as much as they can currently provide with the available transmission to the Cape Town site. However, they won't be finished in time for a guaranteed improvement tonight, but it should be better tomorrow.

The delivery of the rest of the IPC upgrade has been escalated as high as it can go ...
 
ranger said:
Wholesale still isn't able to deliver the full IPC upgrade now, but they are busy upgrading to provide as much as they can currently provide with the available transmission to the Cape Town site. However, they won't be finished in time for a guaranteed improvement tonight, but it should be better tomorrow.

The delivery of the rest of the IPC upgrade has been escalated as high as it can go ...
Click to expand...

What are the steps in latency, it's almost as if it's being routed to different IPC links at different times of the day, generally around 8am and 5/6pm.

Telkom-DSL-BRAS_last_604800.png
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X