WebAfrica/MWEB Peering?

[Johand]

Does WebAfrica and MWeb peer? I thought so, BUT my traceroutes tell a different story:

Tracing route to www.news24.com [196.28.41.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.66.1
  2    11 ms    13 ms     6 ms  wrbs-ip-esr-2.ipnet.wa.co.za [41.185.88.1]
  3    10 ms    12 ms     8 ms  vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
  4    12 ms    11 ms     8 ms  vl35.er.gw.cpt.za.wa.co.za [41.185.0.38]
  5     8 ms    10 ms     8 ms  upstream.vl102.gw.cpt.za.wa.co.za [196.220.59.230]
  6    45 ms    39 ms    39 ms  196.43.39.18
  7   236 ms   225 ms   232 ms  mweb-gw.telkom-ipnet.co.za [196.25.8.250]
  8   225 ms   233 ms   224 ms  vl-12.vic-hscore-2.mweb.co.za [196.22.169.243]
  9   221 ms   218 ms   219 ms  tengig-3-2.vic-core-sw2.mweb.co.za [196.22.169.70]
 10   225 ms   230 ms   224 ms  opt-65-1.optinet.net [196.22.163.22]
 11   225 ms   234 ms   224 ms  200.41.28.196.netactive.net [196.28.41.200]

Trace complete.

Does anybody know whether MWEB and WebAfrica are actually peering, or are they in the process of setting up peering? I know they are both represented at CINX...

 

[Kwerty]

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\duaN>tracert www.mweb.co.za

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

  1     1 ms     2 ms     1 ms  login.router [10.0.0.2]
  2     8 ms     7 ms     7 ms  wrbs-ip-esr-2.ipnet.wa.co.za [41.185.88.1]
  3     9 ms     9 ms     8 ms  vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
  4     9 ms     8 ms     9 ms  vl40.er.gw.cpt.za.wa.co.za [41.185.0.98]
  5    10 ms     9 ms     9 ms  198.32.214.25
  6    10 ms    10 ms    10 ms  196-28-178-134.adsl.mweb.co.za [196.28.178.134]

  7    11 ms    10 ms     9 ms  196.41.144.36
  8    10 ms    12 ms    10 ms  www.mweb.co.za [196.2.63.110]

Trace complete.

C:\Users\duaN>

Howzit guys

From what I've been told we are peering with MWEB.

Unfortunately I'm not 100% sure on the technical details but what I can do is log a query with our NOC department who can shed some more light on this.

Thanks

 

[HavocXphere]

Must be a fluke on your side. All is well on my side & looks like peering.

Tracing route to news24.co.za [152.111.193.28]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 23 ms 22 ms 19 ms tbnb-ip-esr-3.ipnet.wa.co.za [41.185.78.1]
3 47 ms 46 ms 46 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 47 ms 45 ms 46 ms vl40.er.gw.cpt.za.wa.co.za [41.185.0.98]
5 47 ms 46 ms 46 ms 198.32.214.25
6 49 ms 45 ms 46 ms 196-28-178-134.adsl.mweb.co.za [196.28.178.134]
7 48 ms 49 ms 48 ms 196.41.144.36
8 46 ms 46 ms 47 ms cte-gw122-leeuwenhof [196.41.133.234]
9 50 ms 50 ms 49 ms 152.111.193.28

Trace complete.

 

[Johand]

Must be a fluke on your side. All is well on my side & looks like peering.

I wonder - I saw it on two different accounts today (both Office and Private) on different lines on different exchanges...

 

[JasonH]

Here's MWeb (JHB) -> WebAfrica. My line is line at the time :/

tracert [url]www.wa.co.za[/url]

Tracing route to wa.co.za [196.220.63.42]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2   107 ms    16 ms    16 ms  41-133-88-1.dsl.mweb.co.za [41.133.88.1]
  3   661 ms    18 ms    18 ms  tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.16
9.146]
  4    17 ms   350 ms   353 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5    20 ms    21 ms    18 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
  6    59 ms    55 ms    52 ms  tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]

  7   478 ms   349 ms   392 ms  pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
  8   725 ms   248 ms   749 ms  149.6.98.17
  9   493 ms   395 ms   349 ms  te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.
165]
 10   248 ms   462 ms   349 ms  te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.
225]
 11   248 ms   298 ms   298 ms  te1-1.ccr01.lon05.atlas.cogentco.com [130.117.49
.106]
 12   264 ms   273 ms   258 ms  149.6.2.194
 13     *        *        *     Request timed out.
 14   558 ms   233 ms   759 ms  vl101.er.gw.cpt.za.wa.co.za [196.220.59.225]
 15   233 ms   232 ms   543 ms  vl32.cr.gw.cpt.za.wa.co.za [41.185.0.25]
 16   262 ms   235 ms   401 ms  fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
 17     *        *        *     Request timed out.
 18   243 ms   813 ms   235 ms  196.220.63.42

Trace complete.

 

[Armizael]

WA is in CINX - they can peer with MWeb there, but not at JINX. The servers you're tracerouting to are probably in JHB.

 

[HavocXphere]

WA is in CINX - they can peer with MWeb there, but not at JINX. The servers you're tracerouting to are probably in JHB.

That still doesn't explain 200+ms latency. The via CPT routing creates a penalty of ~50ms max.

 

[who.is.michael]

 

[WAJeff]

Hi guys,

Please see an update below from one of our Network Engineers below:

Ok, so how do we know where content is hosted?

And I thought that WA and Mweb were peering? Should this not eliminate any issues?

WA and M-Web is peering, but only in Cape Town for the time being. As to know what is hosted where, we do not have that information available.

How does this impact me, an WA user living in Pretoria?

If I want to connect to sites like the 24.com sites? Or game on the upcoming Call of Duty: Black Ops servers to be hosted by Mweb exclusively?

M-Web is working on a solution to have their JHB hosted content available in Cape Town as well, however there is no eta for this. The game servers we will have to see what M-Web will be doing.

Source

 

[Alestorm]

Good to hear that they'll sort out the JHB/CPT peering issues.