Klerksdorp ADSL problems

[Petrivz]

Line including telephone was down about a month ago. Telkom came to fix then it was fine. Two weeks ago again line including telephone down, they came to fix but only the telephone is now fixed. ADSL struggles to sync, if it syncs its very slow. Reported this again, Telkom came, said nothing is wrong with the line but that the Router was faulty.

Replaced Router on Friday, still exactly same problem. Number 018 468 xxxx
ADSL line speed 4Mbps ISP both MWEB / Afrihost capped
Time of day - all day - intermittently over last 2 weeks

 

[Petrivz]

Oh and the line is very noisy on the telephone. If it syncs it syncs at 400-800Kbps. SNR between 5.8 and 11. Attenuation 45-47db.

Afrihost advised Telkom exchange problems...

 

[Petrivz]

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

1 2 ms 9 ms 8 ms 10.0.0.2
2 15 ms 15 ms 15 ms 105-236-13-65-esr-lo.mtnbusiness.co.za [105.236.13.65]
3 67 ms 52 ms 18 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178.65]
4 20 ms 19 ms 19 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.120]
5 19 ms 18 ms 20 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 18 ms 17 ms 19 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 36 ms 20 ms 19 ms rb-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.94]
8 18 ms 18 ms 22 ms 41.181.139.109
9 20 ms 19 ms 18 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.17]
10 19 ms 20 ms 19 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [196.43.25.137]
11 21 ms 21 ms 20 ms 196.43.51.74
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


Tracing route to www.google.com [216.58.211.164] over a maximum of 30 hops:

1 13 ms 6 ms 5 ms 10.0.0.2
2 30 ms 17 ms 28 ms 105-236-13-65-esr-lo.mtnbusiness.co.za [105.236.13.65]
3 22 ms 43 ms 34 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178.65]
4 789 ms 576 ms 615 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 941 ms 619 ms 495 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 1331 ms 1231 ms 936 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 883 ms 1519 ms 567 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]
8 332 ms 1050 ms 1175 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.187]
9 1334 ms 268 ms 454 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.13]
10 2006 ms 1786 ms 2206 ms 209.85.255.78
11 228 ms 416 ms 203 ms 66.249.95.23
12 605 ms 247 ms 249 ms 209.85.250.216
13 224 ms 226 ms 225 ms 209.85.241.139
14 1004 ms 792 ms 593 ms dub08s01-in-f4.1e100.net [216.58.211.164]

Trace complete.

 

[upup]

I took my router once to a friend on the same exch, eg 018468xxxx number and proof the fault was on Telkom side. It's so easy to say the fault is on the other side.

Seems there is a noise problem on your line.
Phone them daily, insist that the supervisor phone you.

 

[Petrivz]

No change yet

 

[Petrivz]

Finally fixed!

Telkom decided to replace the line from the pole to the house after me nagging them everyday for 3 weeks.