Unbearable latency and download speeds on mweb/afrihost. Please help!

A

Apyrael

Active Member
Joined
May 6, 2010
Messages
30
Reaction score
0
Hi everyone

I have a 4mb line with MWeb and for 2 years I have had good download speeds and good latency. Since January I have started having incredibly bad latency. If I ping mweb.co.za I usually get 9ms and over 1000 pings it never changes from there. It stays dead on 9ms. Lately this has started to be come extremely erratic. It is never steady on 9ms anymore and it jumps between 9ms and 100ms. At night time it usually sits between 200ms and 500ms. I checked the download speed at nights and it has been reduced to 1mb/s.

I have logged 4 faults with telkom, they keep telling me my line is fine. I had a telkom technician come check the line and he said it was fine. Today he brought an adsl "specialist" from telkom whom also said the line was fine. I have phone mweb and they said the line is fine. No one seems to know what the issue is. Telkom checked the noise ratio and it was fine, and the attenuation is also fine. What I don't understand is why the connection is now erratic. It used to be so steady and in recent months it is unbearable. I changed to an afrihost account that I have and the latency was just as bad. Here are some pings I did at the time of writing this post. Please note that I usually get 9ms ping to mweb.co.za and 32ms ping to telkom.co.za.



C:\Users>ping mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=309ms TTL=122
Reply from 196.2.63.110: bytes=32 time=277ms TTL=122
Reply from 196.2.63.110: bytes=32 time=259ms TTL=122
Reply from 196.2.63.110: bytes=32 time=357ms TTL=122

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 259ms, Maximum = 357ms, Average = 300ms



C:\Users>ping telkom.co.za

Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=310ms TTL=241
Request timed out.
Reply from 196.43.22.222: bytes=32 time=398ms TTL=241
Reply from 196.43.22.222: bytes=32 time=455ms TTL=241

Ping statistics for 196.43.22.222:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 310ms, Maximum = 455ms, Average = 387ms



C:\Users>ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.246.91] with 32 bytes of data:
Reply from 212.58.246.91: bytes=32 time=664ms TTL=48
Reply from 212.58.246.91: bytes=32 time=623ms TTL=48
Reply from 212.58.246.91: bytes=32 time=610ms TTL=48
Reply from 212.58.246.91: bytes=32 time=573ms TTL=48

Ping statistics for 212.58.246.91:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 573ms, Maximum = 664ms, Average = 617ms



Here are the tracerts:

C:\Users>tracert mweb.co.za

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 326 ms 321 ms 311 ms 41-132-40-1.dsl.mweb.co.za [41.132.40.1]
3 324 ms 328 ms 343 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 306 ms 290 ms 280 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 354 ms 361 ms 357 ms 196-28-178-38.adsl.mweb.co.za [196.28.178.38]
6 306 ms 321 ms 309 ms cte-core-sw2.vwol.net [196.41.144.35]
7 253 ms 267 ms 258 ms www.mweb.co.za [196.2.63.110]

Trace complete.



C:\Users>tracert telkom.co.za

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.2.1
2 209 ms 229 ms 256 ms 41-132-40-1.dsl.mweb.co.za [41.132.40.1]
3 366 ms 372 ms 383 ms te1-1-0.508.cpt-ipc-1.mweb.co.za [196.28.178.190]
4 364 ms 376 ms 364 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 355 ms 363 ms 296 ms tengige0-3-0-0.12.cpt-up-1.mweb.co.za [196.28.178.113]
6 212 ms 202 ms 201 ms 197-84-4-21.cpt.mweb.co.za [197.84.4.21]
7 227 ms 219 ms 222 ms 196.43.25.205
8 272 ms 271 ms 251 ms 196.43.39.166
9 336 ms 333 ms 286 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
10 181 ms 184 ms 191 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
11 226 ms 243 ms 279 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.



