MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
My net is completely dead in CPT, having to write this on my phone using 3G. Seems no servers can be resolved, maybe a DNS issue.
 
Blackhand said:
My net is completely dead in CPT, having to write this on my phone using 3G. Seems no servers can be resolved, maybe a DNS issue.
Click to expand...

Read my post above. Also, if you have facebook -- add Mweb Guy as a friend so that you are kept up to date on upcoming changes/downtown etc.
 
Yeah, I know they were doing maintenance in CPT, but traffic was supposed to be rerouted and higher latency.
 
GEEZ my interwebs is DEAD SLOW this morning!!!! <sigh> One more month of this bollocks and it ends. Isn't an 'upgrade' meant to speed things up?!?
 
DOnt know why u suffering, my P2P was getting 500KB until 8am now its sitting at 250KB constant.
 
Last edited:
hmm ok so what did the upgrade improve? Here in windy old CTown things are not looking so bright right now. NNTP running at 11kBps, but I suppose it's better than 5kBps.
 
MWEB Operations said:
We are undergoing additional network improvements to prepare for implementation of our SAT-3 link in Cape Town. This will give us even more international capacity and further redundancy on our network.

In order to carry out this change, some preparation work needs to take place tomorrow night. Our Cape Town IPC links will have to be taken offline for a short period. We will be routing all our Cape Town IPC traffic to Johannesburg at midnight, which will last for approximately 3 hours.

We will also use this opportunity to activate additional caching servers in Cape Town, which will reduce the traffic on our north-south links and further optimize network performance.
Click to expand...

I was half-expecting my international traffic in Cape Town to go via SAT-3 this morning, but so far I can't see any difference in routing. (I can't see any difference in caching either.) I guess these infrastructure changes will only bear fruit further down the line...

Edit: I'm sure its no secret that MWeb will sign up for WACS bandwidth in Q2 2011:
http://mybroadband.co.za/news/telec...-fibre-cable-deployment-progressing-well.html
 
Last edited:
I was away for a week so I missed most of the past few pages in this thread, and wasn't aware of the connection limit. Even so, my torrents were running at 150kB/s yesterday afternoon/last night after I got home, and then climbed to 300-350kB/s. I will have to re-test with the uTorrent settings earlier in the thread.

I did notice that with my torrents running MU was barely downloading, and when I switched uTorrent off it rocketed up. Probably due to the connection limit.
 
Gordon_R said:
I was half-expecting my international traffic in Cape Town to go via SAT-3 this morning, but so far I can't see any difference in routing. (I can't see any difference in caching either.) I guess these infrastructure changes will only bear fruit further down the line...

Edit: I'm sure its no secret that MWeb will sign up for WACS bandwidth in Q2 2011:
http://mybroadband.co.za/news/telec...-fibre-cable-deployment-progressing-well.html
Click to expand...

Hi Gordon and all others with this question. The only change from last nights work which may have an effect on the customer experience was the Cape Town caching servers that were brought online, although I'm not sure if they've been taken live yet. The other work was done to prepare the network for the SAT-3 link when it arrives. I don't currently have a date for exactly when that's taking place.
 
Any reason why I can't stream on my 4mb account? Everything buffers incredibly slowly
 
Will@MWEB said:
Hi Gordon and all others with this question. The only change from last nights work which may have an effect on the customer experience was the Cape Town caching servers that were brought online, although I'm not sure if they've been taken live yet.
Click to expand...
They are very much alive and caching broken downloads as far as they go.

I am re-downloading each file 5 times just to verify it fails after the same byte count, then I email the details to your technical support address.
It sure is wasting a lot of bandwidth but if you are too stupid to install proper caching server you should expect this kind of behavior.

Edit : it is also very easy to spot downloads from the cache server - they are usually at about 50kb/s while downloads straight from the source is at 150kb/s

Fix them or take them offline. Simple as that.
 
Last edited:
NNTP hasn't gone faster than 70Kbps since Fri night :( Really miserable.

Update: Now its completely dead - as in NNTP 0Kbps
 
