MWEB peering changes begin - fallout imminent

[Riot2]

lol, cool story
what i see is: paying the same, receiving worse service (how is this something not worthy of complaining about)
at least i got a free 1gb afrihost unshaped account i can use for gaming in the mean time

 

[ijack]

I agree with you. My one branch still uses Mweb, (dont ask, shouldve cancelled a long time ago). Now because Rudi is trying to look like God, we the end use, whom are paying good money, are suffering. Where is my saving? Will I get a discount this month for an inferior local service?

I can hardly access Remote Desktop on my server, as Mweb has still not unshaped the remote desktop port. Used to work just fine when they were peering.

They should play their war games behind the scenes,. I just want what I pay for . R4999 is alot of money for internet!

look how utterly pathetic this is
Tracing route to www.myadsl.co.za [41.203.21.137]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 9 ms 15 ms 13 ms 41-132-28-1.dsl.mweb.co.za [41.132.28.1]
3 10 ms 10 ms 11 ms tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.16
9.134]
4 10 ms 10 ms 11 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 13 ms 11 ms 11 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 18 ms 19 ms 17 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]

7 257 ms 251 ms 251 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 269 ms 267 ms 337 ms 79.141.38.37.available.above.net [79.141.38.37]

9 267 ms 267 ms 279 ms so-0-0-0.mpr1.lhr3.uk.above.net [64.125.27.226]

10 249 ms 253 ms 255 ms xe-1-1-0.mpr2.lhr3.uk.above.net [64.125.27.158]

11 * * * Request timed out.
12 254 ms 253 ms 254 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.2
2]
13 254 ms 254 ms 403 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
14 255 ms 255 ms 258 ms 196.30.213.108
15 255 ms 254 ms 253 ms firewall1.jnb2.host-h.net [196.7.216.173]
16 265 ms 254 ms 254 ms mybroadband.co.za [41.203.21.137]

im not sure why the end users are so happy about mwebs bull**** policy... peer for free or else no peering
now the ppl who get screwed over are the end users who get no form of savings of compensation for the crappy service - i means its noticably bad just browsing myadsl.co.za thx to the change
and in the end if they do decide to peer, its still gonna just be cheaper for mweb, who are unlikely to pass the savings on to the end user

 

[Hotmetal]

I agree with you. My one branch still uses Mweb

See, there is the problem. All your branches should be using MWeb. Problem solved.

They should play their war games behind the scenes,

Clearly you haven't been paying attention. 'Behind the scenes' hasn't worked for years. That is why we are paying a fortune for our internet. Close minded people FTL.

 

[proguy]

Well tomorrow morning im faxing off my "end subscription form" to mweb, really can do much if with my VPN & RDP to other branches/users on other ISP,

Sorry been with you many years but our time will end on the 30 November.

 

[TrueSeeker]

Well as an MWEB customer I can say this. I feel like I'm connected to the free world just a little bit more now. The other providers can either join the party or go to hell for all I care.

When WACS and broadband Infraco comes into play soon then we'll hardly feel the international jump (if it is still there that is...). Of course we here in Cape Town are also going to have a very nice open fiber optic ring to run on in the next few months as well. Probably very closely linked to BI and WACS. I am hoping personally to see a maximum 180ms ping to EU then. From experience I know I will not even feel that when gaming or browsing. I sometimes have a 250ping on overseas game servers and I still do not lag. Given there's a barely noticeable response delay sometimes yeah. Also... Since most South African sites are hosted internationally to save money (because the bastards are not open peering) I really think just about Hetzner alone will give problems. Hmm... W'sup MTN?

 

[TrueSeeker]

Well tomorrow morning im faxing off my "end subscription form" to mweb, really can do much if with my VPN & RDP to other branches/users on other ISP,

Sorry been with you many years but our time will end on the 30 November.

Convince everybody to get MWeb accounts. They are affordable and your international browsing will speed up

 

[Mike Hoxbig]

im not sure why the end users are so happy about mwebs bull**** policy... peer for free or else no peering
now the ppl who get screwed over are the end users who get no form of savings of compensation for the crappy service - i means its noticably bad just browsing myadsl.co.za thx to the change
and in the end if they do decide to peer, its still gonna just be cheaper for mweb, who are unlikely to pass the savings on to the end user

Give it some time, we know the short term effects but we need this to happen. Perhaps we need to take 1 step back in order to move 10 leaps forward.

 

[Biscuit1018]

Is WebAfrica deciding not to peer, are they insane??? Your hosting isn't going to feel "premium" if guys are getting ridiculous latency.

I think WA are already peering for free with Mweb.

I have a MWEB and WA account. MWeb to WA 12ms. WA to Mweb 12 ms.

WA are also peering with telkom etc but that is obviously at a cost

 

[proguy]

Sadly Mweb dont have a 3G network, maybe they need a 4Gs network, but if you running a business sometimes you need things to work now and not in 6months when everybody wakes up.

 

[KinsZA]

Biscuit with your mweb account try ping one of the wage servers and see what you get, I get about 220ms.

I still dont see the "noticeably slower web browsing", there's stuffall difference.

 

[Alestorm]

