MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
Wow, were you brought up in a barn? Learn some manners and respect. Bloody kiddies.
 
We've provided quite a bit of evidence showing that it's not a line quality issue.

Speed tests are running strong, but we can clearly see low quality results in several areas. Thankfully my gaming is still manageable, otherwise I'd have to ditch this account.
 
Had no connection last night. For some reason I could not connect to account. Logged into router and pressed the connect button but no connection. Restarted router a few times then gave up. This morning I logged in again and pressed the button and it worked. Strange.
 
No connection last night, this morning it was on for a short while, now is dead again. Reset the router, got the line checked no problems on my side. I would like to know what I am actually getting from my R899.00 per month. There has barely been a day without issues.
 
Mweb -
72249611.png



Afrihost -
72249685.png



Not acceptable anymore, just not :mad:



Afrihost -

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=19ms TTL=55
Reply from 41.203.21.137: bytes=32 time=19ms TTL=55
Reply from 41.203.21.137: bytes=32 time=19ms TTL=55
Reply from 41.203.21.137: bytes=32 time=20ms TTL=55

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

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

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=215ms TTL=239
Reply from 212.58.241.131: bytes=32 time=215ms TTL=239
Reply from 212.58.241.131: bytes=32 time=215ms TTL=239
Reply from 212.58.241.131: bytes=32 time=215ms TTL=239

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

C:\Users\Andre>ping side-line.com

Pinging side-line.com [74.208.47.190] with 32 bytes of data:
Reply from 74.208.47.190: bytes=32 time=341ms TTL=46
Reply from 74.208.47.190: bytes=32 time=341ms TTL=46
Reply from 74.208.47.190: bytes=32 time=341ms TTL=46
Reply from 74.208.47.190: bytes=32 time=341ms TTL=46

Ping statistics for 74.208.47.190:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 341ms, Maximum = 341ms, Average = 341ms
Click to expand...


Mweb -

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=194ms TTL=50
Reply from 41.203.21.137: bytes=32 time=194ms TTL=50
Reply from 41.203.21.137: bytes=32 time=191ms TTL=50
Reply from 41.203.21.137: bytes=32 time=195ms TTL=50

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

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

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=372ms TTL=238
Reply from 212.58.241.131: bytes=32 time=373ms TTL=238
Reply from 212.58.241.131: bytes=32 time=372ms TTL=238
Reply from 212.58.241.131: bytes=32 time=375ms TTL=238

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

C:\Users\Andre>ping side-line.com

Pinging side-line.com [74.208.47.190] with 32 bytes of data:
Reply from 74.208.47.190: bytes=32 time=497ms TTL=46
Reply from 74.208.47.190: bytes=32 time=486ms TTL=46
Reply from 74.208.47.190: bytes=32 time=486ms TTL=46
Reply from 74.208.47.190: bytes=32 time=488ms TTL=46

Ping statistics for 74.208.47.190:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 486ms, Maximum = 497ms, Average = 489ms
Click to expand...
 
Last edited:
MWEB Guy said:
Hi Pr⊕phet

Please see PM I sent you.
Click to expand...

I replied, thanks. Note that I also get packet loss*** on the mweb network when using plotping from work. It does seem not to be limited to only my house address.

***loss at:
197.80.4.140 / tengig0-0-0-1.vic-p-1.mweb.co.za
197.80.5.7 / pos0-3-2-0.lon-up-1.mweb.co.za
 


Also getting some packet loss this morning. Testing the first time I got 5% packet loss. Also getting 1% packet loss to Capetown and the test can't even connect to the Pretoria and Johannesburg servers.
 
...I've requested a port recreate, not sure if that is going to fix it since it only occurs when I'm connected to mweb trying to play dialbo3. I will retest this tonight being connected to AH and WA to make sure...
 
Phoned MWeb support, was told my password is shown as being incorrect. Please explain how I could log on an still manage to download 40GB so far this month with an incorrect password?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X