Degrading Telkom LTE Uncapped speeds

[Sneeky]

Worse and worse as time goes by, every evening.
Have LTE for almost a year and it was fine. Last few months, very poor effort and not what I signed up for.

 

[Sneeky]

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

They probably do, but just don't give a/

 

[Yuu]

I lost interest searching but this fault was opened 1st day of July saying a faulty SMA card needs replacing and is still open on the noticeboard. I am starting to think this is the cause/issue. By a quick search, an SMA card is part of a CISCO Switch, this is what is taking long as they didn't have it in stock .

Check here

I found this bit interesting

Customer are able to connect.
The workaround has been implemented and will revert back as soon as the faulty hardware has been replaced.

Whatever that workaround is, is possibly what is causing it to slowdown every night like clockwork. I initially thought a new ticket would open regarding the issue, only noticed now you guys mentioning London .

What you guys think?

 

[Sneeky]

I lost interest searching but this fault was opened 1st day of July saying a faulty SMA card needs replacing and is still open on the noticeboard. I am starting to think this is the cause/issue. By a quick search, an SMA card is part of a CISCO Switch, this is what is taking long as they didn't have it in stock .

Check here

I found this bit interesting



Whatever that workaround is, is possibly what is causing it to slowdown every night like clockwork. I initially thought a new ticket would open regarding the issue, only noticed now you guys mentioning London .

What you guys think?

Yuu
Firstly, thank you for a constructive post.

I have no idea how this impacts on my issue at hand (or others in the region) though.
All I can say is my problems started before July, still persist, and any feedback from Telkom would be appreciated.
Right now the silent treatment is not working.
I wish they would just engage their customer base, or attempt to at least.

The std call center approach is along the lines of reboot your router, eish.

 

[Sneeky]

Worse and worse

The joys of Telkom LTE

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 9 ms 9 ms homerouter.cpe [192.168.1.1]
2 * * * Request timed out.
3 31 ms 36 ms 40 ms 172.17.48.9
4 41 ms 38 ms 39 ms 172.17.48.17
5 188 ms 182 ms 212 ms 8ta-150-179-02.telkomadsl.co.za [41.150.179.2]
6 575 ms 573 ms 604 ms 196.25.188.77
7 739 ms 750 ms 743 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.58]
8 1012 ms 951 ms 885 ms ldn-b5-link.telia.net [62.115.35.89]
9 677 ms 713 ms 758 ms ldn-bb3-link.telia.net [80.91.248.217]
10 733 ms 854 ms 852 ms nyk-bb1-link.telia.net [80.91.248.203]
11 868 ms 867 ms 817 ms chi-b22-link.telia.net [62.115.141.166]
12 859 ms 889 ms 881 ms telia-1.e8.router1.chicago.nfoservers.com [74.91.113.254]
13 1166 ms 1078 ms 1069 ms d-216-52-148-29.ded-machine.premium-chicago.nfoservers.com [216.52.148.29]

 

[Sneeky]

News24.co.za

tracert www.news24.co.za

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

1 10 ms 9 ms 9 ms homerouter.cpe [192.168.1.1]
2 * * * Request timed out.
3 39 ms 36 ms 40 ms 172.17.48.9
4 34 ms 39 ms 39 ms 172.17.48.17
5 70 ms 58 ms 57 ms 8ta-150-179-02.telkomadsl.co.za [41.150.179.2]
6 504 ms 552 ms 537 ms ndn-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.90.33]
7 444 ms 423 ms 435 ms 196.43.25.206
8 504 ms 493 ms 469 ms gi1-1-1.cpt-pr-1.optinet.net [197.84.4.22]
9 818 ms 882 ms 887 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
10 637 ms 556 ms 567 ms vl12.cpt-hscore-2.optinet.net [197.84.5.254]
11 574 ms 578 ms 575 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 560 ms 598 ms 584 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
13 650 ms 631 ms 607 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 906 ms 872 ms 899 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
15 931 ms 929 ms 952 ms 41-86-110-143.mweb.co.za [41.86.110.143]

 

[Hummercellc]

News24.co.za

Latency also high on Telkom 3G.
Switched my router to roam on MTN and latency back to normal.

 

[Sneeky]

Tracert mybroadband

Hop 5 fallen over proper now.

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

