Telkom Internet Capped/Uncapped User Feedback (Pt2)

Problems with TI's DNS servers this morning (105.225.0.1/105.225.0.2), local sites resolving but not overseas eg: bbc.co.uk.
 
MickZA said:
Problems with TI's DNS servers this morning (105.225.0.1/105.225.0.2), local sites resolving but not overseas eg: bbc.co.uk.
Click to expand...

Same here. No reddit since yesterday.

Switch to Google DNS to resolve the issue.
 
Piss poor latency to CS:GO servers in CPT. 100+ ms

1 <1 ms <1 ms 1 ms TP-LINK.Home [192.168.1.1]
2 * * * Request timed out.
3 11 ms 10 ms 10 ms 105.224.0.49
4 12 ms 9 ms 11 ms 105.228.0.6
5 10 ms 12 ms 10 ms 105.224.0.13
6 81 ms 82 ms 82 ms 105.187.249.138
7 92 ms 82 ms 80 ms 105.187.249.138
8 84 ms 83 ms 92 ms optinet.ixp.capetown [196.10.140.145]
9 85 ms 85 ms 84 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
10 87 ms 85 ms 85 ms te0-7-0-0.cpt-p-1.optinet.net [197.84.4.33]
11 89 ms 91 ms 93 ms te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
12 88 ms 89 ms 83 ms 197-84-4-100.cpt.mweb.co.za [197.84.4.100]
13 84 ms 83 ms 81 ms 197-80-7-79.jhb.mweb.co.za [197.80.7.79]
14 84 ms 83 ms 84 ms bu-ether3.mca-pe-1.optinet.net [197.80.4.37]
15 84 ms 83 ms 82 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
16 83 ms 88 ms 83 ms 197-80-200-53.jhb.mweb.co.za [197.80.200.53]


And if i ping the 6th hop:

Pinging 105.187.249.138 with 32 bytes of data:
Reply from 105.187.249.138: bytes=32 time=81ms TTL=248
Reply from 105.187.249.138: bytes=32 time=82ms TTL=248
Reply from 105.187.249.138: bytes=32 time=81ms TTL=248
Reply from 105.187.249.138: bytes=32 time=75ms TTL=248

Ping statistics for 105.187.249.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 75ms, Maximum = 82ms, Average = 79ms

What the actual F???

This has been happening for atleast 3 days now...
 
1.png

Speed test to Mweb Speed test server and tracert

Tracing route to cpt-ntp.mweb.co.za [197.84.150.123]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms TP-LINK.Home [192.168.1.1]
2 * * * Request timed out.
3 * 10 ms 10 ms 105.224.0.49
4 13 ms 9 ms 9 ms 105.224.0.130
5 10 ms 10 ms 9 ms 105.224.0.13
6 79 ms 79 ms 80 ms 105.187.249.138
7 82 ms 82 ms 82 ms 105.187.249.138
8 81 ms 82 ms 83 ms optinet.ixp.capetown [196.10.140.15]
9 84 ms 82 ms 86 ms 101.te0-0-2-1.cpt-pe-14.optinet.net [197.84.7.14]
10 77 ms 79 ms 81 ms cpt-ntp.mweb.co.za [197.84.150.123]

Again the same Hop and IP Address... When i change ISP's this dissappears lol
 
Tracing route to cpt-ntp.mweb.co.za [197.84.150.123]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms TP-LINK.Home [192.168.1.1]
2 * * * Request timed out.
3 * 19 ms 19 ms 105.224.0.49
4 21 ms 19 ms 19 ms 105.224.0.50
5 21 ms 19 ms 19 ms 105.224.0.13
6 44 ms 40 ms 40 ms 105.187.249.138
7 40 ms 40 ms 40 ms 105.187.249.138
8 42 ms 41 ms 41 ms optinet.ixp.capetown [196.10.140.145]
9 58 ms 42 ms 42 ms 201.te0-0-2-2.cpt-pe-13.optinet.net [197.84.7.45]
10 43 ms 41 ms 41 ms cpt-ntp.mweb.co.za [197.84.150.123]

Probably a issue in the CT site. Not much we can do...
 
