Degrading Telkom LTE Uncapped speeds

[MDKza]

Try putting the sim into a smartphone or tablet then use something like Opensignal.
https://opensignal.com/android/

That app is super amazing. Thanks.

 

[Sneeky]

I only dabbled with it, but glad it is helping you in what you are trying to do or establish.

 

[Dennis]

Telkom LTE 22H50

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=422 ms
64 bytes from 8.8.8.8: NM icmp_seq=2 ttl=55 time=431 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=55 time=391 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=55 time=384 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 6017ms
min = 384.125 ms
avg = 407.487 ms
max = 431.590 ms
mdev = 20.116 ms

MTN LTE 22H52

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=40.0 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=52.0 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=55 time=44.1 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=55 time=52.1 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 no received, 0% packet loss, time 6026ms
min = 40.083 ms
avg = 47.132 ms
max = 52.180 ms
mdev = 5.208 ms

 

[cavedog]

I only dabbled with it, but glad it is helping you in what you are trying to do or establish.

I think the Telkom backhaul link for mobile is congested..... The latency and slow speeds do not occur on the tower I think... Latency on hop 5 is through the roof and is causing massive speed degradation.....

 

[Sneeky]

I think the Telkom backhaul link for mobile is congested..... The latency and slow speeds do not occur on the tower I think... Latency on hop 5 is through the roof and is causing massive speed degradation.....

That is consistent with our findings to date
http://mybroadband.co.za/vb/showthr...als-So-Far?p=17938583&viewfull=1#post17938583

The question is whose ass needs kissing to get it resolved?

Telkom don't seem to be listening to the paying customer.

 

[FlashSA]

I think the Telkom backhaul link for mobile is congested..... The latency and slow speeds do not occur on the tower I think... Latency on hop 5 is through the roof and is causing massive speed degradation.....

Which link though, because all 3 towers where I am running 3 of these uncapped solutions do not suffer from this peak crawl?

 

[Pho3nix]

So glad I didn't buy this. Telkom LTE as k@k as usual.

Starts not working after 4-6 months of it working beautifully ?

 

[Sneeky]

Which link though, because all 3 towers where I am running 3 of these uncapped solutions do not suffer from this peak crawl?

Its the 41.150.179.x (x=1 or 2)that is causing issue for many here in KZN.
Its typically the 5th hop on a tracert and the ip is located at Telkom HQ in Pretoria.

 

[FlashSA]

Its the 41.150.179.x (x=1 or 2)that is causing issue for many here in KZN.
Its typically the 5th hop on a tracert and the ip is located at Telkom HQ in Pretoria.

But then surely back haul from EL towers should terminate at Telkom HQ as well?

 

[Sneeky]

Im no guru but some of the tracerts to the same server overseas where the user was not experiencing a problem did not feature that ip address which is located in and around Proes street. apologies for the r.

see here for instance.
http://mybroadband.co.za/vb/showthr...als-So-Far?p=17919389&viewfull=1#post17919389

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 <1 ms <1 ms homerouter.cpe [192.168.8.1]
2 * * * Request timed out.
3 71 ms 76 ms 79 ms 10.164.32.73
4 78 ms 78 ms 81 ms 10.164.32.82
5 87 ms 90 ms 69 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
6 88 ms 91 ms 80 ms rndf-ip-hsll-2-wan.telkom-ipnet.co.za [165.165.216.221]
7 251 ms 251 ms 246 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.43.9.46]
8 267 ms 256 ms 279 ms ldn-b5-link.telia.net [62.115.35.89]
9 267 ms 271 ms 259 ms ldn-bb3-link.telia.net [80.91.247.91]
10 410 ms 343 ms 320 ms nyk-bb1-link.telia.net [213.155.133.149]
11 354 ms 363 ms 353 ms chi-b22-link.telia.net [62.115.141.166]
12 375 ms 398 ms 361 ms telia-1.e8.router1.chicago.nfoservers.com [74.91.113.254]
13 359 ms 373 ms 366 ms d-216-52-148-29.ded-machine.premium-chicago.nfoservers.com [216.52.148.29]

Trace complete.

