ADSL in Bergvliet, Capetown

C

chun

Active Member
Joined
Sep 7, 2006
Messages
33
Reaction score
11
Location
Capetown
Number 021 712 ####

Was having congestion issues with 2nd hop ping of around 200ms, but was moved to an ADSL2 DSLAM which fixed the issue (and also got me bumped to 10Meg).

This occurred during the 5-11pm weekday times and most of the weekend.
 
Hi Chun

I have been having similar problems and i live in Meadowridge which is next to Bergvliet. How did you get your problem sorted out? I would like a free bump up as well if the problem is the same! ;D
 
Hey guys,

Number 021 713 ####

I have been having the exact same issues lately and live in Tokai just behind the blue route mall, I am connected to the Bergvliet (VBVT) exchange and had horrendous pings of up to 781ms on the second hop over the weekend! during the week the line is perfect during the day but degrades to the 200-500ms range over the course of the evening.

Chun, Please let us know how you managed to get your line moved to another Dslam?

Thanks.
 
Berglviet

Hello,

021 712 ####
1Mbps
MWEB Uncapped

I have been experiencing problems of late and recently contacted MWEB to find out what was going on. On Sunday at 10pm I ran the following tracert to redbulltv.com to watch the UCI Downhill Championships and the results were as follows:

Tracing route to www.redbulltv.com [64.124.14.63]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 541 ms 560 ms 666 ms 41-132-74-1.dsl.mweb.co.za [41.132.74.1]
3 701 ms 685 ms 631 ms 197-84-96-186.cpt.mweb.co.za [197.84.96.186]
4 675 ms 656 ms 634 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 839 ms 841 ms 871 ms 197-84-5-241.cpt.mweb.co.za [197.84.5.241]
6 963 ms 950 ms 932 ms 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
7 802 ms 813 ms 847 ms 176.67.177.131
8 973 ms 980 ms 993 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
3]
9 913 ms 831 ms 848 ms 4.68.70.78
10 1082 ms 982 ms 861 ms ge-5-1-0.mpr1.lhr2.uk.above.net [64.125.27.149]

11 937 ms 929 ms 962 ms xe-5-2-0.cr1.dca2.us.above.net [64.125.26.21]
12 1143 ms 1174 ms 1151 ms xe-1-3-0.cr1.iah1.us.above.net [64.125.31.213]
13 1116 ms 1087 ms 1154 ms xe-2-0-0.cr1.lax112.us.above.net [64.125.25.45]

14 1092 ms 1193 ms 1236 ms xe-0-2-0.cr1.sjc2.us.above.net [64.125.26.26]
15 1112 ms 1078 ms 1078 ms xe-0-1-0.er1.sjc2.us.above.net [64.125.28.17]
16 * * * Request timed out.
17 * * * Request timed out.
18 1178 ms 1045 ms 935 ms forward.markmonitor.com [64.124.14.63]

Trace complete.

Today I ran the same tracert and the results were as follows:

Tracing route to www.redbulltv.com [64.124.14.63]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 541 ms 560 ms 666 ms 41-132-74-1.dsl.mweb.co.za [41.132.74.1]
3 701 ms 685 ms 631 ms 197-84-96-186.cpt.mweb.co.za [197.84.96.186]
4 675 ms 656 ms 634 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 839 ms 841 ms 871 ms 197-84-5-241.cpt.mweb.co.za [197.84.5.241]
6 963 ms 950 ms 932 ms 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
7 802 ms 813 ms 847 ms 176.67.177.131
8 973 ms 980 ms 993 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
3]
9 913 ms 831 ms 848 ms 4.68.70.78
10 1082 ms 982 ms 861 ms ge-5-1-0.mpr1.lhr2.uk.above.net [64.125.27.149]

11 937 ms 929 ms 962 ms xe-5-2-0.cr1.dca2.us.above.net [64.125.26.21]
12 1143 ms 1174 ms 1151 ms xe-1-3-0.cr1.iah1.us.above.net [64.125.31.213]
13 1116 ms 1087 ms 1154 ms xe-2-0-0.cr1.lax112.us.above.net [64.125.25.45]

14 1092 ms 1193 ms 1236 ms xe-0-2-0.cr1.sjc2.us.above.net [64.125.26.26]
15 1112 ms 1078 ms 1078 ms xe-0-1-0.er1.sjc2.us.above.net [64.125.28.17]
16 * * * Request timed out.
17 * * * Request timed out.
18 1178 ms 1045 ms 935 ms forward.markmonitor.com [64.124.14.63]

