MWEB - SEACOM OUTAGE UPDATE

SabreWolfy said:
From whom should it purchase this 100% SEACOM redundancy? Is there enough capacity in the country for this to even be possible?
Click to expand...

They should have included in their contract that disconnections could occur as the bulk of their data connection is through seacom which is still in implementation
i don't think any ISP provider can have a 100% redundancy plan at this moment seeing as South Africa is in a bit far off geographical location to the rest of the 1st world countrys but my main problem is in the hold they have on their clients , it is most foul play in the business world ( just my opinion )
 
PoenderHoesie said:
They should have included in their contract that disconnections could occur as the bulk of their data connection is through seacom which is still in implementation
i don't think any ISP provider can have a 100% redundancy plan at this moment seeing as South Africa is in a bit far off geographical location to the rest of the 1st world countrys but my main problem is in the hold they have on their clients , it is most foul play in the business world ( just my opinion )
Click to expand...

They (and every other ISP) have a clause in the contract which clearly states that ADSL is a best effort service. Jeez, one could swear nobody even reads the terms when check that box before submitting.
 
sorry for double post my cat went over my laptop

They (and every other ISP) have a clause in the contract which clearly states that ADSL is a best effort service. Jeez, one could swear nobody even reads the terms when check that box before submitting.
Click to expand...

ok so be it then they have stated in their contract that the ADSL connection is as best effort service like any other ISP service provider , but i wouldn't pay any ISP that will not give you your router back after 2 year contract ( unless i understand incorrectly and the router they give you is actually their property (haha that would be funny having assets in everyone's houses ))

but yes this is my last post here as my argument has nothing to do with the seacom failure anymore
 
