Degrading Telkom LTE Uncapped speeds

[Dennis]

Hop 5 still ****ty on my side

Trace to www.bbc.co.uk

1 - 192.168.1.254
1 1 1 (ms)
Avg: 1 ms Loss: 0/3 (0 %)
2 -
3 - 172.17.48.9
47 41 37 (ms)
Avg: 41 ms Loss: 0/3 (0 %)
4 - 172.17.48.17
38 40 50 (ms)
Avg: 42 ms Loss: 0/3 (0 %)
5 - 41.150.179.1
8ta-150-179-01.telkomadsl.co.za
469 490 364 (ms)
Avg: 441 ms Loss: 0/3 (0 %)
6 - 196.25.7.73
ndn-ip-hsll-1-wan.telkom-ipnet.co.za
335 352 340 (ms)
Avg: 342 ms Loss: 0/3 (0 %)
7 - 196.43.9.86
450 475 523 (ms)
Avg: 482 ms Loss: 0/3 (0 %)
8 - 62.115.35.89
ldn-b5-link.telia.net
588 484 479 (ms)
Avg: 517 ms Loss: 0/3 (0 %)
9 - 62.115.144.161
atos-ic-315186-ldn-b5.c.telia.net
233 230 230 321 (ms)
Avg: 253 ms Loss: -1/3 (-25 %)
10 -
11 - 132.185.254.105
ae0.er02.telhc.bbc.co.uk
707 627 644 (ms)
Avg: 659 ms Loss: 0/3 (0 %)
12 - 132.185.255.148
720 788 779 (ms)
Avg: 762 ms Loss: 0/3 (0 %)
13 - 212.58.244.70
bbc-vip115.telhc.bbc.co.uk
217 246 207 (ms)
Avg: 223 ms Loss: 0/3 (0 %)

 

[Sneeky]

F you telkom!!!!!!!!!!!


No prizes for guessing who is using telkom lte here

Just not workable, thx, take my money, but f u.

Used to be 200-300ms.

Let it never be said that Telkom prioritizes anything, ever, other than the bottom line.

 

[Sneeky]

Who has Jan Vermeulens (mybb) email or addy or pm.
He is the only bloke with integrity that will help us out here with some straight answers from Telkom.

?

 

[Dennis]

F you telkom!!!!!!!!!!!


No prizes for guessing who is using telkom lte here

Just not workable, thx, take my money, but f u.

Used to be 200-300ms.

Let it never be said that Telkom prioritizes anything, ever, other than the bottom line.

Dude I feel your pain.

Telkom surely you are aware of what's going on on your network???

 

[Sneeky]

Telkom, pff, I just want some answers, and the average Joe like you and me are not going to get them.

I'm hoping MYBB will investigate, and someone like Jan will ask the right questions.

This is rubbish.

edit: after all, this is what MyADSL/MYBB was founded on. Internet accessibility and connectivity and the efficiency thereof.

 

[Sneeky]

So almost vamp hour, and telkom lte dishes out 1000+ms pings to a server that would normally have 300ms pings.

If you planning on playing online chess, Telkom LTE is not for you, to much lag.
The pawn will shag your queen before you can turn your head.

 

[cavedog]

lol yeah wonder who we gonna need to bribe to sort it out

 

[Sneeky]

It is the epitome of failure, at least for this area.

 

[Sneeky]

Tetris! gonna find a slowwwwww tetris server to match our lte I think. Maybe the lag will be beneficial.

To hell with the thousands of rands of flight sim stuff I have, tetris and 4 keys, YES!

 

[Sneeky]

Just after pumkin hour

\

Tracing route to d-216-52-148-29.ded-machine.premium-chicago.nfoservers.com [216.52.148.29]
over a maximum of 30 hops:

1 4 ms 2 ms 4 ms homerouter.cpe [192.168.1.1]
2 * * * Request timed out.
3 45 ms 36 ms 40 ms 172.17.48.9
4 39 ms 38 ms 41 ms 172.17.48.17
5 45 ms 42 ms 51 ms 8ta-150-179-02.telkomadsl.co.za [41.150.179.2]
6 67 ms 59 ms 57 ms 196.25.188.77
7 348 ms 350 ms 323 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.58]
8 369 ms 366 ms 384 ms ldn-b5-link.telia.net [62.115.35.89]
9 324 ms 289 ms 268 ms ldn-bb3-link.telia.net [80.91.248.217]
10 427 ms 413 ms 443 ms nyk-bb1-link.telia.net [80.91.248.203]
11 425 ms 433 ms 398 ms chi-b22-link.telia.net [62.115.141.166]
12 375 ms 357 ms 330 ms telia-1.e8.router1.chicago.nfoservers.com [74.91.113.254]
13 522 ms 519 ms 505 ms d-216-52-148-29.ded-machine.premium-chicago.nfoservers.com [216.52.148.29]