Trace complete.

When running a tracert to Telkom.co.za, I get the following results:

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 11 ms 11 ms 41-132-74-1.dsl.mweb.co.za [41.132.74.1]
3 12 ms 13 ms 12 ms 197-84-96-138.cpt.mweb.co.za [197.84.96.138]
4 12 ms 12 ms 13 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 17 ms 15 ms 18 ms 197-84-5-242.cpt.mweb.co.za [197.84.5.242]
6 12 ms 13 ms 12 ms tengig0-0-0.cpt-pr-2.mweb.co.za [197.84.4.165]
7 13 ms 13 ms 12 ms cpt.telkom-ipnet.co.za [197.84.4.21]
8 14 ms 13 ms 13 ms 196.43.25.205
9 39 ms 39 ms 40 ms 196.43.39.162
10 39 ms 40 ms 39 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
11 41 ms 40 ms 41 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
12 42 ms 41 ms 42 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

Hope this all helps!
 
The only time i get close to line speed is in the morning before 11am(3.6mb down 0.5mb up with 9ms to telkom's cape town speed test server). Every weekday night for the past 2 months my latency has been between 500ms to 1500ms. this last week I actually consider it not bad if I manage to get 0.5mb. Last night for example i had a ping of 1100ms with 0.2mb down and 0.45m up. I have tried various ISP's(telkom capped, telkoms uncapped, afrihost uncapped, open web gold uncapped) and they all give me the same problem. I have phoned telkom about it and they claim its congestion and there's nothing they can do about it, I even tried speaking to their supervisor and I got the same response.

Phone number: 021 715 xxxx

ADSL line speed: 4Mbps ADSL

ISP name: Telkom Uncapped

Time: 17:00 to 23:00 in the evening for speed, latency remains high until after midnight.

Sync speed of the line: 4096 kbps

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

1 1 ms <1 ms <1 ms
2 787 ms 773 ms 755 ms ti-224-152-01.telkomadsl.co.za [105.224.152.1]
3 799 ms 790 ms 799 ms ti-226-0-06.telkomadsl.co.za [105.226.0.6]
4 855 ms 798 ms 799 ms ti-226-0-13.telkomadsl.co.za [105.226.0.13]
5 779 ms 809 ms 760 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 685 ms 740 ms 816 ms 196.43.39.166
7 706 ms 675 ms 663 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 733 ms 688 ms 703 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
9 725 ms 681 ms 642 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

Straight from my router.(max rate is normally 8846 down)
Downstream Upstream
Current Rate(Kbps) 4096 512
Max Rate(Kbps) 6040 912
Noise Margin(dB) 13 13
Attenuation(dB) 46 27
Output Power(dBm) 19.5 9.5
 
How did I get moved ?

Well I performed this cycle 5 times first :

1. Log call stating latency is slow after hours.
2. Get call closed by Telkom stating "Your ADSL is up"
3. Me saying "yes, I know its up, it was never down, but my pings are rubbish"
4. Immediately log another call.

I think after as I say, around 5 times, I eventually got called by a technician who after a chat said he would come and check my line out.
After checking out my router stats and a traceroute he confirmed DSLAM congestion and made a call to the exchange (the one off Main Rd, near Ladies Mile) to see if there was an open port on an ADSL 2 DSLAM. When he confirmed there was, I asked if 10Meg would be possible (was on 4) and again, after checking my noise margin etc he said no problem.

Off he went and half an hour later he phoned to ask to reboot my router and it was all done.

I think the key here is persistence. Don't get pissed off and continue to log calls and perhaps you will end up speaking to someone who knows what they are doing.

There are about 3 Telkom techies in the area and I have met them all. They are a helpful bunch in my experience. Its amazing what some kind words and a cup of gourmet coffee will get you :)
 
I'm on the same exchange and experience the speed I pay for (1mbps). However over the past couple of months my ADSL modem freezes a couple of times a day and has to be reset or switched off and then on. Sometimes the 'Internet' light doesn't come on at all.
 
-- couple of months of getting 800ms every afternoon and night.
-- 021 715
-- 1Mbps
-- MWEB uncapped
-- 17:00 to 00:00
 
