MWEB peering changes begin - fallout imminent

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

2 * * * Request timed out.
3 44 ms 35 ms 46 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.163.206]
4 56 ms 89 ms 48 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 98 ms 167 ms 118 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 235 ms 199 ms 181 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
7 268 ms 294 ms 274 ms 196.22.175.214
8 317 ms 258 ms 337 ms 149.6.98.5
9 431 ms 433 ms 569 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 392 ms 408 ms 358 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
11 446 ms 370 ms 503 ms te2-1.ccr01.lon05.atlas.cogentco.com [130.117.49.94]
12 267 ms 293 ms 223 ms 149.6.2.194
13 380 ms 403 ms 365 ms 196.43.51.26
14 447 ms 479 ms 497 ms vl102.er.gw.cpt.za.wa.co.za [196.220.59.229]
15 237 ms 262 ms 259 ms vl33.cr.gw.cpt.za.wa.co.za [41.185.0.29]
16 236 ms 352 ms 360 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
17 236 ms 291 ms 243 ms wa-acc1.wadns.net [196.220.39.253]
18 292 ms 239 ms 255 ms 196.220.58.66

Trace complete.

tracert www.wage.co.za

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

2 * * * Request timed out.
3 225 ms 170 ms 210 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
4 205 ms 58 ms 64 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 39 ms 81 ms 87 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 100 ms 101 ms 78 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
7 325 ms 445 ms 421 ms 196.22.175.218
8 412 ms 482 ms 507 ms 149.6.98.17
9 283 ms 314 ms 296 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 349 ms 283 ms * te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.225]
11 362 ms 251 ms 307 ms te1-1.ccr01.lon05.atlas.cogentco.com [130.117.49.106]
12 286 ms 276 ms 290 ms 149.6.2.194
13 331 ms 327 ms 327 ms 196.43.51.26
14 319 ms 328 ms 416 ms vl102.er.gw.cpt.za.wa.co.za [196.220.59.229]
15 436 ms 475 ms 327 ms vl33.cr.gw.cpt.za.wa.co.za [41.185.0.29]
16 336 ms 251 ms 256 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
17 279 ms 331 ms 298 ms wa-acc1.wadns.net [196.220.39.253]
18 329 ms 341 ms 306 ms 196.220.58.65

Trace complete.
 
So your thinking is, support the company that has been raping consumers for decades, close down the smaller ISP's and then allow them to rape you for the rest of your life as the smaller ISPs are no longer there to offer competition. Good one. Lets see how that will work for you in 2 years time.

All I know is, their service degraded instantly yesterday, and I would not move all my branches to an inferior service.

I do not care how 'brave' they want to be. I paid THEM for a service, and I demand a service.

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



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.
Click to expand...
 
ijack said:
So your thinking is, support the company that has been raping consumers for decades, close down the smaller ISP's and then allow them to rape you for the rest of your life as the smaller ISPs are no longer there to offer competition.
Click to expand...

I think there is a bit of a problem with your comprehension skills, this should actually help the smaller ISPs...
 
Bosvark@ said:
Tracing route to www.webafrica.co.za [196.220.58.66] over a maximum of 30 hops:

2 * * * Request timed out.
3 44 ms 35 ms 46 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.163.206]
4 56 ms 89 ms 48 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 98 ms 167 ms 118 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 235 ms 199 ms 181 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
7 268 ms 294 ms 274 ms 196.22.175.214
8 317 ms 258 ms 337 ms 149.6.98.5
9 431 ms 433 ms 569 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 392 ms 408 ms 358 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
11 446 ms 370 ms 503 ms te2-1.ccr01.lon05.atlas.cogentco.com [130.117.49.94]
12 267 ms 293 ms 223 ms 149.6.2.194
13 380 ms 403 ms 365 ms 196.43.51.26
14 447 ms 479 ms 497 ms vl102.er.gw.cpt.za.wa.co.za [196.220.59.229]
15 237 ms 262 ms 259 ms vl33.cr.gw.cpt.za.wa.co.za [41.185.0.29]
16 236 ms 352 ms 360 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
17 236 ms 291 ms 243 ms wa-acc1.wadns.net [196.220.39.253]
18 292 ms 239 ms 255 ms 196.220.58.66

Trace complete.


Trace complete.
Click to expand...


I get ping times from mweb to webafrica.co.za of 11ms
Most of the traceroute is hidden.

The other direction the same
WA to Hetzner also 11ms

Leads me to conclude that
* WA is free peering with MWEB
* WA is stlll on board with MTN Business and has not cut peering links like mweb did
 
Shayd said:
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.
Click to expand...

Its obvious from the ping times that WA are free-peering with Mweb
 
Last edited:
Well done M-Web, what a good way to lose your local online gaming clients who connect to iGame and SGS :P
 
My initial reaction was hugely in favor of MWEB and, indeed, I still respect them for having a pair.

... but, when all is said and done, I still have to pay Telkom a half-grand a month for their line regardless of who my ISP is. Also, the local loop that *should* belong to the tax-payers is still controlled by the monopolies. What's changed?
 
ijack said:
So your thinking is, support the company that has been raping consumers for decades, close down the smaller ISP's and then allow them to rape you for the rest of your life as the smaller ISPs are no longer there to offer competition. Good one. Lets see how that will work for you in 2 years time.

