Peering to MWEB

signates said:
Cant seem to get onto DSTV's website (error 504). Dont know if its related to the peering or another problem.

Also trying to log into an online tiscali/mweb email account gives me 504 errors. Tried on Chrome and IE.

Tracert to www.dstv.com



1 1 ms 1 ms 1 ms 192.168.1.1
2 50 ms 44 ms 45 ms wbs-41-208-224-1.wbs.co.za [41.208.224.1]
3 94 ms 69 ms 44 ms 192.168.2.3
4 55 ms 95 ms 53 ms 192.168.2.9
5 59 ms 45 ms 48 ms 66.8.22.205
6 321 ms 152 ms 119 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]

7 * * * Request timed out.

Using a VPN has allowed me to access my Mweb internet email account and open www.dstv.com
Click to expand...

I had the same issue, works now though, I wonder what it was?
 
r00igev@@r said:
iBurst has been peering with MWEB at JINX for yonks. The peering agreement is covered in layers of dust.

We have been peering with anyone who wishes at JINX and each month send an email to Telkom, Vodacom, MTN and IS asking them to peer. Mostly they ignore our emails and phone calls.

If you are interested in seeing the traffic look at http://stats.jinx.net.za/
Click to expand...

Then why am I lagging all of a sudden since Wednesday on CODMW2 when someone whom uses an MWEB uncapped account, hosts. This is really bugging me, as we all know COD BO is around the corner...
 
SharkBait said:
Then why am I lagging all of a sudden since Wednesday on CODMW2 when someone whom uses an MWEB uncapped account, hosts. This is really bugging me, as we all know COD BO is around the corner...
Click to expand...

MWeb have started transiting us via Vodacom. I'll ask them why since we have a peer with them at JINX. Strange that they have moved from open peering to paid for transit?
 
Last edited:
r00igev@@r said:
MWeb have started transiting us via Vodacom. I'll ask them why since we have a peer with them at JINX. Strange that they have moved from open peering to paid for transit?
Click to expand...

Please come back asap, cause COD Bo is released tomoz and you know what that means. :D
 
http://www.ispa.org.za/inx/jinx-users

You can see here who is at the public peering point. This does not imply that all parties are peering as that is a choice each party has. This also does not mean they are not peering privately either but I doubt it as Telkom believe they are without peer in SA as do one or two others ;)
 
Some strange traceroute from IBurst to www.mweb.co.za. Can anybody shed some light on this? Seems that we are routed via MTN???

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

1 1 ms 1 ms 1 ms 192.168.10.10
2 76 ms 43 ms 54 ms wbs-196-2-112-1.wbs.co.za [196.2.112.1]
3 66 ms 43 ms 73 ms 192.168.0.97
4 198 ms 87 ms 58 ms 192.168.0.113
5 69 ms 53 ms 56 ms iburst-41-213-126-19.iburst.co.za [41.213.126.19
]
6 56 ms 60 ms 42 ms ge2-24.gw14.jnb6.za.mtnbusiness.net [66.8.42.21]

7 98 ms 68 ms 133 ms cte-core1.vwol.net [196.41.133.153]
8 116 ms 195 ms 128 ms 196.41.144.36
9 126 ms 88 ms 112 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
Gimli said:
Some strange traceroute from IBurst to www.mweb.co.za. Can anybody shed some light on this? Seems that we are routed via MTN???
Click to expand...

Yes, apparently mweb is doing this, but no one knows why, because word on the street is, that iburst does have a peering agreement with mweb. ;)

Rooigevaar is trying to find out what is going on.
 
SharkBait said:
Yes, apparently mweb is doing this, but no one knows why, because word on the street is, that iburst does have a peering agreement with mweb. ;)

Rooigevaar is trying to find out what is going on.
Click to expand...

So does WA, but only if you're in Cape Town...Only learned yesterday that if you're based elsewhere, you get the long route treatment. Which might explain why our WA account at work is so sluggish.
 
Durandal said:
So does WA, but only if you're in Cape Town...Only learned yesterday that if you're based elsewhere, you get the long route treatment. Which might explain why our WA account at work is so sluggish.
Click to expand...

WA has SAIX and IS BW, so I would assume that all WA IS accounts would be fine, since IS has a peering agreement in place with MWEB. SAIX on the other hand, is provided by telkom, which is self explanatory. ;)
 
SharkBait said:
WA has SAIX and IS BW, so I would assume that all WA IS accounts would be fine, since IS has a peering agreement in place with MWEB. SAIX on the other hand, is provided by telkom, which is self explanatory. ;)
Click to expand...

Not according to the info on the actual WA website. Apparently only the Cape-Town based customers are okay. I posted it on one of the ADSL forum threads. Will try find it.

Ah, here we go - from the WA website: Please be aware that due to the recent changes implemented by Mweb, affecting local transit through SAIX. Please see MyBB and MyGaming.

This change will adversely affect any Mweb Customers outside of the greater Cape Town region as Mweb only have Regional Peering in place at CINX and JINX. Traffic from the other major centres around South Africa will be rerouted internationally out of the Mweb Network, via London or other international destinations on connection from Johannesburg to the WA network.

This will impact all non-Cape Town Mweb customer's connectivity to the WA Network resources including our Data Centre.



This whole thing just confuses the heck out of me, to be honest. All I know is that our speeds at work have plummeted and WA can't explain it. My iBurst is great in comparison. Am thinking of bringing modem to work and using it as backup.
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X