MWEB Gaming Feedback

StevenC said:
Yeah I had the disconnect at 11:45 last night as well, thought it was strange.

Connected now, latency in the red (2500ms and decreased down to 900ms), seems responsive though.

MEH! We just started raiding last night, last thing I need is more latency! Fortunately I still have accounts knocking about, hopefully this isn't another 3 month issue!
Click to expand...

There was some planned maintenance in Cape Town in the time slot you are referring to, which required a brief reroute via JHB. I believe they upgraded one of the core IPC switches to create more capacity to accept future bandwdith increases. I have been away for a few days - I will still be on leave for another week :D, but I will be checking in periodically. Is everything ok now?
 
ebolazaire said:
Hi Will,

Just read throught he last 50ish pages regarding lag in World of Warcraft.
I'm currently using 4megabit uncapped mweb in jhb.

I'm unable to load any of my characters in WoW atm, when i do manage to log in i'm looking at a ping ranging from 10000ms-20000ms.
I've logged on using a 512 Telkom connection and it runs fine, so it looks like the problem is on my mweb side.

Is anybody else experiencing the same? Is this something that you are currently aware of jhb-side?
Click to expand...

Was working okay with some disconnects this weekend, but come monday morning my problem with logging onto my toon has returned.
 
i was highosh this morning btu was responsive, when i get 20k ms i just wait 1 min or so then it drops down
 
OK if anyone is having intermittent issues can you please give me as much data as possible. When do experience the problem? How long does it last for? where are you located? cmd line latency and a tracert to bbc.co.uk captured while you are having the problem. Also don't forget to eliminate factors like addons and downloads from the equation.
 
Located in Melville Johannesburg.

I'm able to log into WoW, select a character, and then watch the loading bar fill up wait a few minutes watching the bar and then it disconnects.
It does the same with or without any addons loaded. There aren't any downloads going atm.

It did it last week during the week, and then was better on the weekend. Was playing fine last night with a 400ms ping, and then started with the disconnects again this morning.

I'm on a 4mbs uncapped package.

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

1 23 ms 29 ms 4 ms 10.0.0.2
2 21 ms 10 ms 44 ms 41-132-18-1.dsl.mweb.co.za [41.132.18.1]
3 10 ms 12 ms 27 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
4 14 ms 35 ms 13 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 35 ms 27 ms 15 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 13 ms 62 ms 16 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
7 275 ms 295 ms 260 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 350 ms 448 ms 414 ms 149.6.98.17
9 276 ms 241 ms 422 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 261 ms 250 ms 248 ms te4-4.mpd02.lon01.atlas.cogentco.com [130.117.1.134]
11 263 ms 255 ms 236 ms ldn-b4-link.telia.net [213.248.70.237]
12 273 ms 272 ms 259 ms ldn-bb1-link.telia.net [80.91.252.197]
13 243 ms 233 ms 283 ms ldn-b3-link.telia.net [80.91.249.170]
14 233 ms 283 ms 235 ms siemens-ic-119241-ldn-b2.c.telia.net [213.248.104.70]
15 283 ms 252 ms 269 ms 212.58.238.133
16 258 ms 298 ms 256 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.
 
Will, it seems to have settled down for me again, working fine. Only issue is the first time i load a character, i get dc'ed, takes long to enter the game, but when im in the ping is awesome.
This is with or without battleping.
 
Very odd , I get the occassional dc when loading characters, but I generally attribute it to the fact that I'm impatient and tend to alt-tab and do something else while it's loading in.
 
ebolazaire said:
Located in Melville Johannesburg.

I'm able to log into WoW, select a character, and then watch the loading bar fill up wait a few minutes watching the bar and then it disconnects.
It does the same with or without any addons loaded. There aren't any downloads going atm.

It did it last week during the week, and then was better on the weekend. Was playing fine last night with a 400ms ping, and then started with the disconnects again this morning.

I'm on a 4mbs uncapped package.

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

