MWEB Uncapped ADSL Feedback - Part 2

[Mephisto_Helix]

Ye I'm sending a mail as requested the other day. I really hope this gets sorted because for it to happen every other day is just not good enough for me.

C:\Users\Andre>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:

1 8 ms 7 ms 8 ms 41-133-68-1.dsl.mweb.co.za [41.133.68.1]
2 9 ms 9 ms 9 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
3 9 ms 9 ms 8 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
4 266 ms 267 ms 266 ms 176.67.177.131
5 270 ms 264 ms 269 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
3]
6 269 ms 264 ms 273 ms vl-3502-ve-116.csw1.London1.Level3.net [4.69.166
.133]
7 271 ms 264 ms 264 ms ae-1-51.edge4.London1.Level3.net [4.69.139.74]
8 265 ms 272 ms 264 ms BBC-TECHNOL.edge4.London1.Level3.net [212.113.14
.222]
9 * * * Request timed out.
10 270 ms 271 ms 272 ms ae1.er01.thdow.bbc.co.uk [132.185.254.18]
11 271 ms 266 ms 265 ms 132.185.255.92
12 368 ms 359 ms 300 ms 212.58.241.131

Trace complete.

C:\Users\Andre>ping mybroadband.co.za

Pinging mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=126ms TTL=49
Reply from 41.203.21.137: bytes=32 time=120ms TTL=49
Reply from 41.203.21.137: bytes=32 time=135ms TTL=49
Reply from 41.203.21.137: bytes=32 time=139ms TTL=49

Ping statistics for 41.203.21.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 120ms, Maximum = 139ms, Average = 130ms

C:\Users\Andre>tracert mybroadband.co.za

Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

1 7 ms 8 ms 8 ms 41-133-68-1.dsl.mweb.co.za [41.133.68.1]
2 9 ms 9 ms 9 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
3 10 ms 9 ms 9 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
4 32 ms 32 ms 32 ms tengig0-0-0.cpt-pr-2.mweb.co.za [197.84.4.165]
5 33 ms 33 ms 33 ms mtn-pp.cpt-cinx-2.mweb.co.za [196.28.178.142]
6 33 ms 34 ms 33 ms 196.44.0.75
7 129 ms 131 ms 127 ms rb-cr-1.za--ct-cr-1.za.mtnns.net [196.44.31.128]

8 146 ms 151 ms 152 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
9 135 ms 139 ms 142 ms ge4-0-0.gw17.jnb6.za.mtnbusiness.net [196.30.1.3
7]
10 135 ms 134 ms 129 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
11 135 ms 128 ms 134 ms core-router1.jnb2.host-h.net [196.30.213.108]
12 134 ms 140 ms 138 ms core-access-switch1-vlan1001.jnb.host-h.net [41.
72.136.53]
13 156 ms 148 ms 142 ms mybroadband.co.za [41.203.21.137]

W.T.H :wtf:

 

[SHVAK]

I have a serious issue with steam downloads over MWEB uncapped. They are intermittent at best and are seriously being throttled, Which is strange as Mweb bloody claims to host the site in SA. This is not P2P traffic and should not be subject to throttling?

 

[Mephisto_Helix]

Gotta be a general issue or something, Mweb is 80 ping above normal and even AH is 30 above normal. So AH not as bad as Mweb but still being affected.

 

[Lycanthrope]

Anyone else having issues with international sites?

tracert gamespot.com

