• You are not registered on MyBroadband, which means you miss out on great benefits. To join our community is very easy, and completely free. Register now.
  • New Two-Day Giveaway - Enter Here

Telkom Mobile Speed, Disconnections & Coverage Problems – click here first!

Gatekeeper

Well-Known Member
Joined
May 11, 2004
Messages
193
Lol sorry to say man in im Pretoria North, you a re screwed especially now that they launched the uncapped to all users ive had bad service now since initial launch its going on now for 3 years ICASA or any other company wont / cant do anything about it i have fought long and hard and have tome to terms with either 5Mb during the day to 1Mb at night they started with saying it is coverage and sent techs out to confirm it was not coverage but terrible and pathetic towers and equipment in the areas. they still continued. I bought 2 yagi antennas and same issue so no its not coverage dont fall for that lie if the pull that out of their a** signal levels are excellent it doesn't matter what band im on even on advance they gave me an option to cancel or wait for a tower which also never happened this was a year ago. I really feel sorry but at the same time laugh at the users who are taking this service now as im not in the only one and they wont do anything no matter what just waste their techs time, they are fully aware of what is going on, good luck though maybe you are more lucky than me. you have the option to cancel if they cannot provide service dont them tell you otherwise this has been stated by icasa in Pretoria North now there is a special @ ISPAfrica whom is willing to great service @ a reasonable cost. http://eepurl.com/dyFhzr otherwise try the other wireless providers.
 

[OUPA]MrNutz

Expert Member
Joined
Jan 21, 2005
Messages
1,740
Our MPY has obtained the 10mbps uncapped LTE 4days ago. It ran perfectly until 50GB of usage. Then all of the sudden everything just ....died.....I suspect a local tower failure. The LTE lights went from full , to 1 bar on 3g/wcdma. I tried to log a ticket/chat with the 8ta people online. "Sir , please take your router to nearest Telkom shop". NO - its a tower failure - please fix your issue! I have a billion 3g router , tplink 3g router and the huawei b618. All of them can't even register the simcard on the network. Wish Telkom would focccccusssss!!!
 

TeRRoRoFDeAtH

Active Member
Joined
Jun 12, 2009
Messages
70
Don't know what's happening, I'm in Ferndale Randburg area and I get a good connection for 10 or so minutes and then literally can't browse anything for another 10/20 minutes or until I reset my router. Very intermittent connection for the past week. Lights on the router don't change or go red, still 3/3 bars.

Anyone having the same problem?
 

Gatekeeper

Well-Known Member
Joined
May 11, 2004
Messages
193
Hey Guys the last week ive been having extreme issues with LTE stuck on 512Kb upload times out cant even use the connection gaming over 5000ms ping in Pretoria North anyone else having this issues, another thing is I cant even phone in ive tried to stay on hold after their system outage message now for a week. as if the LTE network is completely dead over 1 hour holding for an agent no calls anyone know whats is up.. ?
 

Inn3rs3lf

Expert Member
Joined
Mar 18, 2010
Messages
1,815
Can anyone tell me what is happening between the second and third hop?

Every night, this starts at roughly 6pm and will carry on till the morning. Then everything would be fine until the evening again. However, it's basically like this every day throughout the day. I used to get 9Mbps constant for the past 5 years or so, but for the last 3-4 months, it's been playing up as below:




15 August 2018 20:46pm

Traceroute has started…

traceroute to google.co.za (216.58.223.3), 64 hops max, 72 byte packets
1 www.huaweimobilewifi.com (192.168.8.1) 1.591 ms 1.265 ms 1.186 ms
2 * * *
3 172.17.16.1 (172.17.16.1) 27.220 ms 50.942 ms 83.783 ms
4 172.17.16.17 (172.17.16.17) 35.009 ms 25.124 ms 46.894 ms
5 telkom-internet-gw.telkom-ipnet.co.za (165.165.184.22) 33.091 ms 37.248 ms 19.771 ms
6 rrba-ip-bng-3-wan.telkom-ipnet.co.za (165.165.184.21) 52.129 ms 20.170 ms 41.869 ms
7 72.14.212.1 (72.14.212.1) 37.099 ms 54.173 ms 47.914 ms
8 72.14.237.239 (72.14.237.239) 33.022 ms 34.111 ms 39.939 ms
9 jnb01s07-in-f3.1e100.net (216.58.223.3) 27.918 ms 45.932 ms 31.936 ms

15 August 2018 20:47pm

Traceroute has started…