Biscuit with your mweb account try ping one of the wage servers and see what you get, I get about 220ms.

I still dont see the "noticeably slower web browsing", there's stuffall difference.

I get 9-12ms, even though I'm now getting +-300ms to mybroadband since they cut their peering links. Looks like WA is peered with Mweb.

Also I think it's obvious that RPM and the rest of MyADSL support MWeb in their efforts, so we should put pressure on mtn business to start peering. If they won't budge then moving a massive site like mybroadband off their hosting would be a good bargaining tool.

 

[portcullis]

I get 9-12ms, even though I'm now getting +-300ms to mybroadband since they cut their peering links. Looks like WA is peered with Mweb.

This could be a Cape Town only thing:

tracert www.wage.co.za

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

1 <1 ms <1 ms <1 ms 192.168.75.254
2 1 ms <1 ms <1 ms 10.0.0.1
3 9 ms 8 ms 9 ms 41.132.70.1
4 15 ms 9 ms 10 ms 196.28.178.178
5 10 ms 10 ms 11 ms 196.28.178.133
6 11 ms 17 ms 11 ms 198.32.214.45
7 12 ms 11 ms 12 ms vl40.cr.gw.cpt.za.wa.co.za [41.185.0.97]
8 12 ms 12 ms 14 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
9 14 ms 12 ms 13 ms wa-acc1.wadns.net [196.220.39.253]
10 13 ms 16 ms 13 ms 196.220.58.65

Trace complete.

 

[ld13]

I get 9-12ms, even though I'm now getting +-300ms to mybroadband since they cut their peering links. Looks like WA is peered with Mweb.

Yep, On the WA forums, today @ 05:26PM

We have been peering with a number of companies for some time now. This list includes Mweb.
If you're interested to know more about peering in South Africa, check out: http://www.ispa.org.za/inx/
The ISPA have a very detailed write, and actively promote it to all ISPA members.

 

[Gatecrasher]

If WA and MWeb are peering, something is not quite right. My pings to Wage go via London.

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

  1     1 ms     1 ms     5 ms  DD-WRT [192.168.1.1]
  2    11 ms    11 ms    17 ms  41-133-132-1.dsl.mweb.co.za [41.133.132.1]
  3   121 ms   116 ms   110 ms  tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.163.206]
  4    59 ms    80 ms    80 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5    87 ms    48 ms    90 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
  6   137 ms    85 ms    92 ms  tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
  7   331 ms   264 ms   292 ms  196.22.175.210
  8   281 ms   344 ms   285 ms  149.6.98.5
  9   466 ms   313 ms   427 ms  te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
 10   263 ms   305 ms   264 ms  te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.225]
 11   315 ms   282 ms   305 ms  te1-1.ccr01.lon05.atlas.cogentco.com [130.117.49.106]
 12   245 ms   244 ms   312 ms  149.6.2.194
 13   258 ms   343 ms   328 ms  196.43.39.78
 14   242 ms   235 ms   255 ms  vl101.er.gw.cpt.za.wa.co.za [196.220.59.225]
 15     *      301 ms   270 ms  vl32.cr.gw.cpt.za.wa.co.za [41.185.0.25]
 16   236 ms   258 ms   235 ms  fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
 17   235 ms   261 ms   316 ms  wa-acc1.wadns.net [196.220.39.253]
 18   237 ms   303 ms   237 ms  196.220.58.65

Trace complete.

 

[Alestorm]

If WA and MWeb are peering, something is not quite right. My pings to Wage go via London.

Well WA have said that they are and MWeb obviously will be happy to peer.

But WebAfrica and MWeb are only together in the CINX, not in J(oburg)INX. I guess until WebAfrica get a bigger presence in JHB or other ISP's give in to MWeb's free peering plans this will only work for Cape Town users.

 

[Gatecrasher]

Well WA have said that they are and MWeb obviously will be happy to peer.

But WebAfrica and MWeb are only together in the CINX, not in J(oburg)INX. I guess until WebAfrica get a bigger presence in JHB or other ISP's give in to MWeb's free peering plans this will only work for Cape Town users.

But shouldn't my ping stay with MWeb and be routed by them to MWeb in CT and then link to WA at CINX? Why does it need to go to London?

 

[Alestorm]

But shouldn't my ping stay with MWeb and be routed by them to MWeb in CT and then link to WA at CINX? Why does it need to go to London?

Their network doesn't go from Cape Town to Joburg, they must have gone through some links that they've now cut off (I guess). But you'd think they could get SAIX/Telkom links which are still meant to be up until next week.

 

[Shayd]

I think WA are already peering for free with Mweb.

I have a MWEB and WA account. MWeb to WA 12ms. WA to Mweb 12 ms.

WA are also peering with telkom etc but that is obviously at a cost

Sorry bud Traceroute and Speedtest do not lie, looks like CINX peering is working so guys in CT are fine but with no peering in JINX the routers are sending all our traffic internationally.

 

[scruffy]

Ooooh nice!

I would love to see how the guys offering Local-only accounts and how capped accounts still access the so called "local" content.

 

[MonTage]

Latency? What Latency?

Seriously So much of Latency!!! how long till this corrects itself?