Last edited:
@Rouxenator can you please provide examples of the files you are having this problem with so that I can have this investigated.
 
Sure :

Link URL : http://www.filesonic.com/file/r000216945/30167495/AlexD
Download URL : http://s9.filesonic.com/download/30...268d/a8a294e9a026068afd38ced8867819307912a31d
Filename : AlexD - Traumreise.avi.part2.rar
Fail byte count : 260,131,360
Expected byte count : 307,741,128

Link URL : http://www.filesonic.com/file/r000216945/30168195/AlexD
Download URL : http://s98.filesonic.com/download/3...268d/cb3093b131984cf8c844bd6b5c85f222a30b8578
Filename : AlexD - Wechselspiele.avi.part2.rar
Fail byte count : 16,826,849
Expected byte count : 318,730,454

Link URL : http://www.filesonic.com/file/r000216945/1011750/AlexD_-_Qual_der_Wahl.part2.rar
Download URL : http://s9.filesonic.com/download/10...268d/b2fa946384befa67712118acf331f474aaefcc25
Filename : AlexD_-_Qual_der_Wahl.part2.rar
Fail byte count : 74,738,375
Expected byte count : 264,241,152

I'll add more as they come along. I did get some of them by using my old Vodacom HSDPA modem - no problems at all. It has 4GB that I should blow before month end and it is just pure bliss to download at 500kb/s with no issues. Kinda makes me wonder why M-Web can't be like that...
 
Anyone else experiencing issues with Mweb atm? For instance, I can't access http://www.prophecy.co.za/ at this moment, but it is working 100% on my Afrihost account.

Traceroute using Mweb 384kbps uncapped from Stellenbosch:
Code: 
Tracing route to www.prophecy.co.za [196.37.28.75]
over a maximum of 30 hops:

  1     8 ms     2 ms     2 ms  rb750.tuis [192.168.90.1]
  2     5 ms     2 ms     2 ms  d-link-adsl-router.tuis [192.168.89.1]
  3    89 ms    25 ms    24 ms  41-132-44-1.dsl.mweb.co.za [41.132.44.1]
  4    31 ms    28 ms    27 ms  196-28-178-166.adsl.mweb.co.za [196.28.178.166]
  5    28 ms    28 ms    28 ms  196-28-179-11.adsl.mweb.co.za [196.28.179.11]
  6    29 ms    27 ms    31 ms  196-28-178-66.adsl.mweb.co.za [196.28.178.66]
  7    27 ms    29 ms    33 ms  cte-dist2.vwol.net [196.41.144.22]
  8     *        *        *     Request timed out.
  9  cte-dist2.vwol.net [196.41.144.22]  reports: Destination host unreachable.

And this is how it looks with Afrihost:
Code: 
Tracing route to www.prophecy.co.za [196.37.28.75]
over a maximum of 30 hops:

  1     2 ms     2 ms     1 ms  rb750.tuis [192.168.90.1]
  2    26 ms    29 ms    26 ms  196-210-150-1.dynamic.isadsl.co.za [196.210.150.1]
  3    53 ms    51 ms    53 ms  196.38.73.113
  4    48 ms    48 ms    47 ms  cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
  5    51 ms    52 ms    52 ms  csw3-rba-gi8-4.ip.isnet.net [196.26.0.248]
  6    50 ms    50 ms    50 ms  sw-osfw-shared-1-rba-vl515.ip.isnet.net [196.14.136.10]
  7    56 ms    52 ms    52 ms  196.14.160.146
  8    52 ms    52 ms    54 ms  prophecy.dedicated.co.za [196.37.28.75]
 
Last edited:
Guess its another big fail from their new cache servers...