traceroute to google.co.za (216.58.223.3), 64 hops max, 72 byte packets
1 www.huaweimobilewifi.com (192.168.8.1) 1.941 ms 1.410 ms 1.136 ms
2 * * *
3 172.17.16.1 (172.17.16.1) 3666.979 ms 230.705 ms 109.120 ms
4 172.17.16.17 (172.17.16.17) 32.842 ms 38.980 ms 38.118 ms
5 telkom-internet-gw.telkom-ipnet.co.za (165.165.184.22) 29.980 ms 30.112 ms 58.954 ms
6 rrba-ip-bng-3-wan.telkom-ipnet.co.za (165.165.184.21) 40.921 ms 39.318 ms 18.846 ms
7 72.14.212.1 (72.14.212.1) 51.055 ms 42.127 ms 28.962 ms
8 72.14.237.239 (72.14.237.239) 50.041 ms 44.032 ms 30.935 ms
9 jnb01s07-in-f3.1e100.net (216.58.223.3) 47.032 ms 30.923 ms 20.068 ms


15 August 2018 20:49pm

Traceroute has started…

traceroute to telkom.co.za (165.143.151.45), 64 hops max, 72 byte packets
1 www.huaweimobilewifi.com (192.168.8.1) 2.915 ms 1.202 ms 1.199 ms
2 * * *
3 172.17.16.1 (172.17.16.1) 87.477 ms 43.133 ms 38.945 ms
4 172.17.16.17 (172.17.16.17) 47.008 ms 28.883 ms 29.916 ms
5 telkom-internet-gw.telkom-ipnet.co.za (165.165.184.22) 30.209 ms 48.189 ms 30.936 ms
6 rrba-ip-bng-3-wan.telkom-ipnet.co.za (165.165.184.21) 51.997 ms 27.027 ms 48.975 ms
7 196.43.8.45 (196.43.8.45) 35.048 ms 78.943 ms 32.046 ms
8 rndf-ip-p-1-bundle-pos-104.telkom-ipnet.co.za (41.147.241.49) 34.043 ms 28.178 ms 50.861 ms
9 nbsc-ip-bpe-1-pos-0-0-4-0.telkom-ipnet.co.za (41.147.241.198) 55.056 ms 27.269 ms 51.776 ms
10 nbsc-ip-er-1-gig-6-1-0.telkom-ipnet.co.za (196.43.51.74) 43.081 ms 33.208 ms 30.863 ms
11 telkom-sa-tienet-gw.telkom-ipnet.co.za (196.25.10.42) 21.003 ms 36.098 ms 30.936 ms
12 198.54.206.73 (198.54.206.73) 49.178 ms 25.015 ms 38.896 ms
13 165.143.151.45 (165.143.151.45) 31.047 ms 27.205 ms 42.950 ms

15 August 2018 20:50pm

Traceroute has started…

traceroute to google.com (216.58.223.14), 64 hops max, 72 byte packets
1 www.huaweimobilewifi.com (192.168.8.1) 2.487 ms 1.962 ms 1.928 ms
2 * * *
3 172.17.16.5 (172.17.16.5) 31.283 ms 25.012 ms 37.867 ms
4 172.17.16.21 (172.17.16.21) 40.021 ms 24.010 ms 38.938 ms
5 rrba-ip-bng-3-wan.telkom-ipnet.co.za (165.165.184.21) 21.904 ms 60.377 ms 38.772 ms
6 72.14.212.1 (72.14.212.1) 40.109 ms 46.036 ms 30.859 ms
7 72.14.237.239 (72.14.237.239) 48.176 ms 25.105 ms 48.993 ms
8 jnb01s07-in-f14.1e100.net (216.58.223.14) 29.050 ms 50.124 ms 27.091 ms
 

Hummercellc

Expert Member
Joined
Jan 6, 2008
Messages
3,162
Can anyone tell me what is happening between the second and third hop?

Every night, this starts at roughly 6pm and will carry on till the morning. Then everything would be fine until the evening again. However, it's basically like this every day throughout the day. I used to get 9Mbps constant for the past 5 years or so, but for the last 3-4 months, it's been playing up as below:




15 August 2018 20:46pm

Traceroute has started…