Trace complete.

ping halved, in a few minutes!!!!

 

[Sneeky]

please explain Telkom, you stand up folks of society.

 

[Sneeky]

The difference, before 0000 and just after, nothing changed my side.

Literally a few minutes.
Telkom please explain why you are capping me!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 

[Sneeky]

Proes straat explain (again, excuse the r)

from over 1000ms before midnight to magical sub 300 just after??????????????????

 

[cavedog]

Hope 5 is gone again. Congested like crazy....

Did a quick test and both Band 3 and Band 40 for my tower travels the same route so it stays congested and poor latency and speeds.

 

[Leno]

I assume the following 2 are on different towers, hence different routing

Tower that I connect to on 1800MHz doesnt seem to get congested.

Traceroute when modem forced to 1800MHz

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
 1  192.168.1.2 (192.168.1.2)  9.605 ms  1.321 ms  1.272 ms
 2  * * *
 3  172.17.32.9 (172.17.32.9)  57.249 ms  36.242 ms  40.521 ms
 4  * * *
 5  192.168.102.2 (192.168.102.2)  126.320 ms  60.844 ms  62.774 ms
 6  172.17.32.17 (172.17.32.17)  119.509 ms  66.365 ms  54.274 ms
 7  8ta-150-177-02.telkomadsl.co.za (41.150.177.2)  115.953 ms  50.228 ms  49.544 ms
 8  telkom-sa-mcnet-gw.telkom-ipnet.co.za (196.25.251.126)  83.936 ms
    telkom-sa-mcnet-gw.telkom-ipnet.co.za (196.25.4.118)  147.834 ms
    telkom-sa-mcnet-gw.telkom-ipnet.co.za (196.25.251.126)  37.603 ms
 9  wbs-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.4.117)  129.854 ms  80.619 ms  45.421 ms
10  rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za (196.43.11.134)  127.703 ms  71.159 ms  123.636 ms
11  72.14.212.1 (72.14.212.1)  165.536 ms  120.894 ms  96.814 ms
12  72.14.239.53 (72.14.239.53)  133.819 ms
    72.14.239.33 (72.14.239.33)  113.517 ms  128.898 ms

Modem forced to 2300MHz

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
 1  192.168.1.2 (192.168.1.2)  1.510 ms  1.346 ms  1.149 ms
 2  * * *
 3  172.17.48.13 (172.17.48.13)  65.567 ms  89.852 ms  82.758 ms
 4  172.17.48.21 (172.17.48.21)  72.582 ms  85.287 ms  80.376 ms
 5  8ta-150-179-01.telkomadsl.co.za (41.150.179.1)  477.949 ms  514.187 ms  500.368 ms
 6  ndn-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.7.73)  543.934 ms  638.210 ms  576.151 ms
 7  rrba-ip-lir-1-gig-5-0-0.telkom-ipnet.co.za (196.43.52.38)  569.165 ms  562.200 ms  603.828 ms
 8  72.14.212.1 (72.14.212.1)  594.588 ms  580.451 ms  585.524 ms
 9  72.14.239.33 (72.14.239.33)  535.184 ms
    72.14.239.117 (72.14.239.117)  716.728 ms
    72.14.239.33 (72.14.239.33)  542.387 ms
10  google-public-dns-a.google.com (8.8.8.8)  520.912 ms  556.860 ms *

 

[MDKza]

Just after pumkin hour

ping halved, in a few minutes!!!!

Only this IP seems to be bad for me. Rest of the things I test are fine. What is this thing you are trying to do?

 

[MDKza]

C:\Users\tyty>tracert -d 8.8.8.8

Tracing route to 8.8.8.8 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.100.10
2 * * * Request timed out.
3 71 ms 158 ms 91 ms 172.17.1.13
4 154 ms 63 ms 68 ms 192.168.102.3
5 118 ms 45 ms 60 ms 172.17.1.17
6 57 ms 39 ms 78 ms 172.16.1.205
7 76 ms 40 ms 55 ms 41.150.190.1
8 148 ms 81 ms 112 ms 196.25.181.77
9 84 ms 62 ms 70 ms 196.43.11.134
10 130 ms 54 ms 58 ms 72.14.212.1
11 56 ms 34 ms 45 ms 72.14.239.33
12 63 ms 89 ms 53 ms 8.8.8.8