Last edited:
PoenderHoesie said:
To all the Mweb subscribers that is unhappy with their service i would just like to add that you are getting a bad deal , i worked at a company(don't wana give names ) where i had to give support for a range of routers and 90% of the calls we received from the routers we supplied to mweb was because of the routers being locked and the epic realization that they got a 2 year contract (which can be cancelled with penalty most prob ) where they cannot unlock the routers even after the 2 year contract

Most of these clients either renewed their contract for another 2 years ( taking it in the pooper again ) or used the router for a doorstop

It reminds me of the mtn and vodacom cellphone locking issue a few years ago and both company's stopped with the cellphone locking but mweb knows they got alot of stuck customers so they keep on locking the routers

I just wonder how mweb reeks up a s**t load of cash and not implement redundancy.
Click to expand...

Who cares!! What does this have to do with the SEACOM outage?

MWEB don't force you to sign a 2 year contract and they don't force you to use their router.

The contract is if you want to receive a free router upfront, thats why you sign a 2 year contract, Telkom does the same thing. Thats how they ensure you pay them for it.
 
Last edited:
PoenderHoesie said:
To all the Mweb subscribers that is unhappy with their service i would just like to add that you are getting a bad deal , i worked at a company(don't wana give names ) where i had to give support for a range of routers and 90% of the calls we received from the routers we supplied to mweb was because of the routers being locked and the epic realization that they got a 2 year contract (which can be cancelled with penalty most prob ) where they cannot unlock the routers even after the 2 year contract

Most of these clients either renewed their contract for another 2 years ( taking it in the pooper again ) or used the router for a doorstop

It reminds me of the mtn and vodacom cellphone locking issue a few years ago and both company's stopped with the cellphone locking but mweb knows they got alot of stuck customers so they keep on locking the routers

I just wonder how mweb reeks up a s**t load of cash and not implement redundancy.
Click to expand...

You sir are an idiot.
 
You sir are an idiot.
Click to expand...
and why would you say so?
same post twice
Click to expand...
sorry fixed it just check my post again

Who cares!! What does this have to do with the SEACOM outage?

MWEB don't force you to sign a 2 year contract and they don't force you to use their router.

The contract is if you want to receive a free router upfront, thats why you sign a 2 year contract, Telkom does the same thing. Thats how they ensure you pay them for it
Click to expand...
well seeing so many people on this thread commenting about Mweb's service i just thought i'd add some extras (hope some savvy unhappy mweb clients reads my posts but i think i'm just talking to disguised mweb sales repps,techies i know because i did it too through another company(not giving names))

but yes my posts isn't much of seacom's failure anymore so i won't post anymore unless it's because of seacom
 
People are very quick to forget how MWEB shook up the market with the first affordable uncapped ADSL. Yes it was a bold,risky move and obviously the only way to make it economically viable was a heavy reliance on SEACOM. I don't think they could have predicted an outage of this scale. Event still, thanks to them making the move, we will be reaping the benefits long after we have forgotten this problem. Don't get me wrong, I too am frustrated and I too believe there should be more redundancy, but the simple fact is if they had to build in redundancy, we would not have the cheap ADSL products we have now.
 
Nips said:
Don't get me wrong, I too am frustrated and I too believe there should be more redundancy, but the simple fact is if they had to build in redundancy, we would not have the cheap ADSL products we have now.
Click to expand...

No doubt it has been frustrating but thanks to the outage I have actually had time to see my kids again. Just joking!!!
I think that most people on this forum agree with your sentiments - just look at the potential rand cost per Gig compared to 6 months ago.Unfortunately there are a few twats who don't see the bigger picture,in particular 2 come to mind but fortunately I have them on my ignore list and wont see their comments after I post this(unless someone quotes them:D)
 
God - it breeds - how unfortunate.

Seems some idiots don't realise that uncapped isn't a charge per GB.
 
PoenderHoesie said:
They should have included in their contract that disconnections could occur as the bulk of their data connection is through seacom which is still in implementation
i don't think any ISP provider can have a 100% redundancy plan at this moment seeing as South Africa is in a bit far off geographical location to the rest of the 1st world countrys but my main problem is in the hold they have on their clients , it is most foul play in the business world ( just my opinion )
Click to expand...

All of this is covered in the T&C.
 
Ever since I returned from a client today at 14:30 I've had a perfect connection via MWEB. Fast browsing, all sites I tried working. IRC and SSH perfect. So it seems for me the link is back up fully. Using my @dslmweb.co.za ID. I tried a quick 300MB torrent and that worked for me as well.

Code: 
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 40 byte packets
 1  <REMOVED>
 2  * * *
 3  tengig-0-0-0-107.vic-ipc-1.mweb.co.za (196.22.169.158) [AS10474]  41.065 ms  41.090 ms  41.088 ms
 4  vl-92.vic-hscore-2.mweb.co.za (196.22.189.3) [AS10474/AS11908]  41.084 ms  41.091 ms  43.074 ms
 5  tengig-0-0-0-0-12.vic-up-2.mweb.co.za (196.22.169.242) [AS10474]  101.007 ms  101.015 ms  101.968 ms
 6  * * *
 7  * 125.17.16.113 (125.17.16.113) [AS9498]  176.145 ms  178.930 ms
 8  203.101.100.210 (203.101.100.210) [AS9498/AS7617]  182.228 ms  184.022 ms  189.859 ms
 9  72.14.216.229 (72.14.216.229) [AS15169]  188.091 ms  174.190 ms  177.911 ms
10  66.249.94.168 (66.249.94.168) [AS15169]  178.050 ms  174.815 ms  174.846 ms
11  209.85.241.86 (209.85.241.86) [AS15169]  321.242 ms  321.915 ms 66.249.94.38 (66.249.94.38) [AS15169]  319.154 ms
12  209.85.250.255 (209.85.250.255) [AS15169]  321.746 ms 209.85.250.237 (209.85.250.237) [AS15169]  282.649 ms 209.85.242.125 (209.85.242.125) [AS15169]  280.073 ms
13  209.85.243.142 (209.85.243.142) [AS15169]  282.037 ms 209.85.249.130 (209.85.249.130) [AS15169]  332.685 ms  330.308 ms
14  74.125.206.138 (74.125.206.138) [AS15169]  217.782 ms 74.125.206.10 (74.125.206.10) [AS15169]  217.056 ms 74.125.206.138 (74.125.206.138) [AS15169]  227.960 ms
15  google-public-dns-a.google.com (8.8.8.8) [AS15169]  216.076 ms  218.147 ms  219.801 ms
 
Last edited:
Can anyone say if the @mweb.co.za fix for international will be billed for outside of ones package?

edit: Nevermind, seems @dslmweb is working again
 
Last edited:
Valerion said:
Ever since I returned from a client today at 14:30 I've had a perfect connection via MWEB. Fast browsing, all sites I tried working. IRC and SSH perfect. So it seems for me the link is back up fully. Using my @dslmweb.co.za ID. I tried a quick 300MB torrent and that worked for me as well.

Code: 
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 40 byte packets
15  google-public-dns-a.google.com (8.8.8.8) [AS15169]  216.076 ms  218.147 ms  219.801 ms
Click to expand...

That tracert looks quite fast. I think it's going to a cache somewhere in the East (not all the way to the USA).

To test I rebooted (I've been on SAIX all day), and found that MWeb tracert to Europe is very slow!

Code: 
Tracing route to newswww.bbc.net.uk [212.58.244.57]
over a maximum of 30 hops:

   1   <10 ms   <10 ms   <10 ms  home.gateway [192.168.1.254]
   2     8 ms     8 ms     8 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
   3    28 ms    29 ms    29 ms  tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.163.218]
   4    29 ms    30 ms    29 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
   5    30 ms    32 ms    33 ms  tengig-0-0-0-0-12.vic-up-2.mweb.co.za [196.22.169.242]
   6    31 ms    32 ms    32 ms  tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
   7   347 ms   369 ms   395 ms  125.17.16.113
   8   370 ms   383 ms   395 ms  125.21.167.70
   9   499 ms   461 ms   553 ms  so-5-3-0-dcr2.par.cw.net [195.10.54.77]
  10   462 ms   487 ms   524 ms  xe-4-3-0-xcr1.par.cw.net [195.2.9.233]
  11   592 ms   582 ms   625 ms  xe-0-0-0-xcr1.fra.cw.net [195.2.9.213]
  12   481 ms   485 ms   505 ms  rt-decix.fft.bbc.co.uk [80.81.192.59]
  13   583 ms   532 ms   505 ms  ge0-1-10.rt0.tcman.bbc.co.uk [212.58.239.245]
  14   555 ms   592 ms   593 ms  212.58.238.37
  15   560 ms   550 ms   561 ms  212.58.239.58
  16   519 ms   460 ms   435 ms  212.58.251.44
  17   593 ms   583 ms   524 ms  newswww.bbc.net.uk [212.58.244.57]

Trace complete.
 
Gordon_R said:
That tracert looks quite fast. I think it's going to a cache somewhere in the East (not all the way to the USA).

To test I rebooted (I've been on SAIX all day), and found that MWeb tracert to Europe is very slow!
Click to expand...

In my previous traceroute, both hops 7 and 8 are inside India, and the rest is in Google's own network. I suspect those servers are hosted in India, yeah.

Here's one to Seattle in the US, via India, Singapore and Tokyo.

Code: 
traceroute to www.speedtest.net (69.17.117.207), 30 hops max, 40 byte packets
 1  <REMOVED>
 2  * * *
 3  tengig-0-0-0-107.vic-ipc-1.mweb.co.za (196.22.169.158) [AS10474]  46.018 ms  47.820 ms  50.723 ms
 4  vl-92.vic-hscore-1.mweb.co.za (196.22.189.2) [AS10474/AS11908]  52.819 ms  56.102 ms  57.092 ms
 5  tengig-0-0-0-0-11.vic-up-2.mweb.co.za (196.22.169.226) [AS10474]  62.340 ms  63.225 ms  68.417 ms
 6  tengig-0-3-1-0.mid-1.mweb.co.za (196.22.169.211) [AS10474]  69.411 ms  16.365 ms  17.358 ms
 7  125.17.16.113 (125.17.16.113) [AS9498]  328.908 ms  330.909 ms  332.878 ms
 8  AES-Static-081.36.144.59.airtel.in (59.144.36.81) [AS9498]  364.249 ms  366.090 ms  368.838 ms
 9  if-11-0-0.core1.SVQ-Singapore.as6453.net (120.29.214.5) [*]  372.894 ms  374.761 ms  376.089 ms
10  Vlan1107.icore1.SVQ-Singapore.as6453.net (120.29.214.2) [*]  385.938 ms  386.889 ms  370.687 ms
11  Vlan1717.icore1.SVW-Singapore.as6453.net (116.0.71.13) [*]  376.649 ms  326.863 ms  325.177 ms
12  Vlan1954.icore1.TV2-Tokyo.as6453.net (116.0.88.21) [*]  388.987 ms  392.159 ms  404.636 ms
13  if-10-0-0-1831.core1.TV2-Tokyo.as6453.net (209.58.61.93) [AS18895]  393.932 ms  391.742 ms  391.920 ms
14  if-0-0-0-1906.core2.S00-Seattle.as6453.net (66.110.25.17) [AS6453]  556.722 ms  546.900 ms  547.115 ms
15  if-7-0-0.core1.S00-Seattle.as6453.net (207.45.206.13) [AS6453]  546.953 ms  540.601 ms  509.856 ms
16  ix-4-0-2-143.core1.S00-Seattle.as6453.net (66.110.64.10) [AS6453]  543.832 ms  567.852 ms  541.068 ms
17  152.ge-1-3-0.sr2.sea5.speakeasy.net (69.17.82.54) [AS23504]  548.208 ms  549.061 ms  549.889 ms
18  www.ookla.com (69.17.117.207) [AS23504/AS13790]  552.851 ms  495.653 ms  497.946 ms
 
Hi guys
Is anyone here able to play MMO's on MWEB currently? Is that counted as the heavily shaped P2P???
 
Valerion said:
In my previous traceroute, both hops 7 and 8 are inside India, and the rest is in Google's own network. I suspect those servers are hosted in India, yeah.

Here's one to Seattle in the US, via India, Singapore and Tokyo.

Code: 
traceroute to www.speedtest.net (69.17.117.207), 30 hops max, 40 byte packets
18  www.ookla.com (69.17.117.207) [AS23504/AS13790]  552.851 ms  495.653 ms  497.946 ms
Click to expand...

Hey, this reminds me of the time SEA-ME-WE-4 went down, and I recorded a tracert with 29 hops via the USA to Europe!

At least SEA-ME-WE is working this time (see CW.net on hops 9-12 in my tracert above).
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X