ok, that makes sense, but after using my details we went back to his and then rebooted the router again... and it was crap again... if the first two hops are out of mwebs control, then does telkom route differently based on our login credentials? that doesnt make sense to me
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Which is the most hair-raising South African mountain pass you've driven?
Gordon_R
Honorary Master
You definitely get a different IP address if you login to SAIX, versus MWeb. You might also get assigned to a different DSLAM as well. Beyond that I can't tell...
- Are you both in the same city? There is, for example, a large difference between CPT and JHB when it comes to latency, due to network layout choices.
- Does the router report errors on the line? If so, how many? A certain amount is acceptable, but too many will affect the line speed and latency a lot.
- Congestion on the exchange may cause this, if you are on different exchanges.
- It may indicate a fault on the DSLAM or DSLAM port his line plugs into.
I actually went to the guys house. I put my details into HIS router and then tested his internet from his pc. So location has nothing to do with it. Being at his house using his line would mean that it was the same exchange.
His details on his router and his pc = lame latency
My details on his router and his pc = amazing latency
Which leads me to believe that the line to the dslam is not to blame, and that it is not a problem on the exchange.
His details on his router and his pc = lame latency
My details on his router and his pc = amazing latency
Which leads me to believe that the line to the dslam is not to blame, and that it is not a problem on the exchange.
Your DSLAM seems to be determined by your login. I live in Gordons Bay and switched to Mweb 384k uncapped a month or two ago and my latency to the DSLAM is horrific, currently 1371ms. I complained to Mweb and they said it is the DLSAM and I must talk to Telkom as I am using 'Saix wholesale' bandwidth as my login is [email protected], fat lot of good that does me, I pay Mweb and they must sort it out. Needless to say Telkom are not interested either. So all in all very third world.
sand_man
Honorary Master
Gees got 3 MWEB accounts, 4mb currently performing well below parr... Anyone know of any issues..??
blaaislaai
Executive Member
Been getting crap latency on mweb 4mb for the last few weeks now, cant game at all.. use to get 31- 39ms on local gaming servers
Gordon_R
Honorary Master
Today (Tues 10th), while everyone is getting excited about the 10Mbps lines (including Clareinch exchange), my local latency has been creeeping up, and now its a ridiculous 200ms on local sites!?
Code:
Tracing route to www.dstv.com [196.28.65.142]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms home.gateway [192.168.1.254]
2 7 ms 7 ms 7 ms 41-132-48-1.dsl.mweb.co.za [41.132.48.1]
3 264 ms 269 ms 271 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 192 ms 197 ms 198 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 253 ms 257 ms 255 ms tengig-3-2.vic-core-sw2.mweb.co.za [196.22.169.70]
6 319 ms 317 ms 313 ms 135.75.28.196.netactive.net [196.28.75.135]
7 244 ms 241 ms 239 ms 192.168.196.17
8 225 ms 223 ms 221 ms www.dstv.com [196.28.65.142]
Trace complete.
pmurgs
Well-Known Member
Also been getting terribly latency with Mweb 4mb uncapped lately. Location Fish Hoek, Cape Town.
Code:
Tracing route to sabela.saix.net [196.43.1.9]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 * 258 ms 326 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.16
9.146]
4 * 209 ms 212 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 * * * Request timed out.
6 * 205 ms 243 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 ^C
Tracing route to [url]www.dstv.com[/url] [196.28.65.142]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 * * * Request timed out.
4 312 ms 254 ms * vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 * * * Request timed out.
6 135 ms 166 ms 135 ms 135.75.28.196.netactive.net [196.28.75.135]
7 281 ms 242 ms * 192.168.196.17
8 * * 280 ms CL2www2.m-net.co.za [196.28.65.142]
Trace complete.hey guys, just thought i would add that mweb uncapped used to ping at like 250 ms approx. and now has changed to 350. the change really has dramatically affected mmo/fps performance in my opinion.
also noted that the mweb capped services are still pinging at 250 ms. and also also noted that ping altered like this about 10 days before mweb released their unshaped uncapped gaming package. for 2.5k per month...
suspicious?... who knows...
also noted that the mweb capped services are still pinging at 250 ms. and also also noted that ping altered like this about 10 days before mweb released their unshaped uncapped gaming package. for 2.5k per month...
suspicious?... who knows...
Adenoid Hynkel
Executive Member
C:\Users\JP>ping sabela.saix.net
Pinging sabela.saix.net [196.43.1.9] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 196.43.1.9:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\JP>tracert sabela.saix.net
Tracing route to sabela.saix.net [196.43.1.9]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms sx762.dummy.porta.siemens.net [10.0.0.2]
2 8 ms 8 ms 8 ms 41-133-108-1.dsl.mweb.co.za [41.133.108.1]
3 30 ms 30 ms 30 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 31 ms 30 ms 31 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 35 ms 36 ms 33 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 52 ms 50 ms 45 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
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.
Pinging sabela.saix.net [196.43.1.9] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 196.43.1.9:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\JP>tracert sabela.saix.net
Tracing route to sabela.saix.net [196.43.1.9]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms sx762.dummy.porta.siemens.net [10.0.0.2]
2 8 ms 8 ms 8 ms 41-133-108-1.dsl.mweb.co.za [41.133.108.1]
3 30 ms 30 ms 30 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 31 ms 30 ms 31 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 35 ms 36 ms 33 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 52 ms 50 ms 45 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
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.
Roman4604
Executive Member
Telkom seem to have blocked ICMP to this host, just use www.telkom.co.za instead.
Adenoid Hynkel
Executive Member
C:\Users\JP>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=84ms TTL=244
Reply from 196.43.22.222: bytes=32 time=89ms TTL=244
Reply from 196.43.22.222: bytes=32 time=103ms TTL=244
Reply from 196.43.22.222: bytes=32 time=110ms TTL=244
Ping statistics for 196.43.22.222:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 110ms, Average = 96ms
C:\Users\JP>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 sx762.dummy.porta.siemens.net [10.0.0.2]
2 14 ms 9 ms 8 ms 41-133-108-1.dsl.mweb.co.za [41.133.108.1]
3 197 ms 185 ms 185 ms tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.169.134]
4 193 ms 191 ms 190 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 149 ms 127 ms 123 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 182 ms 182 ms 196 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 163 ms 166 ms 164 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
8 169 ms 170 ms 168 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
9 138 ms 145 ms 149 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
10 138 ms 132 ms 130 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
Trace complete.
Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=84ms TTL=244
Reply from 196.43.22.222: bytes=32 time=89ms TTL=244
Reply from 196.43.22.222: bytes=32 time=103ms TTL=244
Reply from 196.43.22.222: bytes=32 time=110ms TTL=244
Ping statistics for 196.43.22.222:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 110ms, Average = 96ms
C:\Users\JP>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 sx762.dummy.porta.siemens.net [10.0.0.2]
2 14 ms 9 ms 8 ms 41-133-108-1.dsl.mweb.co.za [41.133.108.1]
3 197 ms 185 ms 185 ms tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.169.134]
4 193 ms 191 ms 190 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 149 ms 127 ms 123 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 182 ms 182 ms 196 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 163 ms 166 ms 164 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
8 169 ms 170 ms 168 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
9 138 ms 145 ms 149 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
10 138 ms 132 ms 130 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
Trace complete.
I live in the Strand area and I've been having the same bad latency on hop 2 for about 4 months now. I tested my connection with 3 different accounts (my uncapped 384 as well as 1 x unshaped going through SAIX and another IS pre-paid account). When I do traceroutes, I get the same result regardless of which ISP I'm using - always that bad spike on hop 2.
I've been onto all my ISP's as well as Telkom numerous times. My ISP's are determined that the problem is at the exchange and Telkom is equally determined that their equipment is functioning properly. I had a telkom technician at my house about two weeks ago - everything fine. But here is the interesting thing - the latency on hop 2 seems to be particularly bad from about 7pm to 10pm and almost all the time on weekends. After exhausting all posible avenues (and this post is really the cliffnotes-of-cliffnotes edtion of what I went through with Telkom), the only thing that remains is over-contention at our Strand exchange. I've put this to Telkom and the only answer they gave me is that I'll just have to hang on until they upgrade the exchange ... some day.
I don't know what else to do. Just as another reference, a traceroute from my unshaped account (SAIX) managed by Web Africa.
Tracing route to www.webafrica.co.za [196.220.58.66]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 1463 ms 1458 ms 1382 ms dsl-185-83-1.dynamic.wa.co.za [41.185.83.1]
3 1182 ms 1163 ms 1093 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 940 ms 977 ms 1183 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
5 740 ms 650 ms 665 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
6 567 ms 583 ms 599 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
7 521 ms 526 ms 583 ms wa-acc1.wadns.net [196.220.39.253]
8 729 ms 794 ms 900 ms 196.220.58.66
Last edited:
Am in Gordon's Bay on 384k MWEB uncapped. Ping times are horrific most of the time, this one is 443ms but have seen it over 1000 very often. I do notice that they drop to under 50ms after about 10 at night so seems to be traffic related. Have reported this to Mweb a few times but no luck. Seems as if Telkom have all the ISPs by the short and curly as they control access to their networks. I am thinking about switching back to Telkom just so that I can log issues straight with them, it's just that I love not having to bother about a cap, it's so first world!
Tracing route to sabela.saix.net [196.43.1.9]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.254
2 443 ms 545 ms 501 ms dsl-241-160-01.telkomadsl.co.za [41.241.160.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
Tracing route to sabela.saix.net [196.43.1.9]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.254
2 443 ms 545 ms 501 ms dsl-241-160-01.telkomadsl.co.za [41.241.160.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
When in doubt ask Uncle Google - IT guys are stingy with their hard-earned info
http://www.exit109.com/~jeremy/news/providers/traceroute.html is a good link. Original command is traceroute but DOS commands can only be 6 (6 & 3 for the extension) characters long so it got cut to tracert.exe. Here's my very poor ping:
Tracing route to www.mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.254
2 982 ms 1040 ms 1029 ms dsl-241-160-01.telkomadsl.co.za [41.241.160.1]
3 824 ms 740 ms 735 ms wblv-ip-lir-1-gig-4-0-0.telkom-ipnet.co.za [196.43.8.190]
4 748 ms 735 ms 730 ms 196.43.25.206
5 880 ms 933 ms 955 ms ge0-3.br2.cpt1.za.mtnbusiness.net [196.7.8.206]
6 791 ms 807 ms 793 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
7 774 ms 787 ms 835 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
8 989 ms 1023 ms 1024 ms 196.30.213.108
9 793 ms 755 ms 782 ms firewall1.jnb2.host-h.net [196.7.216.173]
10 790 ms 780 ms 780 ms mybroadband.co.za [41.203.21.137]
Trace complete.
Basically it's going down your network to the destination and telling you how long it takes to send a packet of test info to each host and back to your PC and does it 3 times for each one. Remember the Internet is a muddle of gazillions of machines, info travels from the one to the next hence the name Inter-net. So in my case step 1 is my own ADSL router, step 2 is the point where I hit the Telkom network (pathetic, is overloaded as it drops to under 50 at after 10PM), etc until it gets to the final destination. Step 2 should be under 20 or less.
Am on 384k uncapped Mweb and trying to play BF2 on the Saix servers but latency is too high, Mweb can't help as it is Telkom's network and telkom are not interested as I am Mweb's client.
http://www.exit109.com/~jeremy/news/providers/traceroute.html is a good link. Original command is traceroute but DOS commands can only be 6 (6 & 3 for the extension) characters long so it got cut to tracert.exe. Here's my very poor ping:Tracing route to www.mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.254
2 982 ms 1040 ms 1029 ms dsl-241-160-01.telkomadsl.co.za [41.241.160.1]
3 824 ms 740 ms 735 ms wblv-ip-lir-1-gig-4-0-0.telkom-ipnet.co.za [196.43.8.190]
4 748 ms 735 ms 730 ms 196.43.25.206
5 880 ms 933 ms 955 ms ge0-3.br2.cpt1.za.mtnbusiness.net [196.7.8.206]
6 791 ms 807 ms 793 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
7 774 ms 787 ms 835 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
8 989 ms 1023 ms 1024 ms 196.30.213.108
9 793 ms 755 ms 782 ms firewall1.jnb2.host-h.net [196.7.216.173]
10 790 ms 780 ms 780 ms mybroadband.co.za [41.203.21.137]
Trace complete.
Basically it's going down your network to the destination and telling you how long it takes to send a packet of test info to each host and back to your PC and does it 3 times for each one. Remember the Internet is a muddle of gazillions of machines, info travels from the one to the next hence the name Inter-net. So in my case step 1 is my own ADSL router, step 2 is the point where I hit the Telkom network (pathetic, is overloaded as it drops to under 50 at after 10PM), etc until it gets to the final destination. Step 2 should be under 20 or less.
Am on 384k uncapped Mweb and trying to play BF2 on the Saix servers but latency is too high, Mweb can't help as it is Telkom's network and telkom are not interested as I am Mweb's client.
Hi P3t3rmax
Have you spoken to one of our reps about this yet? You're quite right this looks like a cut and dried case of DSLAM utlization. We have had some success in escalating these to Telkom. A lot depends on what they have available at the exchange in question. If there is available capacity it's a matter of getting them to change the configuration. If they have to provision additional network capacity to the exchange then the timeline can become a lot more extended.
If you haven't spoken to one of our reps yet please PM your account details to MWEB Operations and I'll arrange for it to be escalated.
Have you spoken to one of our reps about this yet? You're quite right this looks like a cut and dried case of DSLAM utlization. We have had some success in escalating these to Telkom. A lot depends on what they have available at the exchange in question. If there is available capacity it's a matter of getting them to change the configuration. If they have to provision additional network capacity to the exchange then the timeline can become a lot more extended.
If you haven't spoken to one of our reps yet please PM your account details to MWEB Operations and I'll arrange for it to be escalated.