1 23 ms 29 ms 4 ms 10.0.0.2
2 21 ms 10 ms 44 ms 41-132-18-1.dsl.mweb.co.za [41.132.18.1]
3 10 ms 12 ms 27 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
4 14 ms 35 ms 13 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 35 ms 27 ms 15 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 13 ms 62 ms 16 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
7 275 ms 295 ms 260 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 350 ms 448 ms 414 ms 149.6.98.17
9 276 ms 241 ms 422 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 261 ms 250 ms 248 ms te4-4.mpd02.lon01.atlas.cogentco.com [130.117.1.134]
11 263 ms 255 ms 236 ms ldn-b4-link.telia.net [213.248.70.237]
12 273 ms 272 ms 259 ms ldn-bb1-link.telia.net [80.91.252.197]
13 243 ms 233 ms 283 ms ldn-b3-link.telia.net [80.91.249.170]
14 233 ms 283 ms 235 ms siemens-ic-119241-ldn-b2.c.telia.net [213.248.104.70]
15 283 ms 252 ms 269 ms 212.58.238.133
16 258 ms 298 ms 256 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.
Click to expand...

I can't see anything in particular wrong with that trace. We need to try and see if there are any other symptoms besides the dc's that we can pin down, what you can try for me as well is to run an extended ping (ping -n 100 bbc.co.uk) and lets have a look at just the final portion of the test, where it shows average ping and packet loss. When were were struggling with extreme in game latency previously the dc's people were getting were I think attributable to timeouts while loading into a busy area. In this case I can't think of an explanation offhand for what you're experiencing so let's just check the general connection quality before we get ahead of ourselves.
 
Also getting the dc at loading of character thing. Normally the first time I try but then it works. But other than that everything is good.
 
Will@MWEB said:
I can't see anything in particular wrong with that trace. We need to try and see if there are any other symptoms besides the dc's that we can pin down, what you can try for me as well is to run an extended ping (ping -n 100 bbc.co.uk) and lets have a look at just the final portion of the test, where it shows average ping and packet loss. When were were struggling with extreme in game latency previously the dc's people were getting were I think attributable to timeouts while loading into a busy area. In this case I can't think of an explanation offhand for what you're experiencing so let's just check the general connection quality before we get ahead of ourselves.
Click to expand...

Ping statistics for 212.58.224.138:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 251ms, Maximum = 683ms, Average = 283ms

Tried to connect after completing the ping.
Select character and sat at the loading bar for 3 minutes before it disconnected me.
edit: tried connecting more than once, all attempts met with the same result.

This is where my confusion comes in, the connection itself looks good.
So the problem should be on my side, but I got an Afrihost account for testing and it connects fine on that account.
 
Last edited:
Location: Boksburg
Time: 9PM

Usual disconnect, lag spikes, 2k ms and total frustration in wow, retail and private servers...
frankly im getting sick of this, im on a 512k Uncapped, Unshaped account.

tracert info:



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

1 1 ms 1 ms 1 ms sitecomwl312.sitecomwl312 [192.168.1.1]
2 1 ms 1 ms 1 ms 192.168.0.1
3 85 ms 68 ms 79 ms 41-133-74-1.dsl.mweb.co.za [41.133.74.1]
4 180 ms 264 ms 284 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
5 * * 108 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
6 312 ms 348 ms 344 ms tengig-0-0-0-0-12.vic-up-2.mweb.co.za [196.22.169.242]
7 430 ms 555 ms 587 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
8 702 ms 665 ms 515 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
9 708 ms 841 ms 775 ms 149.6.98.17
10 676 ms 1013 ms * te3-4.ccr02.lon02.atlas.cogentco.com [154.54.36.169]
11 884 ms 1001 ms 751 ms te9-2.mpd02.lon01.atlas.cogentco.com [130.117.48.153]
12 650 ms 466 ms 804 ms ldn-b4-link.telia.net [213.248.70.237]
13 763 ms 725 ms 755 ms ldn-bb1-link.telia.net [80.91.248.217]
14 683 ms 930 ms 696 ms ldn-b3-link.telia.net [80.91.245.27]
15 765 ms 702 ms 986 ms siemens-ic-119241-ldn-b2.c.telia.net [213.248.104.70]
16 933 ms 813 ms 611 ms 212.58.238.133
17 741 ms 620 ms 478 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.