I always have them telling me to put my router on and off. Which never works :/ If anyone manages to get changed over to another exchange do let us know. Think then i will be more persistent as right now i have very little hope this will ever be sorted out :/
 
Once again the internet is completely unusable on a Sunday:mad:


Phone number: 021 713 xxxx

ADSL line speed: 1Mbps ADSL

ISP name: Afrihost Uncapped

Sync speed of the line: 1024 kbps

Line Stats:

Attenuation: 53.0 Db Down, 26.0 Db up

Noise Margin: 20.4 Db Down, 13.0 Db up


Target Name: www.telkom.co.za
IP: 165.143.158.8
Date/Time: 2013/08/18 02:14:51 PM

1 0 ms [192.168.0.1]
2 924 ms 105-236-10-129-esr-lo.mtnbusiness.co.za [105.236.10.129]
3 920 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 917 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 916 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 915 ms tb-pr-1.za--tb-cr-2.za-a.mtnns.net [196.44.18.143]
7 916 ms wblv-ip-se-2-gw.telkom-ipnet.co.za [196.25.165.197]
8 913 ms [196.43.25.205]
9 937 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.146]
10 * [-]
11 * [-]
12 * [-]

Destination not reached in 35 hops
 
I'm to am so frustrated with this ridiculous ping. I have a uncapped 1mg line Afrihost manges both my line and is my ISP but for some reason can't or wont help me. Could anyone please help me on how to fix the issue or even just point where or what I need to do to resolve the issue.

C:\>ping -n 10 www.afrihost.co.za

Pinging www.afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=542ms TTL=59
Reply from 197.242.144.102: bytes=32 time=526ms TTL=59
Reply from 197.242.144.102: bytes=32 time=618ms TTL=59
Reply from 197.242.144.102: bytes=32 time=570ms TTL=59
Reply from 197.242.144.102: bytes=32 time=532ms TTL=59
Reply from 197.242.144.102: bytes=32 time=510ms TTL=59
Reply from 197.242.144.102: bytes=32 time=569ms TTL=59
Reply from 197.242.144.102: bytes=32 time=590ms TTL=59
Reply from 197.242.144.102: bytes=32 time=529ms TTL=59
Reply from 197.242.144.102: bytes=32 time=523ms TTL=59

Ping statistics for 197.242.144.102:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 510ms, Maximum = 618ms, Average = 550ms
 
Todays results:

C:\>ping -n 10 www.afrihost.co.za

Pinging www.afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=379ms TTL=59
Reply from 197.242.144.102: bytes=32 time=354ms TTL=59
Reply from 197.242.144.102: bytes=32 time=403ms TTL=59
Reply from 197.242.144.102: bytes=32 time=459ms TTL=59
Reply from 197.242.144.102: bytes=32 time=432ms TTL=59
Reply from 197.242.144.102: bytes=32 time=335ms TTL=59
Reply from 197.242.144.102: bytes=32 time=312ms TTL=59
Reply from 197.242.144.102: bytes=32 time=307ms TTL=59
Reply from 197.242.144.102: bytes=32 time=314ms TTL=59
Reply from 197.242.144.102: bytes=32 time=333ms TTL=59

Ping statistics for 197.242.144.102:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 307ms, Maximum = 459ms, Average = 362ms

C:\>tracert www.afrihost.co.za

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

1 1 ms <1 ms <1 ms login.router [10.0.0.2]
2 501 ms 482 ms 444 ms 105-236-9-65-esr-lo.mtnbusiness.co.za [105.236.9.65]
3 458 ms 467 ms 469 ms ipc [41.181.54.86]
4 527 ms 414 ms 648 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 507 ms 503 ms 487 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 437 ms 401 ms 374 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 360 ms 354 ms 344 ms rb-cr-1.za--ct-cr-2.za-b.mtnns.net [196.44.31.250]
8 265 ms 309 ms 313 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
9 392 ms 399 ms 425 ms 196.30.1.53
10 380 ms 613 ms 342 ms tengigabitethernet9-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.25]
11 325 ms 667 ms 363 ms tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.net [196.31.63.198]
12 406 ms 662 ms 459 ms www.afrihost.co.za [197.242.144.102]

Trace complete.
 
Today

Todays results:

C:\>ping -n 10 www.afrihost.co.za