C:\Users>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 350 ms 313 ms 288 ms 41-132-40-1.dsl.mweb.co.za [41.132.40.1]
3 271 ms 288 ms 294 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 279 ms 279 ms 274 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 304 ms 286 ms 277 ms tengige0-3-0-0.12.cpt-up-1.mweb.co.za [196.28.178.113]
6 504 ms 479 ms 470 ms 197-80-4-136.jhb.mweb.co.za [197.80.4.136]
7 519 ms 503 ms 503 ms pos0-0-3-0.lon-up-1.mweb.co.za [196.22.164.2]
8 441 ms 395 ms 428 ms xe-10-1-3.edge4.London1.Level3.net [212.113.14.121]
9 511 ms 495 ms 483 ms ae-24-52.car3.London1.Level3.net [4.69.139.100]
10 388 ms 384 ms 365 ms 195.50.90.162
11 338 ms 317 ms 311 ms 212.58.238.137
12 402 ms 392 ms 406 ms virtual-vip-231.thdo.bbc.co.uk [212.58.241.131]

Trace complete.


Please, any assistant will be greatly appreciated. It is always the worse at night and some nights at certain times the latency comes down, but it is still erratic.

Regards
Apyrael
 
Apyrael said:
Hi everyone

I have a 4mb line with MWeb and for 2 years I have had good download speeds and good latency. Since January I have started having incredibly bad latency. If I ping mweb.co.za I usually get 9ms and over 1000 pings it never changes from there. It stays dead on 9ms. Lately this has started to be come extremely erratic. It is never steady on 9ms anymore and it jumps between 9ms and 100ms. At night time it usually sits between 200ms and 500ms. I checked the download speed at nights and it has been reduced to 1mb/s.

I have logged 4 faults with telkom, they keep telling me my line is fine. I had a telkom technician come check the line and he said it was fine. Today he brought an adsl "specialist" from telkom whom also said the line was fine. I have phone mweb and they said the line is fine. No one seems to know what the issue is. Telkom checked the noise ratio and it was fine, and the attenuation is also fine. What I don't understand is why the connection is now erratic. It used to be so steady and in recent months it is unbearable. I changed to an afrihost account that I have and the latency was just as bad. Here are some pings I did at the time of writing this post. Please note that I usually get 9ms ping to mweb.co.za and 32ms ping to telkom.co.za.



C:\Users>ping mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=309ms TTL=122
Reply from 196.2.63.110: bytes=32 time=277ms TTL=122
Reply from 196.2.63.110: bytes=32 time=259ms TTL=122
Reply from 196.2.63.110: bytes=32 time=357ms TTL=122

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 259ms, Maximum = 357ms, Average = 300ms



C:\Users>ping telkom.co.za

Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=310ms TTL=241
Request timed out.
Reply from 196.43.22.222: bytes=32 time=398ms TTL=241
Reply from 196.43.22.222: bytes=32 time=455ms TTL=241

Ping statistics for 196.43.22.222:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 310ms, Maximum = 455ms, Average = 387ms



C:\Users>ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.246.91] with 32 bytes of data:
Reply from 212.58.246.91: bytes=32 time=664ms TTL=48
Reply from 212.58.246.91: bytes=32 time=623ms TTL=48
Reply from 212.58.246.91: bytes=32 time=610ms TTL=48
Reply from 212.58.246.91: bytes=32 time=573ms TTL=48

Ping statistics for 212.58.246.91:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 573ms, Maximum = 664ms, Average = 617ms



Here are the tracerts:

C:\Users>tracert mweb.co.za

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 326 ms 321 ms 311 ms 41-132-40-1.dsl.mweb.co.za [41.132.40.1]
3 324 ms 328 ms 343 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 306 ms 290 ms 280 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 354 ms 361 ms 357 ms 196-28-178-38.adsl.mweb.co.za [196.28.178.38]
6 306 ms 321 ms 309 ms cte-core-sw2.vwol.net [196.41.144.35]
7 253 ms 267 ms 258 ms www.mweb.co.za [196.2.63.110]

Trace complete.



C:\Users>tracert telkom.co.za

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.2.1
2 209 ms 229 ms 256 ms 41-132-40-1.dsl.mweb.co.za [41.132.40.1]
3 366 ms 372 ms 383 ms te1-1-0.508.cpt-ipc-1.mweb.co.za [196.28.178.190]
4 364 ms 376 ms 364 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 355 ms 363 ms 296 ms tengige0-3-0-0.12.cpt-up-1.mweb.co.za [196.28.178.113]
6 212 ms 202 ms 201 ms 197-84-4-21.cpt.mweb.co.za [197.84.4.21]
7 227 ms 219 ms 222 ms 196.43.25.205
8 272 ms 271 ms 251 ms 196.43.39.166
9 336 ms 333 ms 286 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
10 181 ms 184 ms 191 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
11 226 ms 243 ms 279 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.