Mweb :
Code: 
Tracing route to www.prophecy.co.za [196.37.28.75]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  D-Link.DSL2740U [192.168.1.1]
  2    13 ms    12 ms    12 ms  41-132-38-1.dsl.mweb.co.za [41.132.38.1]
  3    42 ms    20 ms    14 ms  196-28-178-178.adsl.mweb.co.za [196.28.178.178]
  4    36 ms    16 ms    16 ms  196-28-179-11.adsl.mweb.co.za [196.28.179.11]
  5    13 ms    12 ms    13 ms  196-28-178-66.adsl.mweb.co.za [196.28.178.66]
  6    15 ms    19 ms    14 ms  cte-dist2.vwol.net [196.41.144.22]
  7     *        *     cte-dist2.vwol.net [196.41.144.22]  reports: Destination host unreachable.

Trace complete.

VodaCom
Code: 
Tracing route to www.prophecy.co.za [196.37.28.75]
over a maximum of 30 hops:

  1    69 ms    68 ms    88 ms  10.17.14.11
  2   118 ms   124 ms    68 ms  10.113.139.158
  3    68 ms    78 ms    78 ms  vc-196-207-42-18.3g.vodacom.co.za [196.207.42.18]
  4    76 ms    69 ms    66 ms  192.168.108.105
  5    88 ms   125 ms   119 ms  vc-196-207-40-209.3g.vodacom.co.za [196.207.40.209]
  6    97 ms    78 ms    68 ms  vc-196-207-40-211.3g.vodacom.co.za [196.207.40.211]
  7   120 ms    68 ms   113 ms  41.0.196.1
  8   116 ms   162 ms   101 ms  wbs-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.247.205]
  9    77 ms   128 ms   115 ms  196.43.11.234
 10    98 ms    99 ms    76 ms  196.43.25.206
 11   120 ms   105 ms    78 ms  196.25.247.26
 12    78 ms    76 ms    78 ms  core1a-ctn-gi0-1.ip.isnet.net [168.209.2.5]
 13   133 ms   100 ms   188 ms  core1a-pkl-gi0-0-3-1-306.ip.isnet.net [168.209.100.77]
 14    92 ms    92 ms    98 ms  csw3-rba-gi8-4.ip.isnet.net [196.26.0.248]
 15   123 ms   129 ms   117 ms  sw-osfw-shared-1-rba-vl515.ip.isnet.net [196.14.136.10]
 16    88 ms   128 ms    88 ms  196.14.160.146
 17    99 ms   118 ms   108 ms  prophecy.dedicated.co.za [196.37.28.75]

Trace complete.

Edit : I think I spotted the problem :D
cte-dist2.vwol.net [196.41.144.22] reports: Destination host unreachable
 
This is how it's supposed to look from Mweb (got this from a friend in Jhb):
Code: 
1 2 ms <1 ms <1 ms my.router [192.168.1.1]
2 27 ms 22 ms 23 ms 41-132-56-1.dsl.mweb.co.za [41.132.56.1]
3 25 ms 26 ms 26 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
4 24 ms 26 ms 27 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 29 ms 27 ms 26 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 25 ms 27 ms 24 ms g-0-3-vic-jinx-2.mweb.co.za [196.22.163.1]
7 105 ms 135 ms 49 ms is.jinx.net.za [198.32.142.10]
8 53 ms 71 ms 56 ms csw3-rba-gi5-2.ip.isnet.net [168.209.1.173]
9 * 28 ms 58 ms sw-osfw-shared-1-rba-vl515.ip.isnet.net [196.14.136.10]
10 30 ms 29 ms 30 ms 196.14.160.146
11 * 27 ms 74 ms www.prophecy.co.za [196.37.28.75]

or from Mweb Business uncapped (from my office in Technopark, Stellenbosch):
Code: 
                                       Packets               Pings
 Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 172.30.2.1                        0.0%     5    1.0   1.6   0.9   2.6   0.8
 2. 172.30.30.1                       0.0%     5    1.7   2.2   1.6   3.7   0.9
 3. 41-134-xx-xxx.dsl.mweb.co.za      0.0%     4    2.4   2.2   1.8   2.9   0.5
 4. tengig-0-0-0.vic-lns-1.mweb.co.z  0.0%     4   41.1  41.3  40.9  41.6   0.3
 5. vl-92.vic-hscore-2.mweb.co.za     0.0%     4   40.8  41.6  40.8  42.9   0.9
 6. tengig-0-0-0-0-12.vic-up-1.mweb.  0.0%     4   42.9  44.7  42.9  47.4   2.2
 7. g-0-3-vic-jinx-2.mweb.co.za       0.0%     4   42.4  42.4  40.4  44.4   1.6
 8. is.jinx.net.za                    0.0%     4   40.6  43.7  40.6  46.9   3.2
 9. csw3-rba-gi8-4.ip.isnet.net       0.0%     4   40.2  42.3  40.2  46.9   3.1