41.150.179.x MIA
one of mine

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 3 ms 4 ms 3 ms homerouter.cpe [192.168.1.1]
2 * * * Request timed out.
3 47 ms 35 ms 39 ms 172.17.48.13
4 28 ms 39 ms 38 ms 172.17.48.21
5 620 ms 578 ms 571 ms 8ta-150-179-02.telkomadsl.co.za [41.150.179.2]
6 912 ms 928 ms 947 ms 196.25.188.77
7 775 ms 837 ms 856 ms lon-ip-dir-telecity-pos-1-1-0.telkom-ipnet.co.za [196.43.9.50]
8 1315 ms 1298 ms 1353 ms ldn-b5-link.telia.net [62.115.35.89]
9 1210 ms 1159 ms 1147 ms ldn-bb3-link.telia.net [213.155.132.194]
10 1761 ms 1574 ms 1449 ms nyk-bb1-link.telia.net [62.115.135.94]
11 896 ms 1007 ms 996 ms chi-b22-link.telia.net [62.115.141.166]
12 1449 ms 1491 ms 1549 ms telia-1.e8.router1.chicago.nfoservers.com [74.91.113.254]
13 1675 ms 1702 ms 1555 ms d-216-52-148-29.ded-machine.premium-chicago.nfoservers.com [216.52.148.29]

Trace complete.

 

[cavedog]

80Mbps+ speedtest now and see the latency on the tower is the same as when there is congestion on hop 5.

Must be backhaul congestion I'm sure of it. No way the latency will stay the same on the tower if it is the tower that is getting congested....

Now who do we call to fix?

41.150.179.2 is the problem and I'm sure they would have picked up that it is congested so why don't they fix it?

That point must be handling a lot of traffic. Think of just 15 towers maxing their bandwidth would be over 1Gbps traffic on that part of the network.

People that are experiencing slow speeds and high latency during 6pm and 10pm need to post some tracert to bbc.co.uk or anywhere so we can see if everyone getting slow speeds are getting the degradation on 41.150.179.2 usually hop 5

 

[Sneeky]

80Mbps+ speedtest now and see the latency on the tower is the same as when there is congestion on hop 5.

Must be backhaul congestion I'm sure of it. No way the latency will stay the same on the tower if it is the tower that is getting congested....

Now who do we call to fix?

41.150.179.2 is the problem and I'm sure they would have picked up that it is congested so why don't they fix it?

That point must be handling a lot of traffic. Think of just 15 towers maxing their bandwidth would be over 1Gbps traffic on that part of the network.

People that are experiencing slow speeds and high latency during 6pm and 10pm need to post some tracert to bbc.co.uk or anywhere so we can see if everyone getting slow speeds are getting the degradation on 41.150.179.2 usually hop 5

Mine from a few secs ago

5. 67 ms 59 ms 62 ms 8ta-150-179-02.telkomadsl.co.za [41.150.179.2]

Hop 5 still looking good for now, but experience tells me it will go tits up around 1900

 

[Dan C]

Its the 41.150.179.x (x=1 or 2)that is causing issue for many here in KZN.
Its typically the 5th hop on a tracert and the ip is located at Telkom HQ in Pretoria.

Seems our IP range is different here in EL.



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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 192.168.8.1
3 * * * Request timed out.
4 79 ms 74 ms 70 ms 10.164.32.69
5 87 ms 71 ms 81 ms 10.164.32.66
6 79 ms 70 ms 81 ms ipc-aggr-2.north.telkomsa.net [105.228.0.13]
7 72 ms 79 ms 74 ms rrba-ip-hsll-2-wan.telkom-ipnet.co.za [165.165.216.217]
8 257 ms 242 ms 237 ms lon-ip-dir-telecity-pos-1-1-0.telkom-ipnet.co.za [196.43.9.50]
9 248 ms 249 ms 264 ms ldn-b5-link.telia.net [62.115.35.89]
10 267 ms 244 ms 249 ms atos-ic-315186-ldn-b5.c.telia.net [62.115.144.161]
11 * * * Request timed out.
12 259 ms 247 ms 249 ms ae0.er02.telhc.bbc.co.uk [132.185.254.105]
13 261 ms 278 ms 266 ms 132.185.255.148
14 268 ms 265 ms 249 ms bbc-vip111.telhc.bbc.co.uk [212.58.244.66]

Trace complete.

 

[Sneeky]

Seems our IP range is different here in EL.



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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 192.168.8.1
3 * * * Request timed out.
4 79 ms 74 ms 70 ms 10.164.32.69
5 87 ms 71 ms 81 ms 10.164.32.66
6 79 ms 70 ms 81 ms ipc-aggr-2.north.telkomsa.net [105.228.0.13]
7 72 ms 79 ms 74 ms rrba-ip-hsll-2-wan.telkom-ipnet.co.za [165.165.216.217]
8 257 ms 242 ms 237 ms lon-ip-dir-telecity-pos-1-1-0.telkom-ipnet.co.za [196.43.9.50]
9 248 ms 249 ms 264 ms ldn-b5-link.telia.net [62.115.35.89]
10 267 ms 244 ms 249 ms atos-ic-315186-ldn-b5.c.telia.net [62.115.144.161]
11 * * * Request timed out.
12 259 ms 247 ms 249 ms ae0.er02.telhc.bbc.co.uk [132.185.254.105]
13 261 ms 278 ms 266 ms 132.185.255.148
14 268 ms 265 ms 249 ms bbc-vip111.telhc.bbc.co.uk [212.58.244.66]