All I know is, their service degraded instantly yesterday, and I would not move all my branches to an inferior service.

I do not care how 'brave' they want to be. I paid THEM for a service, and I demand a service.
Click to expand...

Um, how are smaller ISP being effected? I run a smaller ISP and this has no effect on my day to day runnings. Smaller ISP`s are still very competitive in this environment. Well at least our business model is.
 
This change is really congesting international traffic. Bye bye online gaming :(
 
1 <1 ms <1 ms <1 ms xxxxx.uct.ac.za [137.xxx.xxx.xxx]
2 <1 ms <1 ms <1 ms 137.xxx.xxx.xxx
3 <1 ms <1 ms <1 ms pyroteichos.uct.ac.za [137.158.248.29]
4 <1 ms <1 ms <1 ms uc-firewall.net.uct.ac.za [137.158.248.21]
5 1 ms <1 ms 1 ms vlan401.uc-edge.net.uct.ac.za [137.158.248.17]
6 1 ms 1 ms 1 ms outside-e2.uct.ac.za [137.158.253.9]
7 1 ms 1 ms 1 ms cpt1-t201-vl2744-uct.net.tenet.ac.za [155.232.7
.1]
8 2 ms 1 ms 1 ms 198.32.214.25
9 2 ms 2 ms 2 ms 196-28-178-134.adsl.mweb.co.za [196.28.178.134]

10 2 ms 2 ms 2 ms 196.41.144.36
11 2 ms 3 ms 7 ms www.mweb.co.za [196.2.63.110]
Click to expand...

Peering seems to be all fine for me. Problem? *trollface*
 
So if I pull my ethernet cable from my house to Jinx will Mweb peer with me for free?
 
TheGuy said:
So if I pull my ethernet cable from my house to Jinx will Mweb peer with me for free?
Click to expand...

First you'll need an AS, and an IP allocation, Then you need to pay your ISPA fees and the JINX Port fees.
Then, yes. You can peer for free :)

The stories about local bandwidth being free are all a myth. You just end up paying someone else. Sometimes its cheaper.
 
Let me make this simple, Webafrica does have peering with MWEB. MWEB has 2 IPC's CT and JHB. All people who are connected to the CT IPC are routing through CINX and so are not suffering WA latency but MWEB customers who are on the JHB IPC are being routed via London.

MWEB JHB -> WA - high latency
MWEB CT -> WA - low latency
WA -> MWEB - low latency

I am using Ubuntu so copying the trace route looks terrible when pasted but anybody on MWEB JHB IPC can back me up.

I have sent PM's to the MWEB guys about this and hopefully a fix can be found soon.
 
diegoa said:
Well done M-Web, what a good way to lose your local online gaming clients who connect to iGame and SGS :P
Click to expand...

Not if you want to play COD:Black Ops they won't, I wouldn't be surprised if they seriously jack up their server offering soon.

Just give me the Valve servers and I am personally happy as a pig in poo
 
Shayd said:
Let me make this simple, Webafrica does have peering with MWEB. MWEB has 2 IPC's CT and JHB. All people who are connected to the CT IPC are routing through CINX and so are not suffering WA latency but MWEB customers who are on the JHB IPC are being routed via London.

MWEB JHB -> WA - high latency
MWEB CT -> WA - low latency
WA -> MWEB - low latency

I am using Ubuntu so copying the trace route looks terrible when pasted but anybody on MWEB JHB IPC can back me up.

I have sent PM's to the MWEB guys about this and hopefully a fix can be found soon.
Click to expand...

Here is the back me up you requested :)

On MWeb 4mbps uncapped and located in Edenvale, Gauteng.
My website www.vaping101.co.za is hosted at WA.
And here are the results of a tracert

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

1 <1 ms <1 ms <1 ms Kerio [192.168.1.1]
2 2 ms 1 ms 1 ms 192.168.0.1
3 11 ms 11 ms 12 ms 41-133-120-1.dsl.mweb.co.za [41.133.120.1]
4 12 ms 12 ms 12 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
5 12 ms 12 ms 13 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
6 14 ms 15 ms 15 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
7 16 ms 15 ms 15 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
8 257 ms 253 ms 251 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
9 259 ms 259 ms 277 ms 149.6.98.17
10 260 ms 259 ms 266 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
11 259 ms 258 ms 259 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
12 259 ms 265 ms 259 ms te2-1.ccr01.lon05.atlas.cogentco.com [130.117.49.94]
13 235 ms 235 ms 234 ms 149.6.2.194
14 235 ms 239 ms 235 ms 196.43.51.26
15 249 ms 232 ms 267 ms vl101.er.gw.cpt.za.wa.co.za [196.220.59.225]
16 235 ms 233 ms 232 ms vl32.cr.gw.cpt.za.wa.co.za [41.185.0.25]
17 235 ms 249 ms 235 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
18 235 ms 234 ms 233 ms wa-acc1.wadns.net [196.220.39.253]
19 235 ms 235 ms 235 ms www.vaping101.co.za [41.185.12.30]

Funny enough, I found my site easier to work on now that it is re-routed than previously. How... I dunno. But it seems to respond better. Probably just because it is Friday and my brain is in go slow mode :)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X