Pinging www.afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=379ms TTL=59
Reply from 197.242.144.102: bytes=32 time=354ms TTL=59
Reply from 197.242.144.102: bytes=32 time=403ms TTL=59
Reply from 197.242.144.102: bytes=32 time=459ms TTL=59
Reply from 197.242.144.102: bytes=32 time=432ms TTL=59
Reply from 197.242.144.102: bytes=32 time=335ms TTL=59
Reply from 197.242.144.102: bytes=32 time=312ms TTL=59
Reply from 197.242.144.102: bytes=32 time=307ms TTL=59
Reply from 197.242.144.102: bytes=32 time=314ms TTL=59
Reply from 197.242.144.102: bytes=32 time=333ms TTL=59

Ping statistics for 197.242.144.102:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 307ms, Maximum = 459ms, Average = 362ms

C:\>tracert www.afrihost.co.za

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

1 1 ms <1 ms <1 ms login.router [10.0.0.2]
2 501 ms 482 ms 444 ms 105-236-9-65-esr-lo.mtnbusiness.co.za [105.236.9.65]
3 458 ms 467 ms 469 ms ipc [41.181.54.86]
4 527 ms 414 ms 648 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 507 ms 503 ms 487 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 437 ms 401 ms 374 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 360 ms 354 ms 344 ms rb-cr-1.za--ct-cr-2.za-b.mtnns.net [196.44.31.250]
8 265 ms 309 ms 313 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
9 392 ms 399 ms 425 ms 196.30.1.53
10 380 ms 613 ms 342 ms tengigabitethernet9-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.25]
11 325 ms 667 ms 363 ms tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.net [196.31.63.198]
12 406 ms 662 ms 459 ms www.afrihost.co.za [197.242.144.102]

Trace complete.
 
Shpongle said:
Once again the internet is completely unusable on a Sunday:mad:


Phone number: 021 713 xxxx

ADSL line speed: 1Mbps ADSL

ISP name: Afrihost Uncapped

Sync speed of the line: 1024 kbps

Line Stats:

Attenuation: 53.0 Db Down, 26.0 Db up

Noise Margin: 20.4 Db Down, 13.0 Db up


Target Name: www.telkom.co.za
IP: 165.143.158.8
Date/Time: 2013/08/18 02:14:51 PM

1 0 ms [192.168.0.1]
2 924 ms 105-236-10-129-esr-lo.mtnbusiness.co.za [105.236.10.129]
3 920 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 917 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 916 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 915 ms tb-pr-1.za--tb-cr-2.za-a.mtnns.net [196.44.18.143]
7 916 ms wblv-ip-se-2-gw.telkom-ipnet.co.za [196.25.165.197]
8 913 ms [196.43.25.205]
9 937 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.146]
10 * [-]
11 * [-]
12 * [-]

Destination not reached in 35 hops
Click to expand...