1 6 ms 1 ms 7 ms homerouter.cpe [192.168.1.1]
2 * * * Request timed out.
3 48 ms 34 ms 40 ms 172.17.48.13
4 41 ms 39 ms 39 ms 172.17.48.21
5 819 ms 824 ms 746 ms 8ta-150-179-02.telkomadsl.co.za [41.150.179.2]
6 918 ms 1005 ms 1058 ms ndn-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.90.33]
7 1129 ms 1119 ms 1154 ms rrba-ip-se-2-gig-2-0-0-102.telkom-ipnet.co.za [196.43.25.138]
8 1248 ms 1353 ms 1268 ms cloudflare.jb1.napafrica.net [196.46.25.198]
9 1100 ms 1146 ms 1240 ms 104.20.71.110

Trace complete.

 

[Sneeky]

 

[PhireSide]

The struggle is real. Worst latency I have ever seen with this 'service'

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

C:\Users\Phil>ping 8.8.8.8 -t

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=760ms TTL=55
Reply from 8.8.8.8: bytes=32 time=819ms TTL=55
Reply from 8.8.8.8: bytes=32 time=884ms TTL=55
Reply from 8.8.8.8: bytes=32 time=880ms TTL=55
Reply from 8.8.8.8: bytes=32 time=900ms TTL=55
Reply from 8.8.8.8: bytes=32 time=867ms TTL=55
Reply from 8.8.8.8: bytes=32 time=813ms TTL=55
Reply from 8.8.8.8: bytes=32 time=703ms TTL=55
Reply from 8.8.8.8: bytes=32 time=742ms TTL=55
Reply from 8.8.8.8: bytes=32 time=794ms TTL=55
Reply from 8.8.8.8: bytes=32 time=773ms TTL=55
Reply from 8.8.8.8: bytes=32 time=809ms TTL=55
Reply from 8.8.8.8: bytes=32 time=847ms TTL=55
Reply from 8.8.8.8: bytes=32 time=818ms TTL=55
Reply from 8.8.8.8: bytes=32 time=774ms TTL=55
Reply from 8.8.8.8: bytes=32 time=784ms TTL=55
Reply from 8.8.8.8: bytes=32 time=878ms TTL=55
Reply from 8.8.8.8: bytes=32 time=893ms TTL=55
Reply from 8.8.8.8: bytes=32 time=942ms TTL=55
Reply from 8.8.8.8: bytes=32 time=900ms TTL=55
Reply from 8.8.8.8: bytes=32 time=811ms TTL=55
Reply from 8.8.8.8: bytes=32 time=774ms TTL=55
Reply from 8.8.8.8: bytes=32 time=797ms TTL=55
Reply from 8.8.8.8: bytes=32 time=756ms TTL=55
Reply from 8.8.8.8: bytes=32 time=733ms TTL=55
Reply from 8.8.8.8: bytes=32 time=790ms TTL=55
Reply from 8.8.8.8: bytes=32 time=833ms TTL=55
Reply from 8.8.8.8: bytes=32 time=884ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1017ms TTL=55
Reply from 8.8.8.8: bytes=32 time=941ms TTL=55
Reply from 8.8.8.8: bytes=32 time=972ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1039ms TTL=55
Reply from 8.8.8.8: bytes=32 time=958ms TTL=55
Reply from 8.8.8.8: bytes=32 time=835ms TTL=55
Reply from 8.8.8.8: bytes=32 time=735ms TTL=55
Reply from 8.8.8.8: bytes=32 time=704ms TTL=55
Reply from 8.8.8.8: bytes=32 time=692ms TTL=55
Reply from 8.8.8.8: bytes=32 time=711ms TTL=55
Reply from 8.8.8.8: bytes=32 time=729ms TTL=55
Reply from 8.8.8.8: bytes=32 time=790ms TTL=55
Reply from 8.8.8.8: bytes=32 time=795ms TTL=55
Reply from 8.8.8.8: bytes=32 time=740ms TTL=55
Reply from 8.8.8.8: bytes=32 time=790ms TTL=55

Ping statistics for 8.8.8.8:
Packets: Sent = 43, Received = 43, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 692ms, Maximum = 1039ms, Average = 823ms
Control-C
^C
C:\Users\Phil>

 

[Sneeky]

The struggle is real. Worst latency I have ever seen with this 'service'