ping info to www.google.com


Pinging www.l.google.com [209.85.227.147] with 32 bytes of data:
Reply from 209.85.227.147: bytes=32 time=618ms TTL=50
Reply from 209.85.227.147: bytes=32 time=667ms TTL=50
Reply from 209.85.227.147: bytes=32 time=386ms TTL=50
Reply from 209.85.227.147: bytes=32 time=702ms TTL=50
Reply from 209.85.227.147: bytes=32 time=598ms TTL=50
Reply from 209.85.227.147: bytes=32 time=735ms TTL=50
Reply from 209.85.227.147: bytes=32 time=829ms TTL=50
Reply from 209.85.227.147: bytes=32 time=930ms TTL=50
Reply from 209.85.227.147: bytes=32 time=1396ms TTL=50
Request timed out.
Reply from 209.85.227.147: bytes=32 time=1316ms TTL=50
Reply from 209.85.227.147: bytes=32 time=558ms TTL=50
Reply from 209.85.227.147: bytes=32 time=472ms TTL=50
Reply from 209.85.227.147: bytes=32 time=656ms TTL=50
Reply from 209.85.227.147: bytes=32 time=935ms TTL=50
Reply from 209.85.227.147: bytes=32 time=918ms TTL=50
Reply from 209.85.227.147: bytes=32 time=700ms TTL=50
Reply from 209.85.227.147: bytes=32 time=589ms TTL=50
Reply from 209.85.227.147: bytes=32 time=657ms TTL=50
Reply from 209.85.227.147: bytes=32 time=923ms TTL=50

Ping statistics for 209.85.227.147:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 386ms, Maximum = 1396ms, Average = 767ms


Will@MWEB Please, please please sort this out. IM so sick of MWEB's connection after 7pm!

Edit: Timeouts are regular after 7pm and the results look similar for both @mweb and @dslmweb, although these are from the @mweb set.

Edit2: Its 10PM and this is what shows up to a ping at www.google.com!?!?!


Pinging www.l.google.com [209.85.229.99] with 32 bytes of data:
Reply from 209.85.229.99: bytes=32 time=2901ms TTL=50
Reply from 209.85.229.99: bytes=32 time=1438ms TTL=50
Reply from 209.85.229.99: bytes=32 time=3501ms TTL=50
Reply from 209.85.229.99: bytes=32 time=1150ms TTL=50
Reply from 209.85.229.99: bytes=32 time=1232ms TTL=50
Reply from 209.85.229.99: bytes=32 time=876ms TTL=50
Request timed out.
Reply from 209.85.229.99: bytes=32 time=1154ms TTL=50
Reply from 209.85.229.99: bytes=32 time=1225ms TTL=50
Reply from 209.85.229.99: bytes=32 time=1499ms TTL=50
Reply from 209.85.229.99: bytes=32 time=2247ms TTL=50
Request timed out.
Reply from 209.85.229.99: bytes=32 time=1067ms TTL=50
Reply from 209.85.229.99: bytes=32 time=3275ms TTL=50
Request timed out.
Reply from 209.85.229.99: bytes=32 time=1137ms TTL=50
Reply from 209.85.229.99: bytes=32 time=1468ms TTL=50
Reply from 209.85.229.99: bytes=32 time=2691ms TTL=50
Reply from 209.85.229.99: bytes=32 time=1006ms TTL=50
Reply from 209.85.229.99: bytes=32 time=541ms TTL=50

Ping statistics for 209.85.229.99:
Packets: Sent = 20, Received = 16, Lost = 4 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 541ms, Maximum = 3275ms, Average = 1381ms



And again at 10.03PM things seem to be a bit better (still not perfect) only 3 minutes later:



Pinging www.l.google.com [209.85.146.147] with 32 bytes of data:
Reply from 209.85.146.147: bytes=32 time=519ms TTL=51
Reply from 209.85.146.147: bytes=32 time=568ms TTL=51
Reply from 209.85.146.147: bytes=32 time=544ms TTL=51
Reply from 209.85.146.147: bytes=32 time=442ms TTL=51
Reply from 209.85.146.147: bytes=32 time=531ms TTL=51
Reply from 209.85.146.147: bytes=32 time=531ms TTL=51
Reply from 209.85.146.147: bytes=32 time=644ms TTL=51
Reply from 209.85.146.147: bytes=32 time=613ms TTL=51
Reply from 209.85.146.147: bytes=32 time=621ms TTL=51
Reply from 209.85.146.147: bytes=32 time=716ms TTL=51
Reply from 209.85.146.147: bytes=32 time=591ms TTL=51
Reply from 209.85.146.147: bytes=32 time=682ms TTL=51
Reply from 209.85.146.147: bytes=32 time=326ms TTL=51
Reply from 209.85.146.147: bytes=32 time=306ms TTL=51
Reply from 209.85.146.147: bytes=32 time=316ms TTL=51
Reply from 209.85.146.147: bytes=32 time=551ms TTL=51
Reply from 209.85.146.147: bytes=32 time=445ms TTL=51
Reply from 209.85.146.147: bytes=32 time=383ms TTL=51
Reply from 209.85.146.147: bytes=32 time=349ms TTL=51
Reply from 209.85.146.147: bytes=32 time=539ms TTL=51

Ping statistics for 209.85.146.147:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 306ms, Maximum = 716ms, Average = 510ms

And finally at 10:06 these are what we expect to see... another 3 minutes later:


Pinging www.l.google.com [209.85.146.147] with 32 bytes of data:
Reply from 209.85.146.147: bytes=32 time=298ms TTL=51
Reply from 209.85.146.147: bytes=32 time=267ms TTL=51
Reply from 209.85.146.147: bytes=32 time=267ms TTL=51
Reply from 209.85.146.147: bytes=32 time=309ms TTL=51
Reply from 209.85.146.147: bytes=32 time=267ms TTL=51
Reply from 209.85.146.147: bytes=32 time=269ms TTL=51
Reply from 209.85.146.147: bytes=32 time=281ms TTL=51
Reply from 209.85.146.147: bytes=32 time=267ms TTL=51
Reply from 209.85.146.147: bytes=32 time=297ms TTL=51
Reply from 209.85.146.147: bytes=32 time=271ms TTL=51
Reply from 209.85.146.147: bytes=32 time=277ms TTL=51
Reply from 209.85.146.147: bytes=32 time=269ms TTL=51
Reply from 209.85.146.147: bytes=32 time=284ms TTL=51
Reply from 209.85.146.147: bytes=32 time=269ms TTL=51
Reply from 209.85.146.147: bytes=32 time=274ms TTL=51
Reply from 209.85.146.147: bytes=32 time=269ms TTL=51
Reply from 209.85.146.147: bytes=32 time=267ms TTL=51
Reply from 209.85.146.147: bytes=32 time=265ms TTL=51
Reply from 209.85.146.147: bytes=32 time=278ms TTL=51
Reply from 209.85.146.147: bytes=32 time=321ms TTL=51

Ping statistics for 209.85.146.147:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 265ms, Maximum = 321ms, Average = 278ms


Will@MWEB, unfortunately no tracert for the last couple of statistics, but if the problem arises again you can epect em :)
 
Last edited:
ebolazaire said:
Ping statistics for 212.58.224.138:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 251ms, Maximum = 683ms, Average = 283ms

Tried to connect after completing the ping.
Select character and sat at the loading bar for 3 minutes before it disconnected me.
edit: tried connecting more than once, all attempts met with the same result.

This is where my confusion comes in, the connection itself looks good.
So the problem should be on my side, but I got an Afrihost account for testing and it connects fine on that account.
Click to expand...

I can't see a reason for this either, I just want to clarify the exact symptoms you're describing here now, because it sounds like you're saying that you can't connect at all with your MWEB account? Have you tried something like creating a new toon on another realm, or maybe clearing the wow cache folders?