C:\Users>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 350 ms 313 ms 288 ms 41-132-40-1.dsl.mweb.co.za [41.132.40.1]
3 271 ms 288 ms 294 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 279 ms 279 ms 274 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 304 ms 286 ms 277 ms tengige0-3-0-0.12.cpt-up-1.mweb.co.za [196.28.178.113]
6 504 ms 479 ms 470 ms 197-80-4-136.jhb.mweb.co.za [197.80.4.136]
7 519 ms 503 ms 503 ms pos0-0-3-0.lon-up-1.mweb.co.za [196.22.164.2]
8 441 ms 395 ms 428 ms xe-10-1-3.edge4.London1.Level3.net [212.113.14.121]
9 511 ms 495 ms 483 ms ae-24-52.car3.London1.Level3.net [4.69.139.100]
10 388 ms 384 ms 365 ms 195.50.90.162
11 338 ms 317 ms 311 ms 212.58.238.137
12 402 ms 392 ms 406 ms virtual-vip-231.thdo.bbc.co.uk [212.58.241.131]

Trace complete.


Please, any assistant will be greatly appreciated. It is always the worse at night and some nights at certain times the latency comes down, but it is still erratic.

Regards
Apyrael
Click to expand...

Good evening Apyrael, looking at your tracers: the problem seems to be closer to the remote end. The latency is high from the 2nd hop, please provide me your mweb account details. Also please advise if this problem is there at specific times of the day or if exists throughout the day?
 
Your figures are certainly not what you should be getting:

Code: 
rogan@aphrodite:~$ ping mweb.co.za
PING mweb.co.za (196.2.63.110) 56(84) bytes of data.
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=1 ttl=118 time=31.1 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=2 ttl=118 time=32.1 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=3 ttl=118 time=30.9 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=4 ttl=118 time=31.1 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=5 ttl=118 time=30.0 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=6 ttl=118 time=30.0 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=7 ttl=118 time=30.5 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=8 ttl=118 time=31.9 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=9 ttl=118 time=30.2 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=10 ttl=118 time=29.6 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=11 ttl=118 time=30.4 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=12 ttl=118 time=29.8 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=13 ttl=118 time=30.0 ms
^C
--- mweb.co.za ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12014ms
rtt min/avg/max/mdev = 29.691/30.633/32.183/0.777 ms
rogan@aphrodite:~$ ping telkom.co.za
PING telkom.co.za (196.43.22.222) 56(84) bytes of data.
64 bytes from nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za (196.43.22.222): icmp_req=1 ttl=245 time=98.8 ms
64 bytes from nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za (196.43.22.222): icmp_req=2 ttl=245 time=55.6 ms
64 bytes from nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za (196.43.22.222): icmp_req=3 ttl=245 time=56.7 ms
64 bytes from nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za (196.43.22.222): icmp_req=4 ttl=245 time=57.6 ms
64 bytes from nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za (196.43.22.222): icmp_req=5 ttl=245 time=57.8 ms
64 bytes from nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za (196.43.22.222): icmp_req=6 ttl=245 time=56.0 ms
64 bytes from nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za (196.43.22.222): icmp_req=7 ttl=245 time=54.9 ms
64 bytes from nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za (196.43.22.222): icmp_req=8 ttl=245 time=55.8 ms
^C
--- telkom.co.za ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7003ms
rtt min/avg/max/mdev = 54.991/61.694/98.895/14.090 ms
rogan@aphrodite:~$ ping www.bbc.co.uk
PING www.bbc.net.uk (212.58.244.67) 56(84) bytes of data.
64 bytes from bbc-vip112.telhc.bbc.co.uk (212.58.244.67): icmp_req=1 ttl=47 time=202 ms
64 bytes from bbc-vip112.telhc.bbc.co.uk (212.58.244.67): icmp_req=2 ttl=47 time=179 ms
64 bytes from bbc-vip112.telhc.bbc.co.uk (212.58.244.67): icmp_req=3 ttl=47 time=179 ms
64 bytes from bbc-vip112.telhc.bbc.co.uk (212.58.244.67): icmp_req=4 ttl=47 time=179 ms
64 bytes from bbc-vip112.telhc.bbc.co.uk (212.58.244.67): icmp_req=5 ttl=47 time=179 ms
64 bytes from bbc-vip112.telhc.bbc.co.uk (212.58.244.67): icmp_req=6 ttl=47 time=179 ms
64 bytes from bbc-vip112.telhc.bbc.co.uk (212.58.244.67): icmp_req=7 ttl=47 time=178 ms
^C
--- www.bbc.net.uk ping statistics ---
8 packets transmitted, 7 received, 12% packet loss, time 7005ms
rtt min/avg/max/mdev = 178.759/182.757/202.976/8.279 ms
rogan@aphrodite:~$