pings also through the roof here, been a few weeks now that around 8-8:30pm streaming just stops and starts, been getting worse the past week and sometimes speeds gets cut down to 18kb/s with characteristics like its throttled but nothing in the profile (not FUP'ed, no where near). Not sure what is happening with Telkom. Durban.
 
bradza said:
pings also through the roof here, been a few weeks now that around 8-8:30pm streaming just stops and starts, been getting worse the past week and sometimes speeds gets cut down to 18kb/s with characteristics like its throttled but nothing in the profile (not FUP'ed, no where near). Not sure what is happening with Telkom. Durban.
Click to expand...
I personally haven't experienced any slow downs this week, also in Durban
 
So I changed to the Telkom 4mb uncapped from a 2mb line with Telkom and an account with Vox, aside from the draconian AUP Vox added I had no issues.

Since the change over I have had 5 lost carrier, sometimes within 30 minutes of each other.

My line spontaneously changing sync profiles from 4094 , 508 to 5100, 380 then after a call to the call centre back to 4094 , 508 for 3 hours, then without even disconnecting the profile managed to change to 4094 , 380??? another call to the centre and im back at 4094 , 508.

Speed test puts my speeds at 3000 , 420 now and its was like that when the profile was correct at the beginning. The top end speedtest always hovers around 3000 and only the upstream changed when the profiles changed.

Any idea why this change is turning into a train wreck? I have never heard of your sync profile just changing spontaneously and incase your wondering the changes have been confirmed by Telkom every time so its not just on my router.

Oh and my snr is better then ideal, so I am really stumped.

Any suggestions?
 
Last edited:
fonoi said:
So I changed to the Telkom 4mb uncapped from a 2mb line with Telkom and an account with Vox, aside from the draconian AUP Vox added I had no issues.

Since the change over I have had 5 lost carrier, sometimes within 30 minutes of each other.

My line spontaneously changing sync profiles from 4094 , 508 to 5100, 380 then after a call to the call centre back to 4094 , 508 for 3 hours, then without even disconnecting the profile managed to change to 4094 , 380??? another call to the centre and im back at 4094 , 508.

Speed test puts my speeds at 3000 , 420 now and its was like that when the profile was correct at the beginning. The top end speedtest always hovers around 3000 and only the upstream changed when the profiles changed.

Any idea why this change is turning into a train wreck? I have never heard of your sync profile just changing spontaneously and incase your wondering the changes have been confirmed by Telkom every time so its not just on my router.

Any suggestions?
Click to expand...

This is a Line issue by the sounds of it. Can you post your stats, best case you phone Telkom and ask them to send someone to fix the connections where possible on your copper line...

Also ASSIA will change your sync speeds to prevent your connection going down...
 
Last edited:
Mode: ADSL_2plus
Type: ATM
Status: Up

Downstream Upstream
Line Coding(Trellis): On On
SNR Margin (0.1dB): 291 274
Attenuation (0.1dB): 280 144
Output Power (0.1dBm): 0 123
Attainable Rate (Kbps): 18136 1180
Rate (Kbps): 4094 508
D (interleaver depth): 96 1
Delay (msec): 7.97 1.13

Tomorrow if the problem persists, I will run new cabling from the Telkom jack to the router, change the POTS filter and then if there is still an issue I guess I will have to log a fault and hope for the best.
 
Last edited:
Best bet once ruling out any line issues is to let the speeds change so that ASSIA can learn about your line. This is normal when a profile changes because the software on Telkom's side has to learn about your line, atleast this is my understanding.

It takes about a week to normalise.

If anyone wants to read more about how it really works , grab the PDF from here DSL-Expresse Profile Optimizer :)
 
Yuu said:
Best bet once ruling out any line issues is to let the speeds change so that ASSIA can learn about your line. This is normal when a profile changes because the software on Telkom's side has to learn about your line, atleast this is my understanding.

It takes about a week to normalise.

If anyone wants to read more about how it really works , grab the PDF from here DSL-Expresse Profile Optimizer :)
Click to expand...

Thanks, this is pretty new, I will give it a week and if I do not go insane during that period I will log a fault.

What is Telkoms relationship with ASSIA?

Since this all happens automatically,
the service provider is able to realize the entire
optimization value from day one without extensive
staff training.
Click to expand...

Yeah that is a terrible idea, 7 calls to Telkom and no one has mentioned this to me, also I wouldn't be calling if my internet was not dropping like a fly. I honestly do not see how making random changes is going to fix my problems.
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X