Also lets try and force an IP change, drop your connection for about 15 minutes and leave the router off. As a final check go onto the mweb myaccount page, under the adsl settings look for protected access and disable it (this really shouldn't be affecting anything, but just to be thorough).
 
this type problem you get in heavy user area, aka orgemar, it should fine in another areas, i got his on my 3g usally when im not getting enough bandwitdh
 
ultraviolet150 said:
Location: Boksburg
Time: 9PM

Usual disconnect, lag spikes, 2k ms and total frustration in wow, retail and private servers...
frankly im getting sick of this, im on a 512k Uncapped, Unshaped account.

tracert info:



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

1 1 ms 1 ms 1 ms sitecomwl312.sitecomwl312 [192.168.1.1]
2 1 ms 1 ms 1 ms 192.168.0.1
3 85 ms 68 ms 79 ms 41-133-74-1.dsl.mweb.co.za [41.133.74.1]
4 180 ms 264 ms 284 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
ping info to www.google.com

Will@MWEB Please, please please sort this out. IM so sick of MWEB's connection after 7pm!

Edit: Timeouts are regular after 7pm and the results look similar for both @mweb and @dslmweb, although these are from the @mweb set.

Edit2: Its 10PM and this is what shows up to a ping at www.google.com!?!?!


Pinging www.l.google.com [209.85.229.99] with 32 bytes of data:
Reply from 209.85.229.99: bytes=32 time=2901ms TTL=50
Reply from 209.85.229.99: bytes=32 time=1438ms TTL=50
Reply from 209.85.229.99: bytes=32 time=3501ms TTL=50

Will@MWEB, unfortunately no tracert for the last couple of statistics, but if the problem arises again you can epect em :)
Click to expand...

No need for that this is plenty :) Those pings are definitely not normal and I don't like the look of the way your latency starts to climb from the word go. I think the next step here is to get your line conditions checked and also to have my team log this with Telkom to be checked for possible congestion at the exchange, or DSLAM level. I'm not in the office at the moment so could I ask you to PM your account details and line number directly to MWEB Operations. I will let them know what I want tested and once they come back with some answers we'll take it from there.
 
Will@MWEB said:
I can't see a reason for this either, I just want to clarify the exact symptoms you're describing here now, because it sounds like you're saying that you can't connect at all with your MWEB account? Have you tried something like creating a new toon on another realm, or maybe clearing the wow cache folders?

Also lets try and force an IP change, drop your connection for about 15 minutes and leave the router off. As a final check go onto the mweb myaccount page, under the adsl settings look for protected access and disable it (this really shouldn't be affecting anything, but just to be thorough).
Click to expand...

Correct, whilst on my mweb account I can't log onto any of my toons on any server. Also not a problem with logging out in high population area since my main is currently at Tarren Mill.
Haven't had a chance to force an IP change as the connection is currently in use by others, will give it a go soon and edit this post to let you know if it works.

Below is my latest ping to bbc.co.uk, less pretty than the previous one i posted;

Ping statistics for 212.58.224.138:
Packets: Sent = 100, Received = 93, Lost = 7 (7% loss),
Approximate round trip times in milli-seconds:
Minimum = 242ms, Maximum = 1312ms, Average = 480ms
 
Will@MWEB said:
No need for that this is plenty :) Those pings are definitely not normal and I don't like the look of the way your latency starts to climb from the word go. I think the next step here is to get your line conditions checked and also to have my team log this with Telkom to be checked for possible congestion at the exchange, or DSLAM level. I'm not in the office at the moment so could I ask you to PM your account details and line number directly to MWEB Operations. I will let them know what I want tested and once they come back with some answers we'll take it from there.
Click to expand...
ok so who exactly to PM? do u want me to PM MWEB operations on this forum and if so can u please link their profile link.