10. sw-osfw-shared-1-rba-vl515.ip.is  0.0%     4   42.0  42.2  41.2  43.5   1.0
11. 196.14.160.146                    0.0%     4   42.2  42.4  41.9  43.0   0.4
12. prophecy.dedicated.co.za          0.0%     4   41.9  42.0  41.3  43.4   1.0

A friend of mine told me about 'mtr' linux app (see above output) to do trace routes / ping tests and it is really fantastic!
 
Pada said:
This is how it's supposed to look from Mweb (got this from a friend in Jhb):
Code: 
1 2 ms <1 ms <1 ms my.router [192.168.1.1]
2 27 ms 22 ms 23 ms 41-132-56-1.dsl.mweb.co.za [41.132.56.1]
3 25 ms 26 ms 26 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
4 24 ms 26 ms 27 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 29 ms 27 ms 26 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 25 ms 27 ms 24 ms g-0-3-vic-jinx-2.mweb.co.za [196.22.163.1]
7 105 ms 135 ms 49 ms is.jinx.net.za [198.32.142.10]
8 53 ms 71 ms 56 ms csw3-rba-gi5-2.ip.isnet.net [168.209.1.173]
9 * 28 ms 58 ms sw-osfw-shared-1-rba-vl515.ip.isnet.net [196.14.136.10]
10 30 ms 29 ms 30 ms 196.14.160.146
11 * 27 ms 74 ms www.prophecy.co.za [196.37.28.75]

or from Mweb Business uncapped (from my office in Technopark, Stellenbosch):
Code: 
                                       Packets               Pings
 Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 172.30.2.1                        0.0%     5    1.0   1.6   0.9   2.6   0.8
 2. 172.30.30.1                       0.0%     5    1.7   2.2   1.6   3.7   0.9
 3. 41-134-xx-xxx.dsl.mweb.co.za      0.0%     4    2.4   2.2   1.8   2.9   0.5
 4. tengig-0-0-0.vic-lns-1.mweb.co.z  0.0%     4   41.1  41.3  40.9  41.6   0.3
 5. vl-92.vic-hscore-2.mweb.co.za     0.0%     4   40.8  41.6  40.8  42.9   0.9
 6. tengig-0-0-0-0-12.vic-up-1.mweb.  0.0%     4   42.9  44.7  42.9  47.4   2.2
 7. g-0-3-vic-jinx-2.mweb.co.za       0.0%     4   42.4  42.4  40.4  44.4   1.6
 8. is.jinx.net.za                    0.0%     4   40.6  43.7  40.6  46.9   3.2
 9. csw3-rba-gi8-4.ip.isnet.net       0.0%     4   40.2  42.3  40.2  46.9   3.1
10. sw-osfw-shared-1-rba-vl515.ip.is  0.0%     4   42.0  42.2  41.2  43.5   1.0
11. 196.14.160.146                    0.0%     4   42.2  42.4  41.9  43.0   0.4
12. prophecy.dedicated.co.za          0.0%     4   41.9  42.0  41.3  43.4   1.0

A friend of mine told me about 'mtr' linux app (see above output) to do trace routes / ping tests and it is really fantastic!
Click to expand...

Thanks guys, I have added this info to the escalation.
 
MWEB Operations said:
Thanks guys, I have added this info to the escalation.
Click to expand...

What is the status on the caching bad copies of files? I was downloading 4 files now when your link when down so I am pretty sure once I restart them they will keep on failing because of your dodgy cache servers.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X