From WebAfrica, FWIW.
 
@MWEB Guy I sent the details via private message.

The erratic ping is constant throughout the entire day. The bad download speed and extremely bad latency is mostly in the afternoon/evening. At 11:00pm it usually it usually simmers down a bit. It is now 10:03pm and i get this:

C:\Users\Apyrael>ping mweb.co.za -t

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=10ms TTL=122
Reply from 196.2.63.110: bytes=32 time=26ms TTL=122
Reply from 196.2.63.110: bytes=32 time=87ms TTL=122
Reply from 196.2.63.110: bytes=32 time=45ms TTL=122
Reply from 196.2.63.110: bytes=32 time=72ms TTL=122
Reply from 196.2.63.110: bytes=32 time=71ms TTL=122
Reply from 196.2.63.110: bytes=32 time=42ms TTL=122
Reply from 196.2.63.110: bytes=32 time=24ms TTL=122
Reply from 196.2.63.110: bytes=32 time=12ms TTL=122
Reply from 196.2.63.110: bytes=32 time=49ms TTL=122
Reply from 196.2.63.110: bytes=32 time=23ms TTL=122
Reply from 196.2.63.110: bytes=32 time=28ms TTL=122

Ping statistics for 196.2.63.110:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 87ms, Average = 40ms

Notice that it does go down to 9ms, but it never stays solid.
 
Last edited:
Awesome, it just gets worse. 10:20pm

C:\Users\Apyrael>ping mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=372ms TTL=122
Reply from 196.2.63.110: bytes=32 time=485ms TTL=122
Reply from 196.2.63.110: bytes=32 time=419ms TTL=122
Reply from 196.2.63.110: bytes=32 time=462ms TTL=122

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 372ms, Maximum = 485ms, Average = 434ms
 
Apyrael said:
Awesome, it just gets worse. 10:20pm

C:\Users\Apyrael>ping mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=372ms TTL=122
Reply from 196.2.63.110: bytes=32 time=485ms TTL=122
Reply from 196.2.63.110: bytes=32 time=419ms TTL=122
Reply from 196.2.63.110: bytes=32 time=462ms TTL=122

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 372ms, Maximum = 485ms, Average = 434ms
Click to expand...

Hi Apyrael,

As per our inbox communication, our technical specialist will be giving you a call.

MWEB Guy
 
Plz do help us 2!!!!!!!!!!!

Hi

We are based in the lonehill area!! For the past week we have been getting 4mb sync speeds but bad download speeds and latency (ping)!!! This is really unacceptable, ive been contacting telkom and mweb but both are clue less at what is wrong!!!! The only message they keep sending me is that your line has been tested and no issues have been found!!!!
The ping and speeds get slower/decrease throughout the day. Im sorry but sometimes its up to 800-900 ping instead of our normal eleven on MWEB johannesburg server, there is no noise on our line, absolutely clear and crisp!!! Plz help us !!! Our speeds range from 200 kbs to 1.5mb on speedtest.net ... This is not normal

Thanks Oliver
 
Two words dude.

CONGESTED EXCHANGE.

Search the "list of congested exchanges" thread to see if yours is on there. Soz I can't provide the link because I'm on a blackberry, but do check it out.