o.0
That's some serious latency on the exchange that you're seeing :( This could be due to a congested/ over-utilised exchange. If your line is with us please drop me a PM and we can have a fault/ work-order logged with Telkom for you
 
Leonvdm said:
I'm to am so frustrated with this ridiculous ping. I have a uncapped 1mg line Afrihost manges both my line and is my ISP but for some reason can't or wont help me. Could anyone please help me on how to fix the issue or even just point where or what I need to do to resolve the issue.

C:\>ping -n 10 www.afrihost.co.za

Pinging www.afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=542ms TTL=59
Reply from 197.242.144.102: bytes=32 time=526ms TTL=59
Reply from 197.242.144.102: bytes=32 time=618ms TTL=59
Reply from 197.242.144.102: bytes=32 time=570ms TTL=59
Reply from 197.242.144.102: bytes=32 time=532ms TTL=59
Reply from 197.242.144.102: bytes=32 time=510ms TTL=59
Reply from 197.242.144.102: bytes=32 time=569ms TTL=59
Reply from 197.242.144.102: bytes=32 time=590ms TTL=59
Reply from 197.242.144.102: bytes=32 time=529ms TTL=59
Reply from 197.242.144.102: bytes=32 time=523ms TTL=59

Ping statistics for 197.242.144.102:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 510ms, Maximum = 618ms, Average = 550ms
Click to expand...

As with most of the results on this thread, it looks like there is some serious exchange over-utilisation or congestion :( It sounds like we've dropped the ball here though, trying to help, if your line is with us we will do our best to have the congestion issues resolved - we do this by logging a fault/ work-order with Telkom on your behalf.
At the end of the day though, it's still up to Telkom to have the actual work attended to and the infrastructure sorted out.

Feel free to drop me a PM and I'll follow up on things for you.
 
I have a 1mg uncapped line with afrihost and no one is helping me I keep opening tickets, phoning, tweeting it doesnt matter everone promises to help and thats as far as it goes.

I can't use the internet when I have this sort of quality.

C:\Users\Leon>tracert www.afrihost.co.za

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

1 1 ms <1 ms <1 ms login.router [10.0.0.2]
2 854 ms 871 ms 820 ms 105-236-9-65-esr-lo.mtnbusiness.co.za [105.236.9.65]
3 854 ms 915 ms 867 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 817 ms 844 ms 874 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 867 ms 896 ms * compj-cpt-1.mtnns.net [196.44.18.2]
6 659 ms 720 ms 734 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 849 ms 874 ms 857 ms rb-cr-1.za--ct-cr-2.za-b.mtnns.net [196.44.31.250]
8 974 ms 781 ms 655 ms 196.44.31.97
9 654 ms 689 ms 735 ms 196.30.1.53
10 831 ms 835 ms 851 ms tengigabitethernet9-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.25]
11 998 ms 932 ms 851 ms tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.net [196.31.63.198]
12 631 ms 666 ms 755 ms www.afrihost.co.za [197.242.144.102]

Trace complete.

C:\Users\Leon>ping -n 10 www.afrihost.co.za

Pinging www.afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=884ms TTL=59
Reply from 197.242.144.102: bytes=32 time=632ms TTL=59
Reply from 197.242.144.102: bytes=32 time=575ms TTL=59
Reply from 197.242.144.102: bytes=32 time=599ms TTL=59
Reply from 197.242.144.102: bytes=32 time=658ms TTL=59
Reply from 197.242.144.102: bytes=32 time=725ms TTL=59
Reply from 197.242.144.102: bytes=32 time=775ms TTL=59
Reply from 197.242.144.102: bytes=32 time=780ms TTL=59
Reply from 197.242.144.102: bytes=32 time=784ms TTL=59
Reply from 197.242.144.102: bytes=32 time=852ms TTL=59

Ping statistics for 197.242.144.102:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 575ms, Maximum = 884ms, Average = 726ms
 
Leonvdm said:
I have a 1mg uncapped line with afrihost and no one is helping me I keep opening tickets, phoning, tweeting it doesnt matter everone promises to help and thats as far as it goes.

I can't use the internet when I have this sort of quality.

C:\Users\Leon>tracert www.afrihost.co.za

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

1 1 ms <1 ms <1 ms login.router [10.0.0.2]
2 854 ms 871 ms 820 ms 105-236-9-65-esr-lo.mtnbusiness.co.za [105.236.9.65]
3 854 ms 915 ms 867 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 817 ms 844 ms 874 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 867 ms 896 ms * compj-cpt-1.mtnns.net [196.44.18.2]
6 659 ms 720 ms 734 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 849 ms 874 ms 857 ms rb-cr-1.za--ct-cr-2.za-b.mtnns.net [196.44.31.250]
8 974 ms 781 ms 655 ms 196.44.31.97
9 654 ms 689 ms 735 ms 196.30.1.53
10 831 ms 835 ms 851 ms tengigabitethernet9-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.25]
11 998 ms 932 ms 851 ms tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.net [196.31.63.198]
12 631 ms 666 ms 755 ms www.afrihost.co.za [197.242.144.102]

Trace complete.

C:\Users\Leon>ping -n 10 www.afrihost.co.za

Pinging www.afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=884ms TTL=59
Reply from 197.242.144.102: bytes=32 time=632ms TTL=59
Reply from 197.242.144.102: bytes=32 time=575ms TTL=59
Reply from 197.242.144.102: bytes=32 time=599ms TTL=59
Reply from 197.242.144.102: bytes=32 time=658ms TTL=59
Reply from 197.242.144.102: bytes=32 time=725ms TTL=59
Reply from 197.242.144.102: bytes=32 time=775ms TTL=59
Reply from 197.242.144.102: bytes=32 time=780ms TTL=59
Reply from 197.242.144.102: bytes=32 time=784ms TTL=59
Reply from 197.242.144.102: bytes=32 time=852ms TTL=59

Ping statistics for 197.242.144.102:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 575ms, Maximum = 884ms, Average = 726ms
Click to expand...