Edit: Nevermind, PM'd it to MWEB Operations on the forum.
just for interest sake here are my pings and tracert to bbc.co.uk at 8.03PM:



Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=570ms TTL=110
Reply from 212.58.224.138: bytes=32 time=260ms TTL=110
Reply from 212.58.224.138: bytes=32 time=245ms TTL=110
Reply from 212.58.224.138: bytes=32 time=412ms TTL=110
Reply from 212.58.224.138: bytes=32 time=484ms TTL=110
Reply from 212.58.224.138: bytes=32 time=595ms TTL=110
Reply from 212.58.224.138: bytes=32 time=436ms TTL=110
Reply from 212.58.224.138: bytes=32 time=326ms TTL=110
Reply from 212.58.224.138: bytes=32 time=457ms TTL=110
Reply from 212.58.224.138: bytes=32 time=455ms TTL=110
Reply from 212.58.224.138: bytes=32 time=475ms TTL=110
Reply from 212.58.224.138: bytes=32 time=518ms TTL=110
Reply from 212.58.224.138: bytes=32 time=322ms TTL=110
Reply from 212.58.224.138: bytes=32 time=401ms TTL=110
Reply from 212.58.224.138: bytes=32 time=397ms TTL=110
Reply from 212.58.224.138: bytes=32 time=737ms TTL=110
Reply from 212.58.224.138: bytes=32 time=506ms TTL=110
Reply from 212.58.224.138: bytes=32 time=1111ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=530ms TTL=110

Ping statistics for 212.58.224.138:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 245ms, Maximum = 1111ms, Average = 486ms


And the Tracert at 8.05PM:


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

1 5 ms 1 ms 1 ms sitecomwl312.sitecomwl312 [192.168.1.1]
2 10 ms 2 ms 2 ms 192.168.0.1
3 281 ms 286 ms 249 ms 41-133-74-1.dsl.mweb.co.za [41.133.74.1]
4 171 ms 159 ms 162 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.163.206]
5 239 ms 420 ms 432 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
6 118 ms 129 ms 147 ms tengig-0-0-0-0-11.vic-up-2.mweb.co.za [196.22.169.226]
7 321 ms 321 ms 300 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
8 522 ms 408 ms 367 ms 196.22.175.210
9 605 ms 387 ms 322 ms 149.6.98.5
10 1144 ms * * te3-4.ccr02.lon02.atlas.cogentco.com [154.54.36.169]
11 416 ms 357 ms 429 ms te9-2.mpd02.lon01.atlas.cogentco.com [130.117.48.153]
12 583 ms 959 ms 880 ms ldn-b4-link.telia.net [213.248.70.237]
13 1129 ms 1289 ms 1475 ms ldn-bb2-link.telia.net [80.91.249.181]
14 1556 ms 1117 ms 620 ms ldn-b3-link.telia.net [80.91.245.29]
15 740 ms 663 ms 897 ms siemens-ic-119241-ldn-b2.c.telia.net [213.248.104.70]
16 1019 ms 714 ms 545 ms 212.58.238.149
17 * * 515 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.
 
Last edited:
Definitely something wrong there ultraviolet

5% packet loss on the ping and note this part of the trace:

1 5 ms 1 ms 1 ms sitecomwl312.sitecomwl312 [192.168.1.1]
2 10 ms 2 ms 2 ms 192.168.0.1
3 281 ms 286 ms 249 ms 41-133-74-1.dsl.mweb.co.za [41.133.74.1]
4 171 ms 159 ms 162 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.163.206]
Click to expand...

That's originating at the very early stages of your connection, so either the line itself, or something at the DSLAM / exchange level before you reach our network. Let's see what we get back from the team once they've had everything checked for you and take it from there. You might also want to give your local cabling a once over just to be certain we haven't overlooked the basics. Make sure you don't have any open telephone jacks or analog devices (handsets, fax, etc) that don't have a microfilter installed and that none of your cabling looks damaged, or has loose connectors.
 
Will@MWEB said:
Definitely something wrong there ultraviolet

5% packet loss on the ping and note this part of the trace:



That's originating at the very early stages of your connection, so either the line itself, or something at the DSLAM / exchange level before you reach our network. Let's see what we get back from the team once they've had everything checked for you and take it from there. You might also want to give your local cabling a once over just to be certain we haven't overlooked the basics. Make sure you don't have any open telephone jacks or analog devices (handsets, fax, etc) that don't have a microfilter installed and that none of your cabling looks damaged, or has loose connectors.
Click to expand...

OK Will, everything has been checked, telephone is on microfilters (has always been), no line damage or loose connections. Lets hope for good news from the team :)
 