Better off than me

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=1173ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1230ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1235ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1113ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1006ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1061ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1173ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1168ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1175ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1185ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1199ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1126ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1011ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1060ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1137ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1186ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1090ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1203ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1181ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1267ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1256ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1285ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1257ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1316ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1201ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1007ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1076ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1048ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1183ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1064ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1108ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1139ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1166ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1122ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1199ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1154ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1001ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1045ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1070ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1103ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1121ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1076ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1047ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1054ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1084ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1140ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1129ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1035ms TTL=55
Reply from 8.8.8.8: bytes=32 time=980ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1066ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1109ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1138ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1150ms TTL=55
Reply from 8.8.8.8: bytes=32 time=954ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1021ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1016ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1004ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1136ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1070ms TTL=55

 

[Sneeky]

MyBB

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

1 4 ms 9 ms 9 ms homerouter.cpe [192.168.1.1]
2 * * * Request timed out.
3 48 ms 38 ms 39 ms 172.17.48.13
4 32 ms 40 ms 39 ms 172.17.48.21
5 748 ms 777 ms 812 ms 8ta-150-179-02.telkomadsl.co.za [41.150.179.2]
6 1251 ms 1237 ms 1149 ms ndn-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.90.33]
7 1143 ms 1130 ms 1154 ms rrba-ip-se-2-gig-2-0-0-102.telkom-ipnet.co.za [196.43.25.138]
8 1252 ms 915 ms 896 ms cloudflare.jb1.napafrica.net [196.46.25.198]
9 1122 ms 1076 ms 1069 ms 104.20.71.110

Trace complete.

 

[Dennis]

Hi @MKdza your resuts first in black and mine second in red notice a difference around hop 5

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\Dennis>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.1.254
2 * * * Request timed out.
3 57 ms 163 ms 50 ms 172.17.48.13
4 49 ms 39 ms 29 ms 172.17.48.21
5 638 ms 638 ms 647 ms 41.150.179.2
6 601 ms 555 ms 475 ms 196.25.188.77
7 873 ms 865 ms 902 ms 196.43.52.38
8 538 ms 526 ms 503 ms 72.14.212.1
9 470 ms 420 ms 406 ms 72.14.239.53
10 745 ms 797 ms 896 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\Dennis>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.1.254
2 * * * Request timed out.
3 48 ms 39 ms 32 ms 172.17.48.9
4 39 ms 52 ms 43 ms 172.17.48.17
5 50 ms 38 ms 57 ms 41.150.179.1
6 508 ms 483 ms 515 ms 196.25.188.73
7 678 ms 635 ms 632 ms 196.43.9.46
8 587 ms 543 ms 557 ms 62.115.35.89
9 461 ms 470 ms 413 ms 80.91.249.181
10 281 ms 718 ms 280 ms 213.155.133.7
11 906 ms 871 ms 869 ms 62.115.141.168
12 307 ms 303 ms 308 ms 64.74.97.253
13 504 ms 538 ms 570 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\Dennis>tracert -d mybroadband.co.za

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

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 50 ms 29 ms 37 ms 172.17.48.9
4 33 ms 39 ms 31 ms 172.17.48.17
5 40 ms 39 ms 39 ms 41.150.179.1
6 400 ms 371 ms 370 ms 196.25.188.73
7 99 ms 88 ms 80 ms 196.43.25.138
8 700 ms 687 ms 671 ms 196.46.25.198
9 489 ms 496 ms 484 ms 104.20.72.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\Dennis>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.1.254
2 * * * Request timed out.
3 34 ms 38 ms 39 ms 172.17.48.13
4 45 ms 41 ms 29 ms 172.17.48.21
5 461 ms 449 ms 465 ms 41.150.179.1
6 902 ms 865 ms 858 ms 196.25.7.165
7 1288 ms 1361 ms 1277 ms 196.43.25.206
8 917 ms 914 ms 837 ms 196.25.3.102
9 * * * Request timed out.
10 408 ms 390 ms 389 ms 41.168.20.227
11 403 ms 400 ms 387 ms 41.168.20.229

