A number of articles have appeared on Mybroadband about MWEB’s strategy to force MTN, Vodacom and Telkom to peer with them.
Two comments:
-
MWEB already peers with MTN. Here are the two hops between their networks1:
6 g-0-3-vic-jinx-2.mweb.co.za (196.22.163.1)
7 mtnns-2.jinx.net.za (198.32.142.31)I think what MWEB probably means by "transit" is that MTN charges them for peering. If MTN agreed to MWEB's ultimatum, they would still be peering at JINX. So if you are an MWEB customer who likes to surf Mybroadband.co.za2, you should demand a discount to compensate for the de-peering.
-
"We do not believe in paying for transit or selling transit. Rather, we have invited all of them to peer with us."
-- MyBB quoting MWEB ISP CEO Derek HershawWhat makes buying transit in London different from Johannesburg?
{ 2 } Comments
MTN-NS and MTN-Business used to be 2 separate networks, while they are still in the process of migrating them, it doesn’t mean that M-Web is peering with all of MTN.
For example a traceroute to myadsl.co.za which is hosted on the MTN-Business network:
1 5 ms <1 ms <1 ms router.heaven.za.net [10.0.0.1]
2 72 ms 100 ms 98 ms 192.168.1.254
3 9 ms 9 ms 9 ms 41-132-38-1.dsl.mweb.co.za [41.132.38.1]
4 10 ms 9 ms 9 ms 196-28-178-190.adsl.mweb.co.za [196.28.178.190]
5 34 ms 34 ms 34 ms 196.22.169.41
6 34 ms 33 ms 34 ms 196.22.169.61
7 36 ms 37 ms 36 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
8 68 ms 67 ms 72 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
9 256 ms 255 ms 255 ms 196.22.175.218
10 255 ms 254 ms 255 ms 79.141.38.37.available.above.net [79.141.38.37]
11 255 ms 255 ms 255 ms so-0-0-0.mpr1.lhr3.uk.above.net [64.125.27.226]
12 273 ms 272 ms 273 ms xe-2-0-0.mpr2.lhr3.uk.above.net [64.125.28.146]
13 257 ms 256 ms 255 ms 213-152-230-91.mtnns.net [213.152.230.91]
14 276 ms 275 ms 276 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
15 273 ms 273 ms 273 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
16 276 ms 277 ms 277 ms 196.30.213.108
17 274 ms 273 ms 274 ms firewall1.jnb2.host-h.net [196.7.216.173]
18 274 ms 272 ms 274 ms mybroadband.co.za [41.203.21.137]
And now to mtn.co.za which used to be MTN-NS
1 5 ms <1 ms <1 ms router.heaven.za.net [10.0.0.1]
2 12 ms 99 ms 99 ms 192.168.1.254
3 9 ms 9 ms 9 ms 41-132-38-1.dsl.mweb.co.za [41.132.38.1]
4 9 ms 9 ms 9 ms 196-28-178-190.adsl.mweb.co.za [196.28.178.190]
5 34 ms 34 ms 34 ms 196.22.169.41
6 34 ms 34 ms 34 ms 196.22.169.61
7 37 ms 36 ms 37 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
8 34 ms 34 ms 33 ms g-0-3-vic-jinx-2.mweb.co.za [196.22.163.1]
9 33 ms 32 ms 32 ms mtnns-2.jinx.net.za [198.32.142.31]
10 36 ms 40 ms 38 ms jh-cr-2.za–jh-pr-1.za.mtnns.net [196.44.0.223]
11 36 ms 35 ms 36 ms rb-cr-1.za–jh-cr-2.za-a.mtnns.net [196.44.31.94]
12 60 ms 34 ms 34 ms rb-dca-1.za–rb-cr-1.za-a.mtnns.net [196.44.0.147]
13 34 ms 34 ms 34 ms mtn-rb-1–rb-ad-1-a.mtnns.net [196.44.8.211]
14 * * * Request timed out.
15 35 ms 34 ms 34 ms 196-11-240-17.mtn.co.za [196.11.240.17]
Both done on M-Web from CT.
Hi David
Thanks for the comment.
I recently heard from a MTN Business executive that the old TICSA/UUNET/Verizon Business SA infrastructurefo is being absorbed into the MTN-NS network (as the latter is by far the larger of the two). I wonder why, if this is the case, and MWEB peers with MTN-NS, the MTN Business peering problem hasn’t just gone away?
Regards,
Simeon.
Post a Comment