MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
Kind of an issue, but I cannot play dota on EU servers. Never before have I had such horrible dc's and lag. Game says 200ping. But I literally freeze ingame for 20 - 30 seconds and get communication errors.
 
Line is pretty much completely dead. It has been like this in the evening for 3 days straight. It has been pretty much perfect the last couple of months. Can you check my account for any irregularities please MWEB Guy?

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 814 ms 858 ms 905 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 949 ms 910 ms 903 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 907 ms 1012 ms 1018 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 741 ms 626 ms 607 ms 196.28.178.66
6 832 ms 795 ms 725 ms cte-core-sw2.vwol.net [196.41.144.35]
7 773 ms 913 ms 947 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Also - can you guys check out your news server? Missing articles are the catch of the day on MWEB - I thought running NNTP would be cheaper than having to serve all that content fresh from overseas :)
 
No offence MwebGuy but everytime I come here with a problem you tell me its an exchange issue :/

I don't think my ping has dropped from 120 since last thursday when this started.
I'll phone telkom tomorrow to ask if they can do all the regular checks.
 
Line is pretty much completely dead. It has been like this in the evening for 3 days straight. It has been pretty much perfect the last couple of months. Can you check my account for any irregularities please MWEB Guy?

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 814 ms 858 ms 905 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 949 ms 910 ms 903 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 907 ms 1012 ms 1018 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 741 ms 626 ms 607 ms 196.28.178.66
6 832 ms 795 ms 725 ms cte-core-sw2.vwol.net [196.41.144.35]
7 773 ms 913 ms 947 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Also - can you guys check out your news server? Missing articles are the catch of the day on MWEB - I thought running NNTP would be cheaper than having to serve all that content fresh from overseas :)

Evening StevenC

The results show that the exchange could be congested. The 2nd hop is very high. Does this normally happening in the evening more than during the day?

What is happening with the news server?
 
No offence MwebGuy but everytime I come here with a problem you tell me its an exchange issue :/

I don't think my ping has dropped from 120 since last thursday when this started.
I'll phone telkom tomorrow to ask if they can do all the regular checks.


Same issues for me I have even bypassed my wireless and am directly connected to the router.

My line is perfect. Not dropped a session in ages.

It must be from Mweb's side.

However I have also reported my line to Telkom to check.
 
My issues start at around 8pm, same as last night...

So if it is congestion, then what? I just have to put up with it?
 
Not at home during the day to test right now, but I was off sick last week since Thursday and it was mainly fine but generally from about 8 onwards the line just slows down to a trickle. Pages take ages to load, NNTP / P2P traffic is dead and I can barely do anything in GW2 (the only thing running).

News server wise - articles missing, lots of them! On fresh stuff as well. People on other ISPs are able to 100% it.

Trying to get a trial account for another ISP, my Afrihost one is being very shy with giving me my ADSL login password (that is active according to their client zone). Remember those free 1GB accounts? I cannot find the password anywhere for it!
 
My issues start at around 8pm, same as last night...

So if it is congestion, then what? I just have to put up with it?

Good MOrning Handz, if it is congestion we have to log a fault with Telkom. It will be up to them

I therefore require trace routes to mweb.co.za and bbc.co.uk when the problem occurs. Speed tests with your MWEB account and the Telkom guest account will also be appreciated.
 
Ok, I am very fast losing patience here. After the other day, I now have this, which happened out of nowhere about 10 minutes ago.

Afrihost - fine and dandy

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

Tracing route to mygaming.co.za [41.72.157.182]
over a maximum of 30 hops:

1 6 ms 7 ms 6 ms 105-236-7-129-esr-lo.mtnbusiness.co.za [105.236.
7.129]
2 19 ms 18 ms 18 ms 41.181.222.42
3 17 ms 16 ms 16 ms ng-mse-1--ng-cr-1-a.za.mtnns.net [196.44.27.68]

4 15 ms 16 ms 22 ms jh-cr-1.za--ng-cr-1.za.mtnns.net [196.44.31.176]