I've just read through your PM. I'll personally be following up on your account for you to see if we can have things sorted out for you.
These traceroutes show some fairly heavy congestion on your exchange. We'll do our best to push Telkom to resolve the outstanding faults. Please also understand that we can only push so far, unfortunately at the end of the day - it's up to Telkom to maintain their hardware infrastructure.

In the mean time, I'll reply to your PM and get the ball rolling on our side.
 
The congestion at the Bergvliet exchange has become Ridiculous lately, has anyone else been having stats as shocking as these?

Phone number: 021 713 xxxx

ADSL line speed: 1Mbps ADSL

ISP name: Afrihost Uncapped

Sync speed of the line: 1024 kbps

Line Stats:

Attenuation: 53.0 Db Down, 26.0 Db up

Noise Margin: 20.4 Db Down, 13.0 Db up


Target Name: www.telkom.co.za
IP: 165.143.158.8
Date/Time: 2013/09/13 10:06:59 PM

1 1 ms 0 ms [192.168.0.1]
2 2279 ms 2208 ms 105-236-10-129-esr-lo.mtnbusiness.co.za [105.236.10.129]
3 2290 ms 2214 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 2271 ms 2206 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 2259 ms 2184 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 2491 ms 2187 ms tb-pr-1.za--tb-cr-2.za-a.mtnns.net [196.44.18.143]
7 2383 ms 2159 ms wblv-ip-se-2-gw.telkom-ipnet.co.za [196.25.165.197]
8 N/A 2169 ms [196.43.25.205]
9 2430 ms 2164 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.146]
10 * * [-]
11 * * [-]
12 * * [-]
13 * * [-]
14 * * [-]
15 * * [-]
16 * * [-]
17 * * [-]
18 * * [-]
19 * * [-]
20 * * [-]
21 * * [-]
22 * * [-]
23 * * [-]
24 * * [-]
25 * * [-]
26 * * [-]
27 * * [-]
28 * * [-]
29 * * [-]
30 * * [-]
31 * * [-]
32 * * [-]
33 * * [-]
34 * * [-]
35 * * [-]

Destination not reached in 35 hops
 
Last edited:
I feel you pain!

I too have experienced exactly the same problem in Bergvliet for weeks especially on Friday nights. I have spent hours trying to diagnose the problem and logged numerous calls with Afrihost, all of which have come to nothing. Upon Googling the issue I am kind of relieved that it is not only me experiencing the problem, but all the more annoyed that I seem to get brushed off when I ask for assistance. The last time I logged a service issue with Afrihost was around the same time you were having your issues on Friday night. Afrihost, clearly there is a problem! The response I received follows:

Your line sync is perfect -

AS a result ,for me to take this further please read through and perform the

following :

SLOW ACCESS TROUBLESHOOTING,FACTORS,CAUSES

Some of the contributing factors of slow access are ,congestion at the dslam,a line fault or something at the end users side eg the router.
Heavy downloading is also a major factor(view clients data usage).
To assist the client in pinpointing the possible cause/s of your slow access issue, please find out the following information from the client to assist in the basic troubleshooting

• Are you connecting, using a Capped or Uncapped data account?
• When did the problem start?
• Did the problem occur after bad weather?
• Are you connecting wirelessly to your router?
• Have you tried disabling your wifi connection and connecting directly to the computer using a Ethernet/LAN cable?
• Do you have a microfilter installed on your voice line?
• Have you changed/swapped the microfilter recently or removed the microfilter entirely and tested? ie. Have you plugged your router directly into the phone socket/wall jack and then tested your connection?
• Is there noise (crackling, echoing, feedback) on your voice line?
• Have you installed/updated your Antivirus and have all possible threats been removed from your computer?

Once THE CLIENT has completed / answered the tasks above please ask them to perform the following Speed Test for us.CLIENTS are required as per Telkom regulation to use two
Different ISP’ when performing the speed tests.


This response is so frustrating because it is a standard response i.e. the wording Once THE CLIENT, it assumes there is no problem on the line i.e. your line sync is perfect, and it assumes I have not done some basic diagnostics - and yet, here I sit with an unusable line...

My phone number is similar: 021 712 xxxx
ADSL line speed: 4096 (I have just changed it to a 10mbps hoping the change might make a difference)
ISP name: Afrihost Uncapped

Best of luck.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X