Trace complete.

Seems you going a similar route to Cara. Lucky buggers

 

[Sneeky]

Seems our IP range is different here in EL.

Traced the bbc as well.

Its already starting to go pear shaped, see the infamous hop 5 compared to 15-20minutes ago.

Tracing route to bbc-vip111.telhc.bbc.co.uk [212.58.244.66]
over a maximum of 30 hops:

1 4 ms 3 ms 2 ms homerouter.cpe [192.168.1.1]
2 * * * Request timed out.
3 33 ms 162 ms 34 ms 172.17.48.13
4 47 ms 49 ms 29 ms 172.17.48.21
5 148 ms 136 ms 129 ms 8ta-150-179-02.telkomadsl.co.za [41.150.179.2]
6 220 ms 218 ms 201 ms ndn-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.90.33]
7 418 ms 420 ms 404 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.43.9.46]
8 400 ms 399 ms 414 ms ldn-b5-link.telia.net [62.115.35.89]
9 312 ms 297 ms 312 ms atos-ic-315186-ldn-b5.c.telia.net [62.115.144.161]
10 * * * Request timed out.
11 317 ms 310 ms 307 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
12 392 ms 354 ms 369 ms 132.185.255.148
13 373 ms 395 ms 404 ms bbc-vip111.telhc.bbc.co.uk [212.58.244.66]

Trace complete.

67ms --> 148ms in a matter of minutes

 

[cavedog]

And she's gone.....

 

[Dan C]

And she's gone.....

oh dear... did one just now and still the same.

 

[Sneeky]

And she's gone.....

Yup, thar she blows, going south fast.

Earlier tracert (hop 5) around 1735 at 67ms

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 6 ms 3 ms 4 ms homerouter.cpe [192.168.1.1]
2 * * * Request timed out.
3 43 ms 36 ms 40 ms 172.17.48.9
4 40 ms 38 ms 39 ms 172.17.48.17
5 67 ms 59 ms 62 ms 8ta-150-179-02.telkomadsl.co.za [41.150.179.2]
6 113 ms 124 ms 122 ms 196.25.188.77
7 330 ms 311 ms 310 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.58]
8 422 ms 426 ms 447 ms ldn-b5-link.telia.net [62.115.35.89]
9 355 ms 302 ms 247 ms ldn-bb3-link.telia.net [80.91.248.217]
10 407 ms 399 ms 402 ms nyk-bb1-link.telia.net [80.91.248.203]
11 378 ms 368 ms 404 ms chi-b22-link.telia.net [62.115.141.166]
12 380 ms 357 ms 400 ms telia-1.e8.router1.chicago.nfoservers.com [74.91.113.254]
13 468 ms 498 ms 450 ms d-216-52-148-29.ded-machine.premium-chicago.nfoservers.com [216.52.148.29]

Trace complete.

Now 1830 pretty much as predicted and characteristic of the last few months.

Tracing route to bbc-vip111.telhc.bbc.co.uk [212.58.244.66]
over a maximum of 30 hops:

1 3 ms 2 ms 1 ms homerouter.cpe [192.168.1.1]
2 * * * Request timed out.
3 42 ms 41 ms 39 ms 172.17.48.13
4 42 ms 29 ms 36 ms 172.17.48.21
5 290 ms 295 ms 274 ms 8ta-150-179-02.telkomadsl.co.za [41.150.179.2]
6 602 ms 552 ms 603 ms ndn-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.90.33]
7 743 ms 735 ms 725 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.43.9.46]
8 756 ms 782 ms 739 ms ldn-b5-link.telia.net [62.115.35.89]
9 589 ms 557 ms 548 ms atos-ic-315186-ldn-b5.c.telia.net [62.115.144.161]
10 * * * Request timed out.
11 802 ms 803 ms 821 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
12 700 ms 675 ms 682 ms 132.185.255.148
13 695 ms 654 ms 684 ms bbc-vip111.telhc.bbc.co.uk [212.58.244.66]

Trace complete.

worse still to come

 

[cavedog]

Yup, thar she blows, going south fast.

Earlier tracert (hop 5) around 1735.



Now 1830 as pretty much predicted.

And by the looks of it the tower latency is still the same no increase at all so it is network side not tower congestion. Surely Telkom should see this congestion or what are their network engineers doing the whole day?

You just need to look at a graph to see that the capacity was maxed and it's not like it's the first time it's been a while.

 

[Dan C]

Seems you going a similar route to Cara. Lucky buggers

Well I'm not on the uncapped deal, using the integrated SIM LTE. Maybe that's the difference ?