5 16 ms 16 ms 20 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
6 19 ms 19 ms 19 ms qux--rb-dca-2.za-b.za.mtnbusiness.net [41.181.16
5.119]
7 16 ms 16 ms 16 ms 196.30.1.53
8 16 ms 16 ms 17 ms tengigabitethernet9-1.gw20.jnb6.za.mtnbusiness.n
et [196.31.220.25]
9 16 ms 15 ms 15 ms tengigabitethernet5-1.hr9.jnb6.za.mtnbusiness.ne
t [196.31.63.146]
10 20 ms 20 ms 20 ms core-router1.jnb2.host-h.net [196.30.213.108]
11 16 ms 16 ms * firewall5.jnb2.host-h.net [41.72.136.23]
12 20 ms 19 ms 20 ms 41.72.157.182

Trace complete.

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

Pinging mygaming.co.za [41.72.157.182] with 32 bytes of data:
Reply from 41.72.157.182: bytes=32 time=20ms TTL=57
Reply from 41.72.157.182: bytes=32 time=19ms TTL=57
Reply from 41.72.157.182: bytes=32 time=20ms TTL=57
Reply from 41.72.157.182: bytes=32 time=20ms TTL=57

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


Mweb - a trainsmash

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

Tracing route to mygaming.co.za [41.72.157.182]
over a maximum of 30 hops:

1 6 ms 6 ms 6 ms 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
2 452 ms 470 ms 446 ms 197.82.5.250
3 429 ms 426 ms 437 ms 197.82.2.3
4 459 ms 468 ms 484 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
5 495 ms 455 ms 461 ms static161-134.netactive.co.za [196.22.161.134]
6 466 ms 469 ms 476 ms jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]

7 489 ms 470 ms 481 ms 196.44.31.99
8 476 ms 471 ms 487 ms 196.31.220.6
9 458 ms 453 ms 468 ms tengigabitethernet1-1.gw20.jnb6.za.mtnbusiness.n
et [196.31.220.23]
10 457 ms 445 ms 452 ms tengigabitethernet5-1.hr9.jnb6.za.mtnbusiness.ne
t [196.31.63.146]
11 470 ms 452 ms 458 ms core-router1.jnb2.host-h.net [196.30.213.108]
12 451 ms 459 ms 450 ms firewall5.jnb2.host-h.net [41.72.136.23]
13 452 ms 453 ms 457 ms 41.72.157.182

Trace complete.

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

Pinging mygaming.co.za [41.72.157.182] with 32 bytes of data:
Reply from 41.72.157.182: bytes=32 time=464ms TTL=54
Reply from 41.72.157.182: bytes=32 time=462ms TTL=54
Reply from 41.72.157.182: bytes=32 time=439ms TTL=54
Reply from 41.72.157.182: bytes=32 time=432ms TTL=54

Ping statistics for 41.72.157.182:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 432ms, Maximum = 464ms, Average = 449ms

Wth is going on. I can't even browse with Mweb. Please notice that 2nd hop with Afrihost there is nothing at all wrong.
 
My MWEB in DBN also just took a dive... 2nd hop at exchange is 20 ms.. then afterwards anywhere between 300ms and 600ms locally. Any other Durbanites with an issue?
 
Okay glad I'm not the only one having problems. Tried rebooting router to no avail.
 
Yeah Mal1ce, Mweb is Deadweb for me in Durbs North Coast- currently on my Afrihost account! Any idea whats up Mweb?
 
My MWEB in DBN also just took a dive... 2nd hop at exchange is 20 ms.. then afterwards anywhere between 300ms and 600ms locally. Any other Durbanites with an issue?

I'll bet 2 beers the Dinx just bombed .......


Getting over Mweb to be honest. Time to find a better alternative.
 
DBN MWEB is Borked....

With MWEB...

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\>ping www.google.co.za

Pinging www.google.co.za [74.125.233.56] with 32 bytes of data:
Reply from 74.125.233.56: bytes=32 time=472ms TTL=53
Reply from 74.125.233.56: bytes=32 time=488ms TTL=53
Reply from 74.125.233.56: bytes=32 time=470ms TTL=53
Reply from 74.125.233.56: bytes=32 time=493ms TTL=54

