Telkom & Mweb peering again to some extent?

[JasonH]

Looks like the issue has been fixed - here's MWEB/Telkom peering )

[root@mgmt ~]# tracert telkom.co.za
traceroute to telkom.co.za (196.43.22.222), 30 hops max, 40 byte packets
 1  vz2-jnb.vps.za-dns.com (196.2.147.180)  0.023 ms  0.014 ms  0.012 ms
 2  65.75.28.196.netactive.net (196.28.75.65)  0.891 ms  0.923 ms  0.929 ms
 3  129.75.28.196.netactive.net (196.28.75.129)  1.279 ms  1.352 ms  1.454 ms
 4  tengig-1-6.vic-hscore-1.mweb.co.za (196.22.169.65)  1.452 ms  1.456 ms  1.553 ms
 5  TenGigE0-0-0-0.11.vic-up-1.mweb.co.za (196.22.169.225)  4.686 ms  4.697 ms  4.708 ms
 6  197-80-4-117.jhb.mweb.co.za (197.80.4.117)  1.284 ms  1.301 ms  1.308 ms
 7  196.43.25.137 (196.43.25.137)  1.325 ms  0.756 ms  0.902 ms
 8  196.43.39.166 (196.43.39.166)  1.328 ms  1.052 ms  1.044 ms
 9  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za (196.43.23.6)  1.470 ms  1.467 ms  1.537 ms
10  nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za (196.43.23.30)  4.095 ms  4.061 ms  4.197 ms
11  nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za (196.43.22.222)  4.001 ms  4.039 ms  4.116 ms

 

[shaunvw]

I noticed this last night playing blops I was actually able to play on a mweb server

 

[Big Bean]

Yay!
1 32 ms 25 ms 19 ms dsl-240-220-01.telkomadsl.co.za [41.240.220.1]
2 28 ms 27 ms 19 ms 196.43.11.218
3 58 ms 27 ms 32 ms 196.43.25.206
4 28 ms 32 ms 26 ms 197-84-4-22.cpt.mweb.co.za [197.84.4.22]
5 29 ms 29 ms 27 ms Vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
6 31 ms 28 ms 31 ms 196-28-178-34.adsl.mweb.co.za [196.28.178.34]
7 23 ms 29 ms 29 ms www.mweb.co.za [196.2.63.110]

 

[fragtion]

Ah, I spoke too soon about the Cape-town-only peering. Seems like MWEB-SAIX are also peering in JHB now. Good stuff! Hope they organized enough capacity, saw it was congested and laggy earlier today