Telkom Internet Capped/Uncapped User Feedback (Pt2)

ranger said:
Can you try with winmtr or pingplotter or mtr?

The high variability indicates something in the path is near congestion, and traceroute can give an incorrect view of the problem, where the other tools that ping all the hops simultaneously gives a better picture of where the problem is.
Click to expand...

Tried WinMTR a few minutes ago. Here's my results:

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| Billion.400G - 0 | 811 | 811 | 0 | 0 | 31 | 0 |

| wtvw-ip-bb-1.south.dsl.telkomsa.net - 0 | 811 | 811 | 10 | 25 | 155 | 32 |

| ipc-4-up.south.dsl.telkomsa.net - 0 | 811 | 811 | 13 | 27 | 152 | 36 |

| ipc-aggr-2.south.dsl.telkomsa.net - 0 | 811 | 811 | 13 | 27 | 155 | 36 |

| blv-pr-01-be200-vl1.net.telkomsa.net - 0 | 811 | 811 | 50 | 116 | 236 | 143 |

| jb1-pr-01-te1-0.net.telkomsa.net - 0 | 811 | 811 | 73 | 136 | 269 | 152 |

| jb1-pr-01-te1-0.net.telkomsa.net - 0 | 811 | 811 | 72 | 136 | 268 | 152 |

| jb1-google-gw.net.telkomsa.net - 0 | 811 | 811 | 35 | 47 | 175 | 56 |

| 72.14.237.239 - 0 | 811 | 811 | 36 | 47 | 174 | 58 |

| jnb01s07-in-f3.1e100.net - 0 | 811 | 811 | 72 | 135 | 269 | 156 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Click to expand...
 
Having very high pings tonight , Milnerton,Cape Town area

C:\Users\>ping telkom.co.za
Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=240ms TTL=245
Reply from 196.43.22.222: bytes=32 time=244ms TTL=245
Reply from 196.43.22.222: bytes=32 time=217ms TTL=245
Reply from 196.43.22.222: bytes=32 time=209ms TTL=245

Ping statistics for 196.43.22.222:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 209ms, Maximum = 244ms, Average = 227ms

C:\Users\>tracert www.telkom.co.za
Tracing route to www.telkom.co.za [165.143.158.60]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway [192.168.1.254]
2 8 ms 8 ms 8 ms wtvw-ip-bng-1.south.dsl.telkomsa.net [105.224.24
8.1]
3 268 ms 264 ms 259 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
4 223 ms 223 ms 231 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]

5 210 ms 213 ms 219 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 236 ms 235 ms 232 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.4
3.25.58]

Trace complete.

C:\Users\>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.244.26]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms home.gateway [192.168.1.254]
2 9 ms 8 ms 8 ms wtvw-ip-bng-1.south.dsl.telkomsa.net [105.224.24
8.1]
3 235 ms 231 ms 230 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
4 221 ms 216 ms 212 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]

5 201 ms 204 ms 192 ms 196.25.103.93
6 565 ms 566 ms 558 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.46]
7 633 ms 658 ms 678 ms ldn-b5-link.telia.net [62.115.35.89]
8 581 ms 555 ms 574 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.14
2]
9 * * * Request timed out.
10 542 ms 523 ms 503 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 660 ms 629 ms 624 ms 132.185.255.149
12 469 ms 483 ms 494 ms bbc-vip145.telhc.bbc.co.uk [212.58.244.26]
 
I'm also in Cape Town and have huge lag. Another problem I still have is my download speeds and Speedtest speeds hover at around the 2 meg mark but I have a 4 meg line that syncs at 4 meg. Chatted to Telkom and according to them there is no fault on my line.
 
elf_lord_ZC5 said:
Probably connected to a 2mb line from the box to the exchange ... , possible ...
Click to expand...

Don't see how that's possible because how would I then sync at 4 meg. It's only been like this in the last few months and I've had the line for a few years with full 4 meg speeds.
 
There is fiber at the street corner box, good cable from me to the box, but the box only has 2mb port cards in it ... , so I can only get 2mb and not 40mb or better ...

So the port cards are the bottleneck or choke point ...
 
Hi Ranger, i am wondering if you can help.

I normally game with a ping of between 40 and 60. All of a sudden I am having terrible issues with ping and it seems to be to all CPT servers. The JHB ones are OK but I get between 260 and 280 now to all CPT servers. I am in northern KZN.

Thanks man
 
cant browse a single video on youtube tonight with Telkom. So tired of this... I been having issues with Telkom for weeks and after phoning support they say nothing is wrong with my line
 
Kyubi_ZA said:
cant browse a single video on youtube tonight with Telkom. So tired of this... I been having issues with Telkom for weeks and after phoning support they say nothing is wrong with my line
Click to expand...

Might be related to post #6102-6106 above.
 
Going on 72 hours without Internet now in Lonehill jhb. Telkom logged a fault but no follow up.... Annoyed beyond belief with the lack of service. No line or data
 
Typical Telkom, when things work, alls well most of the time, when they don't - well no one tells you anything, and service does not exist. Wish someone could explain to them the value of "feedback"
 
tracert www.google.co.za

Tracing route to www.google.co.za [216.58.223.35] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 981 ms 1754 ms 3205 ms wbs-ip-hsll-2-gi4-0-0-vl102.telkom-ipnet.co.za [105.226.0.21]
4 669 ms 1282 ms 623 ms ipc-2-up.south.dsl.telkomsa.net [105.226.0.22]
5 196 ms 31 ms 485 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
6 129 ms 247 ms 306 ms blv-pr-01-be200-vl1.net.telkomsa.net [105.226.0.53]
7 397 ms 99 ms 38 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]
8 2674 ms 1450 ms 1278 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]
9 103 ms 101 ms 217 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]
10 697 ms 364 ms 363 ms 72.14.239.129
11 199 ms 102 ms 1317 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.

-_-
 
MickeyD said:
try these:
tracert capetown.spdtst.saix.net
tracert rosebank.spdtst.saix.net
Click to expand...

tracert capetown.spdtst.saix.net

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 1050 ms 1839 ms 1086 ms wbs-ip-hsll-2-gi3-1-0-vl102.telkom-ipnet.co.za [105.226.0.29]
4 57 ms 909 ms 877 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
5 353 ms 288 ms 733 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
6 517 ms 430 ms 78 ms 196.25.190.209
7 388 ms 647 ms 42 ms wbs-ip-hsll-1-gig-2-1-0.telkom-ipnet.co.za [196.43.52.62]
8 52 ms 59 ms 24 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [196.25.37.2]
9 241 ms 30 ms 61 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]


Trace complete.

tracert rosebank.spdtst.saix.net

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 3976 ms 2934 ms * wbs-ip-hsll-2-gi4-0-0-vl102.telkom-ipnet.co.za [105.226.0.21]
4 * * 3077 ms ipc-2-up.south.dsl.telkomsa.net [105.226.0.22]
5 * 3228 ms 2339 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
6 1726 ms 239 ms 52 ms 165.165.214.213
7 158 ms 97 ms 78 ms 196.43.39.74
8 168 ms 114 ms 59 ms rrba-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za[196.25.45.90]
9 * 55 ms 141 ms 196.25.45.102

Trace complete.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X