Ping statistics for 74.125.233.56:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 470ms, Maximum = 493ms, Average = 480ms

C:\Users\>ping www.google.co.za -t

Pinging www.google.co.za [74.125.233.56] with 32 bytes of data:
Reply from 74.125.233.56: bytes=32 time=482ms TTL=53
Reply from 74.125.233.56: bytes=32 time=459ms TTL=54
Reply from 74.125.233.56: bytes=32 time=462ms TTL=53
Reply from 74.125.233.56: bytes=32 time=443ms TTL=54
Reply from 74.125.233.56: bytes=32 time=467ms TTL=54
Reply from 74.125.233.56: bytes=32 time=461ms TTL=54
Reply from 74.125.233.56: bytes=32 time=474ms TTL=54
Reply from 74.125.233.56: bytes=32 time=453ms TTL=53
Reply from 74.125.233.56: bytes=32 time=475ms TTL=54
Reply from 74.125.233.56: bytes=32 time=462ms TTL=54
Reply from 74.125.233.56: bytes=32 time=480ms TTL=53
Reply from 74.125.233.56: bytes=32 time=489ms TTL=54

Ping statistics for 74.125.233.56:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 443ms, Maximum = 489ms, Average = 467ms

C:\Users\>tracert www.google.co.za

Tracing route to www.google.co.za [74.125.233.56]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 7 ms 6 ms 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
3 457 ms 455 ms 455 ms 197.82.5.250
4 526 ms 467 ms 440 ms 197.82.2.3
5 446 ms 443 ms 437 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
6 426 ms 449 ms 422 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
7 468 ms 438 ms 452 ms 64.233.174.21
8 474 ms 485 ms 483 ms jnb01s01-in-f24.1e100.net [74.125.233.56]

Trace complete.



Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\>ping www.mweb.co.za -t

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=486ms TTL=119
Reply from 196.2.63.110: bytes=32 time=492ms TTL=119
Reply from 196.2.63.110: bytes=32 time=498ms TTL=119
Reply from 196.2.63.110: bytes=32 time=485ms TTL=119
Reply from 196.2.63.110: bytes=32 time=498ms TTL=119
Reply from 196.2.63.110: bytes=32 time=508ms TTL=119
Reply from 196.2.63.110: bytes=32 time=1060ms TTL=119
Reply from 196.2.63.110: bytes=32 time=494ms TTL=119
Reply from 196.2.63.110: bytes=32 time=481ms TTL=119
Reply from 196.2.63.110: bytes=32 time=492ms TTL=119
Reply from 196.2.63.110: bytes=32 time=490ms TTL=119
Reply from 196.2.63.110: bytes=32 time=494ms TTL=119
Reply from 196.2.63.110: bytes=32 time=468ms TTL=119

Ping statistics for 196.2.63.110:
Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 468ms, Maximum = 1060ms, Average = 534ms


Same line with Afrihost....
C:\Users\>ping www.mweb.co.za -t

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=44ms TTL=116
Reply from 196.2.63.110: bytes=32 time=117ms TTL=116
Reply from 196.2.63.110: bytes=32 time=43ms TTL=116
Reply from 196.2.63.110: bytes=32 time=44ms TTL=116
Reply from 196.2.63.110: bytes=32 time=43ms TTL=116
Reply from 196.2.63.110: bytes=32 time=43ms TTL=116
Reply from 196.2.63.110: bytes=32 time=42ms TTL=116
Reply from 196.2.63.110: bytes=32 time=43ms TTL=116
Reply from 196.2.63.110: bytes=32 time=43ms TTL=116
Reply from 196.2.63.110: bytes=32 time=48ms TTL=116
Reply from 196.2.63.110: bytes=32 time=43ms TTL=116

Ping statistics for 196.2.63.110:
Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 117ms, Average = 50ms
C:\Users\>


C:\Users\>
 
Last edited:
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X