traceroute to google.co.za (216.58.223.3), 64 hops max, 72 byte packets
1 www.huaweimobilewifi.com (192.168.8.1) 1.591 ms 1.265 ms 1.186 ms
2 * * *
3 172.17.16.1 (172.17.16.1) 27.220 ms 50.942 ms 83.783 ms
4 172.17.16.17 (172.17.16.17) 35.009 ms 25.124 ms 46.894 ms
5 telkom-internet-gw.telkom-ipnet.co.za (165.165.184.22) 33.091 ms 37.248 ms 19.771 ms
6 rrba-ip-bng-3-wan.telkom-ipnet.co.za (165.165.184.21) 52.129 ms 20.170 ms 41.869 ms
7 72.14.212.1 (72.14.212.1) 37.099 ms 54.173 ms 47.914 ms
8 72.14.237.239 (72.14.237.239) 33.022 ms 34.111 ms 39.939 ms
9 jnb01s07-in-f3.1e100.net (216.58.223.3) 27.918 ms 45.932 ms 31.936 ms

15 August 2018 20:47pm

Traceroute has started…

traceroute to google.co.za (216.58.223.3), 64 hops max, 72 byte packets
1 www.huaweimobilewifi.com (192.168.8.1) 1.941 ms 1.410 ms 1.136 ms
2 * * *
3 172.17.16.1 (172.17.16.1) 3666.979 ms 230.705 ms 109.120 ms
4 172.17.16.17 (172.17.16.17) 32.842 ms 38.980 ms 38.118 ms
5 telkom-internet-gw.telkom-ipnet.co.za (165.165.184.22) 29.980 ms 30.112 ms 58.954 ms
6 rrba-ip-bng-3-wan.telkom-ipnet.co.za (165.165.184.21) 40.921 ms 39.318 ms 18.846 ms
7 72.14.212.1 (72.14.212.1) 51.055 ms 42.127 ms 28.962 ms
8 72.14.237.239 (72.14.237.239) 50.041 ms 44.032 ms 30.935 ms
9 jnb01s07-in-f3.1e100.net (216.58.223.3) 47.032 ms 30.923 ms 20.068 ms


15 August 2018 20:49pm

Traceroute has started…

traceroute to telkom.co.za (165.143.151.45), 64 hops max, 72 byte packets
1 www.huaweimobilewifi.com (192.168.8.1) 2.915 ms 1.202 ms 1.199 ms
2 * * *
3 172.17.16.1 (172.17.16.1) 87.477 ms 43.133 ms 38.945 ms
4 172.17.16.17 (172.17.16.17) 47.008 ms 28.883 ms 29.916 ms
5 telkom-internet-gw.telkom-ipnet.co.za (165.165.184.22) 30.209 ms 48.189 ms 30.936 ms
6 rrba-ip-bng-3-wan.telkom-ipnet.co.za (165.165.184.21) 51.997 ms 27.027 ms 48.975 ms
7 196.43.8.45 (196.43.8.45) 35.048 ms 78.943 ms 32.046 ms
8 rndf-ip-p-1-bundle-pos-104.telkom-ipnet.co.za (41.147.241.49) 34.043 ms 28.178 ms 50.861 ms
9 nbsc-ip-bpe-1-pos-0-0-4-0.telkom-ipnet.co.za (41.147.241.198) 55.056 ms 27.269 ms 51.776 ms
10 nbsc-ip-er-1-gig-6-1-0.telkom-ipnet.co.za (196.43.51.74) 43.081 ms 33.208 ms 30.863 ms
11 telkom-sa-tienet-gw.telkom-ipnet.co.za (196.25.10.42) 21.003 ms 36.098 ms 30.936 ms
12 198.54.206.73 (198.54.206.73) 49.178 ms 25.015 ms 38.896 ms
13 165.143.151.45 (165.143.151.45) 31.047 ms 27.205 ms 42.950 ms

15 August 2018 20:50pm

Traceroute has started…

traceroute to google.com (216.58.223.14), 64 hops max, 72 byte packets
1 www.huaweimobilewifi.com (192.168.8.1) 2.487 ms 1.962 ms 1.928 ms
2 * * *
3 172.17.16.5 (172.17.16.5) 31.283 ms 25.012 ms 37.867 ms
4 172.17.16.21 (172.17.16.21) 40.021 ms 24.010 ms 38.938 ms
5 rrba-ip-bng-3-wan.telkom-ipnet.co.za (165.165.184.21) 21.904 ms 60.377 ms 38.772 ms
6 72.14.212.1 (72.14.212.1) 40.109 ms 46.036 ms 30.859 ms
7 72.14.237.239 (72.14.237.239) 48.176 ms 25.105 ms 48.993 ms
8 jnb01s07-in-f14.1e100.net (216.58.223.14) 29.050 ms 50.124 ms 27.091 ms
I have the same problem when roaming on MTN, but when on the Telkom home network it is fine.

It would seem the home network and roaming take different paths, which is to be expected.

My guess would be Telkom have not bought enough capacity from MTN for roaming. And the links are congested during peak times.
 
Top