Couldnt update sc2 or update the maps in game. Hopped on telkom and instant update no problems. Downloads also suddenly going today at half line speed again (is it really needed to half the download speed of 384's?)
Im in the big starcraft2 SA channel, no one on mweb can update the game or play at all. FIX THIS ****.
 
Last edited:
ultraviolet150 said:
ok so who exactly to PM? do u want me to PM MWEB operations on this forum and if so can u please link their profile link.

Edit: Nevermind, PM'd it to MWEB Operations on the forum.
just for interest sake here are my pings and tracert to bbc.co.uk at 8.03PM:



Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=570ms TTL=110
Reply from 212.58.224.138: bytes=32 time=260ms TTL=110
Reply from 212.58.224.138: bytes=32 time=245ms TTL=110
Reply from 212.58.224.138: bytes=32 time=412ms TTL=110
Reply from 212.58.224.138: bytes=32 time=484ms TTL=110
Reply from 212.58.224.138: bytes=32 time=595ms TTL=110
Reply from 212.58.224.138: bytes=32 time=436ms TTL=110
Reply from 212.58.224.138: bytes=32 time=326ms TTL=110
Reply from 212.58.224.138: bytes=32 time=457ms TTL=110
Reply from 212.58.224.138: bytes=32 time=455ms TTL=110
Reply from 212.58.224.138: bytes=32 time=475ms TTL=110
Reply from 212.58.224.138: bytes=32 time=518ms TTL=110
Reply from 212.58.224.138: bytes=32 time=322ms TTL=110
Reply from 212.58.224.138: bytes=32 time=401ms TTL=110
Reply from 212.58.224.138: bytes=32 time=397ms TTL=110
Reply from 212.58.224.138: bytes=32 time=737ms TTL=110
Reply from 212.58.224.138: bytes=32 time=506ms TTL=110
Reply from 212.58.224.138: bytes=32 time=1111ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=530ms TTL=110

Ping statistics for 212.58.224.138:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 245ms, Maximum = 1111ms, Average = 486ms


And the Tracert at 8.05PM:


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

1 5 ms 1 ms 1 ms sitecomwl312.sitecomwl312 [192.168.1.1]
2 10 ms 2 ms 2 ms 192.168.0.1
3 281 ms 286 ms 249 ms 41-133-74-1.dsl.mweb.co.za [41.133.74.1]
4 171 ms 159 ms 162 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.163.206]
5 239 ms 420 ms 432 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
6 118 ms 129 ms 147 ms tengig-0-0-0-0-11.vic-up-2.mweb.co.za [196.22.169.226]
7 321 ms 321 ms 300 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
8 522 ms 408 ms 367 ms 196.22.175.210
9 605 ms 387 ms 322 ms 149.6.98.5
10 1144 ms * * te3-4.ccr02.lon02.atlas.cogentco.com [154.54.36.169]
11 416 ms 357 ms 429 ms te9-2.mpd02.lon01.atlas.cogentco.com [130.117.48.153]
12 583 ms 959 ms 880 ms ldn-b4-link.telia.net [213.248.70.237]
13 1129 ms 1289 ms 1475 ms ldn-bb2-link.telia.net [80.91.249.181]
14 1556 ms 1117 ms 620 ms ldn-b3-link.telia.net [80.91.245.29]
15 740 ms 663 ms 897 ms siemens-ic-119241-ldn-b2.c.telia.net [213.248.104.70]
16 1019 ms 714 ms 545 ms 212.58.238.149
17 * * 515 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.
Click to expand...

Your traceroutes and pings are BAD, impossible to use for gaming bad. Either something is using up a lot of bandwidth on your line (torrent, spyware, virus etc.) and causing a bottleneck, your phone line is damaged, or your exchange is congested.

I recommend installing NetLimiter on all your home PCs for monitoring, disconnect any other devices that are using the internet and making sure there is nothing using bandwidth you are unaware of. You would be amazed how many people I've helped "fix" their ADSL lagging in games simply by finding a rampant process on one of the computers using up all their bandwidth.
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X