MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
Im also getting drops. It's happened quite a few times today going by my IRC connection which got disconnected about 4 times so far
Oh and it seems my speeds have gone back to their.. 50-60's again for downloads.

Telkom speeds flying. at 100-107KB's Mweb... not flying :p
 
Last edited:
Keep on getting disconnected from NFS World Servers, and my pings to local sites are at 100ms+. I have NEVER experienced pings like these for local sites.

Mweb Ping:
Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=111ms TTL=119
Reply from 196.2.63.110: bytes=32 time=111ms TTL=119
Reply from 196.2.63.110: bytes=32 time=110ms TTL=119
Reply from 196.2.63.110: bytes=32 time=110ms TTL=119

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

BBC:
Pinging www.bbc.net.uk [212.58.244.69] with 32 bytes of data:
Reply from 212.58.244.69: bytes=32 time=270ms TTL=47
Reply from 212.58.244.69: bytes=32 time=269ms TTL=47
Reply from 212.58.244.69: bytes=32 time=269ms TTL=47
Request timed out.

Ping statistics for 212.58.244.69:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 269ms, Maximum = 270ms, Average = 269ms
 
Last edited:
Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 196.2.63.110: bytes=32 time=126ms TTL=119
Reply from 196.2.63.110: bytes=32 time=122ms TTL=119
Reply from 196.2.63.110: bytes=32 time=121ms TTL=119
Reply from 196.2.63.110: bytes=32 time=124ms TTL=119
Reply from 196.2.63.110: bytes=32 time=121ms TTL=119
Request timed out.
Reply from 196.2.63.110: bytes=32 time=146ms TTL=119
Reply from 196.2.63.110: bytes=32 time=155ms TTL=119
Reply from 196.2.63.110: bytes=32 time=144ms TTL=119
Reply from 196.2.63.110: bytes=32 time=138ms TTL=119

Ping statistics for 196.2.63.110:
Packets: Sent = 16, Received = 9, Lost = 7 (43% loss),
Approximate round trip times in milli-seconds:
Minimum = 121ms, Maximum = 155ms, Average = 133ms

Same thing for me
 
BBC
Pinging www.bbc.net.uk [212.58.244.71] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.58.244.71: bytes=32 time=277ms TTL=46
Reply from 212.58.244.71: bytes=32 time=276ms TTL=46
Request timed out.
Reply from 212.58.244.71: bytes=32 time=276ms TTL=46

Ping statistics for 212.58.244.71:
Packets: Sent = 10, Received = 3, Lost = 7 (70% loss),
Approximate round trip times in milli-seconds:
Minimum = 276ms, Maximum = 277ms, Average = 276ms
 
It seems the timeouts have stopped but latency is still very high and browsing is slightly better.

Hi

I have reauthed your account for you as a test.
please power down the router for a few minutes then test the connection again and let me know how it goes.
 
Very very high packet loss only on Mweb and connection keeps freezing/dying for up to a minute at a time .......
 
Hi

I have reauthed your account for you as a test.
please power down the router for a few minutes then test the connection again and let me know how it goes.

Switched to afrihost 1gb account and am having the same problem. Might be telkom.
 
I have noticed my mweb connection has been relatively poor over the last 2 days.

http://www.speedtest.net/result/2328498478.png

I have a 10mb line and no, I am not getting 10mb.

Modem stats:
Downstream Upstream
Current Rate(Kbps) 10015 1023
Max Rate(Kbps) 23628 1088
Noise Margin(dB) 12.9 8
Attenuation(dB) 29 13
Output Power(dBm) 5.5 12.5
 
Just spoke to telkom and they said there isnt a fault on their side but they recreated the port for me and reset everything. Still getting slow speeds and high latency.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X