Trace complete.

C:\Users\tyty>tracert -d 216.52.148.29

Tracing route to 216.52.148.29 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.100.10
2 * * * Request timed out.
3 78 ms 51 ms 47 ms 172.17.1.13
4 117 ms 37 ms 44 ms 192.168.102.3
5 76 ms 25 ms 23 ms 172.17.1.17
6 39 ms 19 ms 30 ms 172.16.1.205
7 39 ms 19 ms 30 ms 41.150.190.2
8 120 ms 84 ms 100 ms 196.25.49.73
9 221 ms 203 ms 194 ms 196.43.9.58
10 338 ms 210 ms 209 ms 62.115.35.89
11 311 ms 265 ms 228 ms 213.155.136.76
12 319 ms 386 ms 400 ms 213.155.135.71
13 353 ms 328 ms 317 ms 62.115.141.168
14 399 ms 309 ms 342 ms 64.74.97.253
15 337 ms 330 ms 314 ms 216.52.148.29

Trace complete.

C:\Users\tyty>tracert -d mybroadband.co.za

Tracing route to mybroadband.co.za [104.20.71.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.100.10
2 * * * Request timed out.
3 190 ms 26 ms 33 ms 172.17.1.13
4 136 ms 36 ms 42 ms 192.168.102.3
5 106 ms 37 ms 45 ms 172.17.1.17
6 82 ms 49 ms 49 ms 172.16.1.205
7 84 ms 42 ms 36 ms 41.150.190.2
8 83 ms 25 ms 30 ms 196.25.82.133
9 85 ms 37 ms 46 ms 196.43.25.138
10 122 ms 67 ms 61 ms 196.46.25.198
11 53 ms 29 ms 23 ms 104.20.71.110

Trace complete.

C:\Users\tyty>tracert -d ewn.co.za

Tracing route to ewn.co.za [41.168.20.229]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.100.10
2 * * * Request timed out.
3 30 ms 30 ms 39 ms 172.17.1.13
4 80 ms 40 ms 30 ms 192.168.102.3
5 80 ms 33 ms 30 ms 172.17.1.17
6 62 ms * 56 ms 172.16.1.205
7 37 ms 38 ms 29 ms 41.150.190.2
8 58 ms 20 ms 19 ms 196.25.49.73
9 38 ms 32 ms 30 ms 196.43.25.138
10 69 ms 25 ms 19 ms 41.160.2.70
11 * * * Request timed out.
12 ^C
C:\Users\tyty>tracert -d news24.com

Tracing route to news24.com [41.86.110.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.100.10
2 * * * Request timed out.
3 195 ms 27 ms 36 ms 172.17.1.13
4 115 ms 36 ms 19 ms 192.168.102.3
5 35 ms 19 ms 31 ms 172.17.1.17
6 36 ms 30 ms 30 ms 172.16.1.205
7 69 ms 30 ms 19 ms 41.150.190.2
8 99 ms 71 ms 58 ms 196.25.216.121
9 63 ms 21 ms 29 ms 196.43.25.138
10 134 ms 30 ms 30 ms 197.80.4.118
11 66 ms 72 ms 74 ms 197.80.7.34
12 144 ms 49 ms 46 ms 197.84.4.34
13 183 ms 154 ms 114 ms 197.84.5.254
14 117 ms 46 ms 57 ms 196.28.178.70
15 107 ms 40 ms 50 ms 196.41.133.166
16 119 ms 49 ms 48 ms 197.84.196.6
17 118 ms 44 ms 45 ms 197.84.208.146
18 88 ms 59 ms 59 ms 41.86.110.143

Trace complete.

C:\Users\tyty>tracert -d cpt-1.valve.net

Tracing route to cpt-1.valve.net [152.111.192.244]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.100.10
2 * * * Request timed out.
3 19 ms 33 ms 29 ms 172.17.1.13
4 62 ms 52 ms 41 ms 192.168.102.3
5 23 ms 30 ms 30 ms 172.17.1.17
6 67 ms 20 ms 20 ms 172.16.1.205
7 59 ms 40 ms 21 ms 41.150.190.2
8 68 ms 20 ms 35 ms 196.25.49.73
9 61 ms 50 ms 50 ms 196.43.25.138
10 43 ms 49 ms 46 ms 197.80.4.118
11 135 ms 81 ms 103 ms 197.80.7.1
12 90 ms 50 ms 52 ms 197.84.4.46
13 112 ms 50 ms 61 ms 197.84.5.254
14 60 ms 44 ms 43 ms 196.28.178.70
15 96 ms 79 ms 61 ms 196.41.144.34
16 110 ms 61 ms 61 ms 196.41.133.234
17 68 ms 44 ms 41 ms 152.111.192.244

Trace complete.

C:\Users\tyty>


Pings are not great all round but that IP seems to be the only really bad one.
Is that even local?

 

[Sneeky]

Only this IP seems to be bad for me. Rest of the things I test are fine. What is this thing you are trying to do?

Pings are not great all round but that IP seems to be the only really bad one.
Is that even local?

Ok, not sure if you have gone through the last few pages of the thread, but this is the problem.

Every night, it just gets worse as the evening progresses.
Typically hop 5 is the problem, that seems ok for now. but the end result is still putrid.

Tracing route to d-216-52-148-29.ded-machine.premium-chicago.nfoservers.com [216.52.148.29]
over a maximum of 30 hops:

1 1 ms 10 ms 9 ms homerouter.cpe [192.168.1.1]
2 * * * Request timed out.
3 38 ms 34 ms 40 ms 172.17.48.9
4 28 ms 53 ms 25 ms 172.17.48.17
5 182 ms 186 ms 172 ms 8ta-150-179-02.telkomadsl.co.za [41.150.179.2]
6 451 ms 434 ms 429 ms 196.25.188.77
7 511 ms 574 ms 597 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.58]
8 776 ms 794 ms 838 ms ldn-b5-link.telia.net [62.115.35.89]
9 779 ms 801 ms 694 ms ldn-bb3-link.telia.net [80.91.248.217]
10 739 ms 744 ms 697 ms nyk-bb1-link.telia.net [80.91.248.203]
11 773 ms 815 ms 882 ms chi-b22-link.telia.net [62.115.141.166]
12 900 ms 859 ms 840 ms telia-1.e8.router1.chicago.nfoservers.com [74.91.113.254]
13 842 ms 813 ms 807 ms d-216-52-148-29.ded-machine.premium-chicago.nfoservers.com [216.52.148.29]

People in other areas that pinged the same server dont have issue.
Its seems to be KZN from PMB to DBN to RBY.

Do you think this is acceptable?
The server used to, for many months ping at 250-350, it still does at pumpkin hour.
Its not specific to that server, it can be any offshore server be it BBC or whatever.

Net result is no gaming, and netflix looking like a 8 bit game from the 80's.

 

[Sneeky]

Spectacular Telkom LTE

Hop 5 seems to be better than the last few weeks, maybe they are trying to resolve, I dunno, they say nothing, but again, end result still horrible.

Tracing route to d-216-52-148-29.ded-machine.premium-chicago.nfoservers.com [216.52.148.29]
over a maximum of 30 hops:

1 4 ms 8 ms 9 ms homerouter.cpe [192.168.1.1]
2 * * * Request timed out.
3 167 ms 26 ms 38 ms 172.17.48.9
4 38 ms 38 ms 39 ms 172.17.48.17
5 139 ms 134 ms 119 ms 8ta-150-179-02.telkomadsl.co.za [41.150.179.2]
6 484 ms 470 ms 483 ms 196.25.188.77
7 577 ms 604 ms 580 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.58]
8 806 ms 826 ms 750 ms ldn-b5-link.telia.net [62.115.35.89]
9 792 ms 719 ms 763 ms ldn-bb3-link.telia.net [80.91.248.217]
10 724 ms 732 ms 689 ms nyk-bb1-link.telia.net [80.91.248.203]
11 775 ms 745 ms 782 ms chi-b22-link.telia.net [62.115.141.166]
12 844 ms 839 ms 784 ms telia-1.e8.router1.chicago.nfoservers.com [74.91.113.254]
13 1008 ms 1043 ms 1058 ms d-216-52-148-29.ded-machine.premium-chicago.nfoservers.com [216.52.148.29]

 

[cavedog]

Spectacular Telkom LTE

What I don't understand is how the hell they did not notice the congestion on the backhaul yet.....