Trace complete.



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\Dennis>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.1.254
2 * * * Request timed out.
3 38 ms 36 ms 40 ms 172.17.48.9
4 59 ms 60 ms 42 ms 172.17.48.17
5 48 ms 34 ms 39 ms 41.150.179.1
6 471 ms 482 ms 492 ms 196.25.188.73
7 806 ms 828 ms 802 ms 196.43.25.206
8 483 ms 494 ms 467 ms 197.84.98.50
9 469 ms 457 ms 437 ms 197.84.7.34
10 872 ms 821 ms 771 ms 197.84.5.254
11 604 ms 627 ms 606 ms 196.28.178.70
12 67 ms 57 ms 58 ms 196.41.133.166
13 118 ms 114 ms 97 ms 197.84.196.6
14 450 ms 451 ms 447 ms 197.84.208.146
15 404 ms 417 ms 392 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\Dennis>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.1.254
2 * * * Request timed out.
3 46 ms 40 ms 39 ms 172.17.48.13
4 36 ms 38 ms 39 ms 172.17.48.21
5 289 ms 255 ms 286 ms 41.150.179.1
6 574 ms 541 ms 606 ms 196.25.188.73
7 927 ms 979 ms 1076 ms 196.43.25.206
8 758 ms 823 ms 747 ms 197.84.98.50
9 920 ms 972 ms 932 ms 197.84.7.33
10 1178 ms 1193 ms 1117 ms 197.84.5.254
11 920 ms 835 ms 875 ms 196.28.178.70
12 695 ms 750 ms 711 ms 196.41.144.34
13 1192 ms 1111 ms 1168 ms 196.41.133.234
14 450 ms 431 ms 433 ms 152.111.192.244

Trace complete.

 

[Sneeky]

Just did the last one Dennis. Pretty sure the rest will be the same if you look and my Ping 8.8.8.8

Tracing route to 152.111.192.244 over a maximum of 30 hops

1 3 ms 2 ms 6 ms homerouter.cpe [192.168.1.1]
2 * * * Request timed out.
3 31 ms 39 ms 41 ms 172.17.48.13
4 34 ms 40 ms 39 ms 172.17.48.21
5 599 ms 601 ms 634 ms 8ta-150-179-02.telkomadsl.co.za [41.150.179.2]
6 940 ms 867 ms 954 ms 196.25.188.77
7 861 ms 824 ms 882 ms 196.43.25.206
8 1355 ms 1217 ms 1233 ms gi1-1-1.cpt-pr-2.optinet.net [197.84.98.50]
9 940 ms 961 ms 835 ms te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
10 855 ms 853 ms 816 ms vl12.cpt-hscore-2.optinet.net [197.84.5.254]
11 839 ms 780 ms 819 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 1278 ms 1346 ms 1417 ms 196.41.144.34
13 867 ms 897 ms 813 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
14 862 ms 861 ms 893 ms 152.111.192.244

Trace complete.

Enough for one night, praying for fire at Telkom.

 

[virgel]

Another slow night in Southdowns Irene centurion:
trace-route to 8.8.8.8 (8.8.8.8) , 5 relative hops max, 52 byte packets
1 192.168.8.1 (192.168.8.1) 25.320 ms 250.442 ms 258.749 ms
2 * * *
3 172.17.1.13 (172.17.1.13) 224.960 ms 618.879 ms 622.941 ms
4 * * *
5 172.17.1.17 (172.17.1.17) 279.873 ms 415.509 ms 421.626 ms
6 172.16.1.205 (172.16.1.205) 166.251 ms 1272.061 ms 1273.406 ms
7 8ta-150-190-01.telkomadsl.co.za (41.150.190.1) 222.347 ms 1787.489 ms 1795.054 ms
8 196.25.181.169 (196.25.181.169) 100.265 ms 1211.545 ms 1214.878 ms
9 196.43.52.42 (196.43.52.42) 157.314 ms 1205.526 ms *
10 72.14.212.1 (72.14.212.1) 212.646 ms 614.511 ms 618.010 ms
11 72.14.239.33 (72.14.239.33) 155.875 ms 1370.117 ms *
12 google-public-dns-a.google.com (8.8.8.8) 124.248 ms 4766.331 ms *
13 google-public-dns-a.google.com (8.8.8.8) 124.662 ms 127.029 ms 136.486 ms

My upload speeds are x6 faster than download speeds. I wish I could just receive 10mbps after 6pm just to watch Netflix

Recently my download speeds are 12mbps during the day compared to previous speeds which was 40mbps. Am luck to get a 1mbps after 7pm. Wish I could cancel my contract.......

 

[Dennis]

So this is pinging mybroadband from network cable to Telkom Lte router

