Mweb Latency Problems

G

GoofySmurf

Expert Member
Joined
Dec 23, 2009
Messages
1,254
Reaction score
325
Heya

Just wondering if anyone else is experiencing problems with their uncapped Mweb ADSL account.


ping games.saix.net

Pinging games.saix.net [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=528ms TTL=241
Reply from 196.43.22.222: bytes=32 time=447ms TTL=241
Reply from 196.43.22.222: bytes=32 time=461ms TTL=241
Reply from 196.43.22.222: bytes=32 time=489ms TTL=241

ping www.myadsl.co.za

Pinging www.myadsl.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=550ms TTL=37
Reply from 41.203.21.137: bytes=32 time=551ms TTL=37
Reply from 41.203.21.137: bytes=32 time=586ms TTL=37
Reply from 41.203.21.137: bytes=32 time=550ms TTL=37

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


ping www.google.com

Pinging www.l.google.com [64.233.179.104] with 32 bytes of data:
Reply from 64.233.179.104: bytes=32 time=414ms TTL=50
Reply from 64.233.179.104: bytes=32 time=580ms TTL=50
Reply from 64.233.179.104: bytes=32 time=426ms TTL=50
Reply from 64.233.179.104: bytes=32 time=554ms TTL=50


tracert -d games.saix.net

Tracing route to games.saix.net [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 30 ms 31 ms 30 ms 196.22.169.134
4 104 ms 31 ms 43 ms 196.22.189.3
5 232 ms 299 ms 300 ms 196.22.169.241
6 200 ms 150 ms 149 ms 196.22.169.219
7 500 ms 450 ms 450 ms 196.22.163.230
8 501 ms 450 ms 450 ms 130.117.136.1
9 501 ms 450 ms 450 ms 130.117.50.138
10 518 ms 466 ms 459 ms 130.117.1.18
11 550 ms 469 ms 468 ms 130.117.2.17
12 416 ms 469 ms 460 ms 130.117.49.106
13 376 ms 459 ms 459 ms 149.6.2.194
14 680 ms 616 ms 610 ms 196.43.8.146
15 680 ms 445 ms 445 ms 196.43.23.6
16 588 ms 470 ms 452 ms 196.43.23.34
17 691 ms 645 ms 645 ms 196.43.22.222

Trace complete.

tracert -d www.myadsl.co.za

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.0.1
2 * * * Request timed out.
3 41 ms 31 ms 30 ms 196.22.169.134
4 232 ms 149 ms 149 ms 196.22.189.3
5 56 ms 53 ms 62 ms 196.22.169.241
6 34 ms 32 ms 34 ms 196.22.169.219
7 384 ms 450 ms 450 ms 196.22.163.230
8 257 ms 257 ms 257 ms 79.141.38.37
9 261 ms 260 ms 264 ms 64.125.27.226
10 341 ms 258 ms 334 ms 64.125.27.158
11 527 ms 286 ms 285 ms 213.152.230.91
12 587 ms 585 ms 551 ms 196.30.1.22
13 550 ms 599 ms 550 ms 196.30.156.136
14 574 ms 613 ms 552 ms 196.30.213.108
15 574 ms 561 ms 553 ms 196.7.216.173
16 622 ms 609 ms 597 ms 41.203.21.137

Trace complete.
 
Yip, it seems to be all MWEB ADSL accounts. I get a similar tracert.

Looks like we all getting routed internationally and then back to SA. :confused:

Think this might have to do with their new IPC capacity or something.
This press release mentions something about it. http://www.mweb.com/media_press_current_releases.aspx

Would have been nice if they had informed us.
 
All local traffic routing through London?

Have the same issue. It seems all traffic is being routed internationally. There is a network notice so they are presumably working on it.


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

1 1 ms <1 ms <1 ms 10.7.12.1
2 14 ms 14 ms 13 ms 41-132-2-1.dsl.mweb.co.za [41.132.2.1]
3 24 ms 25 ms 24 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.163.206]
4 24 ms 24 ms 24 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 57 ms 51 ms 55 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 28 ms 26 ms 29 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
7 251 ms 251 ms 250 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 251 ms 251 ms 251 ms 79.141.38.37.available.above.net [79.141.38.37]
9 252 ms 252 ms 251 ms so-0-0-0.mpr1.lhr3.uk.above.net [64.125.27.226]
10 251 ms 270 ms 251 ms xe-1-1-0.mpr2.lhr3.uk.above.net [64.125.27.158]
11 250 ms 249 ms 250 ms 213-152-230-91.mtnns.net [213.152.230.91]
12 544 ms 545 ms 544 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
13 544 ms 543 ms 543 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
14 544 ms 543 ms 544 ms 196.30.213.108
15 544 ms 545 ms 544 ms firewall1.jnb2.host-h.net [196.7.216.173]
16 545 ms 545 ms 545 ms mybroadband.co.za [41.203.21.137]

Trace complete.
 
This isn't the first time that Mweb is routing all the international traffic via London.

This also happened when SEACOM went down for like a month!

An easy fix: switch to the @mweb.co.za realm :)
 
Mweb is really working on my nerves now. I'm not downloading at all on my uncapped account during the day anymore. I want to download a simple 50mb file off rapishare at 22:00, and I'm getting a speed of 0.28 kb/s at the fastest, until it finally breaks. Also with Megaupload, breaks the connection. When I download from something like cnet downloads, I get 45 kb/s. How can they explain this. Throttling so badly that I can't do anything anymore. Hellopeter her I come. I declare war against these c@#ts now.....
 
spacemonkeyj said:
Mweb is really working on my nerves now. I'm not downloading at all on my uncapped account during the day anymore. I want to download a simple 50mb file off rapishare at 22:00, and I'm getting a speed of 0.28 kb/s at the fastest, until it finally breaks. Also with Megaupload, breaks the connection. When I download from something like cnet downloads, I get 45 kb/s. How can they explain this. Throttling so badly that I can't do anything anymore. Hellopeter her I come. I declare war against these c@#ts now.....
Click to expand...

interwebz are deaded, it's becoming a weekend trend now for mweb. aslo getting around 1-2kB/s lol...
 
Ya, looks like they are working on something. I am hoping this is related to the IPC in Cape Town. Perhaps they are trying to launch it. Please let this be the case!!

I hope this is fully fixed by 2AM Tonight, The NFL(National Football League--In America) is starting and I need to stream this game live in HD, please let their BE LIGHT. Can't afford downtime today, too f'n excited!!
 
Last edited:
same latency problems
crap(per than normal) speeds
guess it must be related to this as stated above
Outage Num:8569
MWEB ADSL outage affecting All areas
MWEB ADSL services in the following area may be Slow : All areas : Slow international and local internet browsing and email.
Start Date:2010-09-09 15:04:36
End Date:
Status:Open
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X