MWEB Uncapped ADSL Feedback

Status
Not open for further replies.
Hi Prophet,

These are Telkom related outages that are reported to us. There is no further information relating to the outages and no ETA with regards to a resolution. Updates are posted on the Network Status page once the outage has been resolved.

Kind regards,
MWEB Guy

Thank you.

/gets out of ADSL Safety bunker ;)
 
MWEB 1Mb - really poor performance - not unusual
Test conducted on 15 January 2012 9:09:10 PM SAST

Download Speed: 221 kbps (27.6 KB/sec transfer rate)
Upload Speed: 150 kbps (18.8 KB/sec transfer rate)
Latency: 250 ms

Hi alexius,

Please send me the MWEB account details via PM as I would like to look into this from our side.

Kind regards,
MWEB Guy
 
Just ran the test again (My Broadband speed test - using South African Server)
The speed is getting worse.....;-(

Your Latest Results (1Mb line)
Test conducted on 15 January 2012 9:50:00 PM SAST

Download Speed: 100 kbps (12.5 KB/sec transfer rate)
Upload Speed: 82 kbps (10.3 KB/sec transfer rate)
Latency: 274 ms
 
youtube very slow again....

+1 even on my 384k account, did not think Youtube could be this slow

fine on Telkom

Edit Finally cleared up, back to normal speed
 
Last edited:
Hi Guys,

Thanks for all the feedback, glad to hear things are back to normal.

Kind regards,
MWEB Guy
 
Just ran speed test again -

Your Latest Results - 1Mb ADSL - using International Server
Test conducted on 16 January 2012 9:23:57 AM SAST

Download Speed: 164 kbps (20.5 KB/sec transfer rate)
Upload Speed: 81 kbps (10.1 KB/sec transfer rate)
Latency: 563 ms

Your Latest Results- 1Mb ADSL - using Local Server
Test conducted on 16 January 2012 9:27:30 AM SAST

Download Speed: 239 kbps (29.9 KB/sec transfer rate)
Upload Speed: 155 kbps (19.4 KB/sec transfer rate)
Latency: 820 ms
 
Just ran speed test again -

Your Latest Results - 1Mb ADSL - using International Server
Test conducted on 16 January 2012 9:23:57 AM SAST

Download Speed: 164 kbps (20.5 KB/sec transfer rate)
Upload Speed: 81 kbps (10.1 KB/sec transfer rate)
Latency: 563 ms

Your Latest Results- 1Mb ADSL - using Local Server
Test conducted on 16 January 2012 9:27:30 AM SAST

Download Speed: 239 kbps (29.9 KB/sec transfer rate)
Upload Speed: 155 kbps (19.4 KB/sec transfer rate)
Latency: 820 ms

Hi alexius,

Would you mind please doing a test using the MWEB speed test?
I'd like to compare the results and take it from there.

kind regards,
MWEB Guy
 
Mweb -

1710219192.png


Imaginet -

1710221523.png



200 extra ping on DDO with packet loss again ........ not hard to see why when my local ping is 150 odd on Mweb today. This last week or so has been really crappy again, why so much crap after a good while of smooth?
 
Imaginet tests -

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

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

Pinging www-cctld.l.google.com [209.85.229.94] with 32 bytes of data:
Reply from 209.85.229.94: bytes=32 time=237ms TTL=51
Reply from 209.85.229.94: bytes=32 time=237ms TTL=51
Reply from 209.85.229.94: bytes=32 time=237ms TTL=51
Reply from 209.85.229.94: bytes=32 time=237ms TTL=51

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

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

Tracing route to www-cctld.l.google.com [209.85.229.94]
over a maximum of 30 hops:

1 7 ms 7 ms 8 ms 196-210-130-1.dynamic.isadsl.co.za [196.210.130.
1]
2 20 ms 20 ms 20 ms cdsl2-rba-vl2563.ip.isnet.net [196.38.73.213]
3 20 ms 20 ms 20 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
4 21 ms 21 ms 20 ms core1b-rba-te2-0-0.ip.isnet.net [196.26.0.181]
5 255 ms 255 ms 255 ms mi-za-rba-p5-gi2-0-2.ip.isnet.net [168.209.164.9
7]
6 250 ms 251 ms 250 ms mi-uk-dock-p3-gi3-1-1.ip.isnet.net [168.209.161.
80]
7 300 ms 255 ms 254 ms core1a-dock-gi1-0-17.ip.isnet.net [168.209.164.2
04]
8 233 ms 230 ms 230 ms 168.209.246.66
9 232 ms 281 ms 231 ms 195.66.226.125
10 229 ms 229 ms 228 ms 209.85.252.76
11 231 ms 228 ms 229 ms 209.85.253.92
12 237 ms 237 ms 237 ms 72.14.232.134
13 236 ms 236 ms 234 ms 72.14.236.191
14 * 235 ms 234 ms 209.85.243.73
15 237 ms 237 ms 237 ms ww-in-f94.1e100.net [209.85.229.94]

Trace complete.

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

Pinging www.mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=20ms TTL=53
Reply from 41.203.21.137: bytes=32 time=20ms TTL=53
Reply from 41.203.21.137: bytes=32 time=20ms TTL=53
Reply from 41.203.21.137: bytes=32 time=20ms TTL=53

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


Mweb tests -

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

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

Pinging www-cctld.l.google.com [74.125.233.24] with 32 bytes of data:
Reply from 74.125.233.24: bytes=32 time=148ms TTL=55
Reply from 74.125.233.24: bytes=32 time=141ms TTL=55
Reply from 74.125.233.24: bytes=32 time=153ms TTL=55
Reply from 74.125.233.24: bytes=32 time=139ms TTL=55

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

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

Tracing route to www-cctld.l.google.com [74.125.233.24]
over a maximum of 30 hops:

1 7 ms 7 ms 8 ms 41-133-68-1.dsl.mweb.co.za [41.133.68.1]
2 125 ms 125 ms 128 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
3 126 ms 125 ms 123 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
4 147 ms 149 ms 146 ms ge1-0-1.cpt-cinx-2.mweb.co.za [196.28.178.137]
5 146 ms 150 ms 149 ms google.cinx.net.za [196.223.22.41]
6 147 ms 146 ms 147 ms 64.233.174.105
7 146 ms 146 ms 147 ms cpt01s01-in-f24.1e100.net [74.125.233.24]

Trace complete.

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

Pinging www.mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=135ms TTL=51
Reply from 41.203.21.137: bytes=32 time=136ms TTL=51
Reply from 41.203.21.137: bytes=32 time=136ms TTL=51
Reply from 41.203.21.137: bytes=32 time=135ms TTL=51

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

It's clear Mweb has issues.
 
Mweb -

1710219192.png


Imaginet -

1710221523.png



200 extra ping on DDO with packet loss again ........ not hard to see why when my local ping is 150 odd on Mweb today. This last week or so has been really crappy again, why so much crap after a good while of smooth?

Hi Mephisto_Helix,

Thanks for all the info provided.
I will look into this for you from my side and let you know if I find anything.

kind regards,
MWEB Guy
 
Much thanks bru

Hi Mephisto_Helix,

I have check with the engineers and there seem to be no issues on the network.
I have since refreshed your account, please could you power down your router for 5mins and let me know if your connection improves.

kind regards,
MWEB Guy
 
Not even the slightest difference, actually, I think it's now worse :mad:

1710338314.png



And judging by my other accounts being just peachy, I would say there IS an issue on the network, it's clear as day.
 
Not even the slightest difference, actually, I think it's now worse :mad:

1710338314.png



And judging by my other accounts being just peachy, I would say there IS an issue on the network, it's clear as day.

Hi Mephisto_Helix,

Thank you for bringing this matter to our attention.
Our engineers are investigating underlying cause and hopefully it will be resolved soon.

kind regards,
MWEB Guy
 
Went out until now and I see (touch wood) that everything looks fine again ....... so whatever was done, thank you.
 
Went out until now and I see (touch wood) that everything looks fine again ....... so whatever was done, thank you.

Thanks for the feedback Mephisto, the problem should be resolved now. Please let me know should the problem re-occur.

Kind regards, MWEB Guy
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X