MWEB data routed internationally from Telkom line

?

<?php?>

Well-Known Member
Joined
Nov 15, 2010
Messages
367
Reaction score
0
Hi, I'm struggling with high latency issues in reference to downloading e-mail messages from MWEB's POP3 server.

I did a "traceroute" and noticed that the data is routed internationally. When I do a trace to other non-MWEB hosted domain, the data is routed locally. Is it possible to determine from the trace below, if MWEB or Telkom is routing the data internationally?


Code: 
[root@pdc /]# traceroute -m 100 pop3.mweb.co.za
traceroute to pop3.mweb.co.za (196.28.76.80), 100 hops max, 40 byte packets
 1  196.25.202.193 (196.25.202.193)  2.321 ms  2.984 ms  3.514 ms
 2  obfn-ip-esr-1-wan.telkom-ipnet.co.za (196.25.90.225)  20.973 ms  25.595 ms  35.178 ms
 3  lon-ip-dir-telecity-gig-1-0-2.telkom-ipnet.co.za (196.43.9.217)  310.645 ms  315.701 ms  320.204 ms
 4  vl1088.mpd01.lon01.atlas.cogentco.com (149.6.2.193)  325.322 ms  330.062 ms  301.568 ms
 5  te1-8.ccr01.lon01.atlas.cogentco.com (130.117.3.226)  336.536 ms  341.092 ms te3-2.ccr01.lon01.atlas.cogentco.com (130.117.1.73)  345.956 ms
 6  te1-1.ccr01.lon09.atlas.cogentco.com (154.54.36.166)  350.080 ms  292.595 ms  292.264 ms
 7  149.6.98.6 (149.6.98.6)  305.993 ms 149.6.98.18 (149.6.98.18)  317.655 ms  321.689 ms
 8  pos0-1-3-0.mid-up-1.mweb.co.za (196.22.163.233)  563.594 ms pos0-0-1-2.mid-up-1.mweb.co.za.175.22.196.in-addr.arpa (196.22.175.209)  553.978 ms  546.047 ms
 9  TenGigE0-1-1-0.vic-up-1.mweb.co.za (196.22.169.209)  571.561 ms  575.492 ms  559.361 ms
10  vl-12.vic-hscore-2.mweb.co.za (196.22.169.243)  567.447 ms  579.389 ms  583.444 ms
11  tengig-3-2.vic-core-sw2.mweb.co.za (196.22.169.70)  587.561 ms  591.499 ms  595.553 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  tengig-3-2.vic-core-sw2.mweb.co.za (196.22.169.70)  563.741 ms !X * *
[root@pdc /]#

Thanks
 
All Mweb traffic will be regarded as international traffic, since it is going to be routed via London. See the link that biena provided for more information.

So once you've exceeded your international cap, you won't be able to access Mweb stuff any more. AFAIK Mweb hosts quite a lot of essential news services, like News24 & SuperSport.
 
Problem is on Telkom's side. They are refusing to peer openly and freely with MWEB at a local level. All or most other ISPs are now peering directly with each other and with MWEB, exchanging traffic locally and efficiently, in a free and open manner (AFAIK).

Telkom still wants to charge for local peering, and MWEB have put their foot down and refused flatly. That's why all traffic between the MWEB and Telkom networks is being exchanged internationally, at the London POP, where both companies have peering agreements with UK based operators. Very stupid mentality from Telkom's side. One of the only RSA operators who are refusing to peer, when the rest of the industry have moved forward. Typical.

It's time to change your ISP from Telkom to someone else. Try WebAfrica, Afrihost, MWEB or Axxess. All excellent choices.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X