That could also explain why it is erratic. More ppl use the internet during the afternoon and evening, so that could explain the time of day latency shifts.

Telkom won't tell you if your exchange is congested.
 
Hey Jack. Ye, I am leaning towards it being a congested exchange, but I am trying to find out what my options are. Like can I be moved to a different exchange, are there any, must I order a new line? I don't really know what the options are. I did check the list of congested exchanges and my one isn't in the list.
 
Apyrael, do you perhaps know which exchange you are connected to? If not, what is the first 3 digits of your phone number?
 
Hi jack

Yes MWEB told us about that yesterday as the technical support called us, but they arent doing anything about it!!!!!! i still receive the message about your line has no issues, but how come this hasnt happened before. My neighbour 3 houses away gets full 4mb as i went to his house today!!!
 
Oliverwww, mweb CANT DO ANYTHING. It is entirely up to telkom to choose when they want to install more DSLAMS into the exchanges. All mweb can do is put pressure on telkom.

It is entirely possible that your neighbor is connected to a different exchange, that is free from congestion.

You could run a traceroute to help ascertain where the problem is. You would then be able to see where the faults lie.
 
Thanks Jack

Alright Jack

The only issue is that he is also connected to the montecasino exchange (465) So I dont know what is the issue??
http://mybroadband.co.za/vb/images/smilies/confused.gif
How could i run a test on my line, to see what the issue is??

And is this actually possible for telkom to fix?? Or will i always have bad ping and speeds?? Im sorry but even at 5-6 in the morning its like 60 -100 instead of 10-30!!!

Thanks Oliver

Ye I know MWEB cant do anything, but Im going to ask my friends dad ( he is like one of the top at MWEB, Andre Joubert) to see if he cant push telkom!!!! And my dad says we will be changing our adsl line to mweb not the data, he mentioned his friend could only get 1mb then he changed and now he gets 3.7!!!!
 
Telkom Trial - Free adsl

Hi

I suspect its the exchange as well, it just can't handle the load.
I too am experiencing terrible connection speeds, packet losses for the last three months.

I think everyone has taken the free three month adsl trial from Telkom.
 
:mad::twisted::mad::twisted: WELL THEN SCREW TELKOM!!!!!!!!!!!!!!!!!!!!!!!!!!!!! I CANT DO ANYTHING WITH THE INTERNET AND THEY DONT HELP!!!!!!!!!!!!!!!!!!!! STUPID IDIOTS!!!!!!!! I BET U MY DOG IS SMARTER THAN THEM
 
Jack Shizz said:
It is entirely up to telkom to choose when they want to install more DSLAMS into the exchanges.
Click to expand...
I'm starting to think the issue is more regional in nature. As indicated here Fourways (467) is also exhibiting the same bad performance, and I'm pretty sure Monte (465) also aggregates up to Bryanston like Fourways (where the regional ESRs reside).

I'm guessing one of the 10Gbps metroE rings or ESR routers in the area is completely saturated, or has failed with the load having to be taken up to the remaining ones.

Jack Shizz said:
You could run a traceroute to help ascertain where the problem is. You would then be able to see where the faults lie.
Click to expand...
Will probably tell you the latency starts from the 1st hop, that being the loopback inf (of your ISP) on the ESR terminating your session. More revealing would be if you have a more advanced router (like a Mikrotik) which will show the peer device name in your PPPoE session. Telkom encodes the location of the ESRs in their naming convention.
 
Last edited:
@Frequency43 i am connected to this exchange

http://www.broadbandstats.co.za/exchange/WGUS

Strange thing is the passed few days my latency has been fine... this might just be because it is weekend. I am going to check this week again. Telkom said that the exchange is not congested, but mweb logged an issue with them and asked them to check the exchange. Let's see what happens
 
Apyrael said:
@Frequency43 i am connected to this exchange

http://www.broadbandstats.co.za/exchange/WGUS

Strange thing is the passed few days my latency has been fine... this might just be because it is weekend. I am going to check this week again. Telkom said that the exchange is not congested, but mweb logged an issue with them and asked them to check the exchange. Let's see what happens
Click to expand...

I havent forgotten about you mate. Im currently in discussions regarding WGUS

Its a slow process :)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X