Pinging www.mybroadband.co.za [104.20.72.110] with 32 bytes of data:
Reply from 104.20.72.110: bytes=32 time=370ms TTL=55
Reply from 104.20.72.110: bytes=32 time=388ms TTL=55
Reply from 104.20.72.110: bytes=32 time=396ms TTL=55
Reply from 104.20.72.110: bytes=32 time=388ms TTL=55
Reply from 104.20.72.110: bytes=32 time=413ms TTL=55
Reply from 104.20.72.110: bytes=32 time=443ms TTL=55
Reply from 104.20.72.110: bytes=32 time=397ms TTL=55
Reply from 104.20.72.110: bytes=32 time=362ms TTL=55
Reply from 104.20.72.110: bytes=32 time=387ms TTL=55
Reply from 104.20.72.110: bytes=32 time=441ms TTL=55
Reply from 104.20.72.110: bytes=32 time=477ms TTL=55
Reply from 104.20.72.110: bytes=32 time=455ms TTL=55
Reply from 104.20.72.110: bytes=32 time=419ms TTL=55
Reply from 104.20.72.110: bytes=32 time=446ms TTL=55
Reply from 104.20.72.110: bytes=32 time=441ms TTL=55
Reply from 104.20.72.110: bytes=32 time=430ms TTL=55
Reply from 104.20.72.110: bytes=32 time=419ms TTL=55
Reply from 104.20.72.110: bytes=32 time=417ms TTL=55
Reply from 104.20.72.110: bytes=32 time=410ms TTL=55
Reply from 104.20.72.110: bytes=32 time=449ms TTL=55
Reply from 104.20.72.110: bytes=32 time=458ms TTL=55
Reply from 104.20.72.110: bytes=32 time=447ms TTL=55

And this is via wifi to android hotspot on afrihost.

Pinging www.mybroadband.co.za [104.20.72.110] with 32 bytes of data:
Reply from 104.20.72.110: bytes=32 time=64ms TTL=52
Reply from 104.20.72.110: bytes=32 time=61ms TTL=52
Reply from 104.20.72.110: bytes=32 time=64ms TTL=52
Reply from 104.20.72.110: bytes=32 time=49ms TTL=52
Reply from 104.20.72.110: bytes=32 time=73ms TTL=52
Reply from 104.20.72.110: bytes=32 time=58ms TTL=52
Reply from 104.20.72.110: bytes=32 time=61ms TTL=52
Reply from 104.20.72.110: bytes=32 time=67ms TTL=52
Reply from 104.20.72.110: bytes=32 time=49ms TTL=52
Reply from 104.20.72.110: bytes=32 time=74ms TTL=52
Reply from 104.20.72.110: bytes=32 time=58ms TTL=52
Reply from 104.20.72.110: bytes=32 time=63ms TTL=52
Reply from 104.20.72.110: bytes=32 time=67ms TTL=52
Reply from 104.20.72.110: bytes=32 time=71ms TTL=52

Please sort out your network Telkom !!!!!

 

[Sneeky]

Its just awful

 

[MDKza]

Wow ok, sucks for you guys hard man.

Move to PTA. :crylaugh:

Hope they sort it out soon.

 

[virgel]

Am in centurion and tower is a literally across the road from my place. Speeds are ok during the day but after 6pm speeds drop to +- 2mbps.

 

[Sneeky]

The difference between 1700 and 1900

1700

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=84ms TTL=55
Reply from 8.8.8.8: bytes=32 time=58ms TTL=55
Reply from 8.8.8.8: bytes=32 time=49ms TTL=55
Reply from 8.8.8.8: bytes=32 time=59ms TTL=55
Reply from 8.8.8.8: bytes=32 time=59ms TTL=55
Reply from 8.8.8.8: bytes=32 time=70ms TTL=55
Reply from 8.8.8.8: bytes=32 time=48ms TTL=55
Reply from 8.8.8.8: bytes=32 time=45ms TTL=55
Reply from 8.8.8.8: bytes=32 time=75ms TTL=55
Reply from 8.8.8.8: bytes=32 time=71ms TTL=55
Reply from 8.8.8.8: bytes=32 time=51ms TTL=55
Reply from 8.8.8.8: bytes=32 time=46ms TTL=55
Reply from 8.8.8.8: bytes=32 time=60ms TTL=55
Reply from 8.8.8.8: bytes=32 time=55ms TTL=55