Tracing route to gamespot.com [107.23.58.229]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    14 ms    14 ms    14 ms  41-133-64-1.dsl.mweb.co.za [41.133.64.1]
  3    31 ms    32 ms    36 ms  te1-1-0.502.cpt-ipc-1.mweb.co.za [196.28.178.166
]
  4    32 ms    32 ms    31 ms  197-84-3-2.cpt.mweb.co.za [197.84.3.2]
  5     *        *      204 ms  TenGigE0-7-0-3.12.cpt-p-1.mweb.co.za [196.28.178
.113]
  6   182 ms     *        *     197-84-4-193.cpt.mweb.co.za [197.84.4.193]
  7     *      173 ms   173 ms  176.67.177.131
  8   288 ms   274 ms   274 ms  195.50.124.133
  9   263 ms   270 ms   265 ms  vl-3604-ve-228.csw2.London1.Level3.net [4.69.166
.157]
 10     *      269 ms   276 ms  ae-59-224.ebr2.London1.Level3.net [4.69.153.141]

 11   350 ms   344 ms   344 ms  ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]

 12   344 ms   338 ms   349 ms  4.69.148.50
 13   343 ms   348 ms   342 ms  ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221
]
 14     *      329 ms   347 ms  ae-72-72.csw2.Washington1.Level3.net [4.69.134.1
50]
 15   355 ms     *      348 ms  ae-2-70.edge2.Washington1.Level3.net [4.69.149.7
8]
 16     *        *      348 ms  AMAZON.COM.edge2.Washington1.Level3.net [4.79.22
.86]
 17   346 ms   339 ms   339 ms  72.21.220.151
 18   330 ms   325 ms   328 ms  72.21.222.157
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22   350 ms   350 ms   350 ms  ec2-107-23-58-229.compute-1.amazonaws.com [107.2
3.58.229]

Trace complete.

 

[MWEBHelp]

I have a serious issue with steam downloads over MWEB uncapped. They are intermittent at best and are seriously being throttled, Which is strange as Mweb bloody claims to host the site in SA. This is not P2P traffic and should not be subject to throttling?

Hi SHVAK

We are not experiencing any trouble with steam downloads at the moment.

Send me your MWEB details so I can investigate.

 

[Krypty]

Seems something just happened on the backbone. My link is also bouncing at this stage. Seems to be internationally isolated

 

[johanopperman]

Same here. International just slowed down to an almost complete halt. Probably last 5 minutes or so.

Pretoria North/Akasia area.

 

[MWEBHelp]

Same here. International just slowed down to an almost complete halt. Probably last 5 minutes or so.

Pretoria North/Akasia area.

Send me your MWEB details and a trace route to an international site.

 

[nelis]

yes seems a bit slo. just a tiny bit faster than a 56k modem. Also in Pretoria

 

[Lycanthrope]

Seems okay again... For now

*relaxes*

I was having palpitations there, visions of another backbone failure flashing before my eyes.

DREAD, I TELLS YA!

 

[Mephisto_Helix]

Someone let me know when it's safe to switch back to Mweb, I can't deal with the slowness and crap .......

 

[MWEBHelp]

Hi Everyone

Just to let you know that we are currently experiencing a partial loss of international capacity.
Due to a cable break near Marsielles which is affecting Seacom.

We are currently operating on backup capacity, so you may be experiencing some slowness on international sites and downloads.
Particularly lower priority traffic such as P2P downloads will be the most affected.

We will update you as soon as we have an ETA on the repair.

 

[Mephisto_Helix]

It's ze French, those bastiche!

 

[TheRedBar0n]

I don't know how on earth this is possible! We have a 4mb uncapped business account with Mweb, located in Bellville and on speedtest the ping was just over 1700ms.... And download of 0.03 to Cape Town.

Here is another result:
http://www.speedtest.net/result/2201146542.png

Poor man!

Please help @Mweb Guy!

Right, issue resolve and lines are running 100%! Was a firewall misconfiguration from our service provider. I would like to thank Mweb for their excellent business support and followups on the matter!

 

[MWEBHelp]

Right, issue resolve and lines are running 100%! Was a firewall misconfiguration from our service provider. I would like to thank Mweb for their excellent business support and followups on the matter!

Thank you for the feedback.

 

[Will@MWEB]

...and we're clear Both Seacom circuits back up and engineers monitoring.

 

[Mike Hoxbig]

NNTP still going at 60 KB/s on a 2 meg line, used to be better before

 

[hambone]

Particularly lower priority traffic such as P2P downloads will be the most affected.

Don't forget to open the flood gates

 

[BioWolfZA]

I would just like to know, does the up and running in 15 minutes or less rule only apply to office hours?

 

[Franna]

Hope Mweb can acquire some fully redundant bandwidth on WACS for when Seacom goes down every second week.