1900

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=325ms TTL=55
Reply from 8.8.8.8: bytes=32 time=398ms TTL=55
Reply from 8.8.8.8: bytes=32 time=418ms TTL=55
Reply from 8.8.8.8: bytes=32 time=428ms TTL=55
Reply from 8.8.8.8: bytes=32 time=404ms TTL=55
Reply from 8.8.8.8: bytes=32 time=342ms TTL=55
Reply from 8.8.8.8: bytes=32 time=361ms TTL=55
Reply from 8.8.8.8: bytes=32 time=377ms TTL=55
Reply from 8.8.8.8: bytes=32 time=411ms TTL=55
Reply from 8.8.8.8: bytes=32 time=396ms TTL=55
Reply from 8.8.8.8: bytes=32 time=417ms TTL=55
Reply from 8.8.8.8: bytes=32 time=416ms TTL=55
Reply from 8.8.8.8: bytes=32 time=425ms TTL=55
Reply from 8.8.8.8: bytes=32 time=459ms TTL=55
Reply from 8.8.8.8: bytes=32 time=467ms TTL=55
Reply from 8.8.8.8: bytes=32 time=474ms TTL=55
Reply from 8.8.8.8: bytes=32 time=455ms TTL=55
Reply from 8.8.8.8: bytes=32 time=386ms TTL=55
Reply from 8.8.8.8: bytes=32 time=413ms TTL=55
Reply from 8.8.8.8: bytes=32 time=460ms TTL=55
Reply from 8.8.8.8: bytes=32 time=445ms TTL=55

Hop 5 seems 'much' better @1900 but still going south overall

Tracing route to 104.20.72.110 over a maximum of 30 hops

1 3 ms 9 ms 9 ms homerouter.cpe [192.168.1.1]
2 * * * Request timed out.
3 40 ms 34 ms 44 ms 172.17.48.13
4 40 ms 39 ms 39 ms 172.17.48.21
5 66 ms 58 ms 64 ms 8ta-150-179-02.telkomadsl.co.za [41.150.179.2]
6 43 ms 42 ms 43 ms ndn-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.90.29]
7 532 ms 551 ms 539 ms rrba-ip-se-2-gig-2-0-0-102.telkom-ipnet.co.za [196.43.25.138]
8 48 ms 41 ms 51 ms cloudflare.jb1.napafrica.net [196.46.25.198]
9 264 ms 293 ms 277 ms 104.20.72.110

2000 (8 bells)

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 10 ms 2 ms 5 ms homerouter.cpe [192.168.1.1]
2 * * * Request timed out.
3 36 ms 36 ms 39 ms 172.17.48.13
4 63 ms 39 ms 58 ms 172.17.48.21
5 45 ms 39 ms 44 ms 8ta-150-179-02.telkomadsl.co.za [41.150.179.2]
6 77 ms 62 ms 53 ms ndn-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.90.29]
7 592 ms 558 ms 573 ms lon-ip-dir-telecity-pos-1-1-0.telkom-ipnet.co.za [196.43.9.50]
8 492 ms 528 ms 575 ms ldn-b5-link.telia.net [62.115.35.89]
9 583 ms 520 ms 590 ms ldn-bb3-link.telia.net [80.91.246.144]
10 394 ms 347 ms 350 ms nyk-bb1-link.telia.net [62.115.135.98]
11 382 ms 354 ms 356 ms chi-b22-link.telia.net [62.115.141.166]
12 339 ms 319 ms 329 ms telia-2.e2.router2.chicago.nfoservers.com [64.74.97.253]
13 306 ms 307 ms 328 ms d-216-52-148-29.ded-machine.premium-chicago.nfoservers.com [216.52.148.29]

Trace complete.

Hop 5 much improved for now, thank you whoever did something!!!

The top server is the one I have used for pinging/tracert's (amongst others) which this evening shows a marked improvement in total contrast to the rest.
If that is the new norm, I will be most grateful to return to this normalised level, the rest of the servers I do not care for.

Compared to this nonsense before. (+1000ms)
http://mybroadband.co.za/vb/showthr...ped-speeds?p=17947365&viewfull=1#post17947365

DL still sucks but not an issue for me at least in peak hours.
Oddly latency on the speed tests is still quite poor.
Will check for another hour then need to get some sleep, early start tomorrow.

If anyone else from kzn wants to confirm that would really help. thx.

Gonna try and stay quietly optimistic here.