MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
Getting bad latency and some packet loss today =/

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

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=67ms TTL=118
Reply from 196.2.63.110: bytes=32 time=66ms TTL=118
Reply from 196.2.63.110: bytes=32 time=69ms TTL=118
Reply from 196.2.63.110: bytes=32 time=65ms TTL=118
Reply from 196.2.63.110: bytes=32 time=96ms TTL=118
Reply from 196.2.63.110: bytes=32 time=77ms TTL=118
Reply from 196.2.63.110: bytes=32 time=72ms TTL=118
Reply from 196.2.63.110: bytes=32 time=84ms TTL=118
Reply from 196.2.63.110: bytes=32 time=95ms TTL=118
Reply from 196.2.63.110: bytes=32 time=102ms TTL=118
Request timed out.
Reply from 196.2.63.110: bytes=32 time=99ms TTL=118
Reply from 196.2.63.110: bytes=32 time=72ms TTL=118
Reply from 196.2.63.110: bytes=32 time=973ms TTL=118
Reply from 196.2.63.110: bytes=32 time=104ms TTL=118
Reply from 196.2.63.110: bytes=32 time=66ms TTL=118
Reply from 196.2.63.110: bytes=32 time=97ms TTL=118
Reply from 196.2.63.110: bytes=32 time=95ms TTL=118
Reply from 196.2.63.110: bytes=32 time=88ms TTL=118
Reply from 196.2.63.110: bytes=32 time=103ms TTL=118
Reply from 196.2.63.110: bytes=32 time=78ms TTL=118
Reply from 196.2.63.110: bytes=32 time=71ms TTL=118
Reply from 196.2.63.110: bytes=32 time=106ms TTL=118
Reply from 196.2.63.110: bytes=32 time=78ms TTL=118
Request timed out.
Reply from 196.2.63.110: bytes=32 time=65ms TTL=118
Reply from 196.2.63.110: bytes=32 time=95ms TTL=118
Reply from 196.2.63.110: bytes=32 time=98ms TTL=118
Reply from 196.2.63.110: bytes=32 time=80ms TTL=118
Reply from 196.2.63.110: bytes=32 time=65ms TTL=118
Reply from 196.2.63.110: bytes=32 time=274ms TTL=118
Reply from 196.2.63.110: bytes=32 time=93ms TTL=118
Reply from 196.2.63.110: bytes=32 time=97ms TTL=118
Reply from 196.2.63.110: bytes=32 time=174ms TTL=118
Reply from 196.2.63.110: bytes=32 time=98ms TTL=118
Reply from 196.2.63.110: bytes=32 time=81ms TTL=118
Reply from 196.2.63.110: bytes=32 time=67ms TTL=118
Reply from 196.2.63.110: bytes=32 time=65ms TTL=118
Reply from 196.2.63.110: bytes=32 time=67ms TTL=118
Reply from 196.2.63.110: bytes=32 time=86ms TTL=118
Reply from 196.2.63.110: bytes=32 time=67ms TTL=118
Reply from 196.2.63.110: bytes=32 time=147ms TTL=118
Reply from 196.2.63.110: bytes=32 time=67ms TTL=118

Ping statistics for 196.2.63.110:
Packets: Sent = 43, Received = 41, Lost = 2 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 65ms, Maximum = 973ms, Average = 112ms
 
Same here, bad packet loss. Mweb guy......This has gone on for a pretty long time now. Is your network team just lazy or what? Get this stuff fixed. I have reported this to you last week already. Can we expect a week off our payment for this internet that is unplayable on?
 
Here's some more info:

C:\Users\Werner>pathping mweb.co.za

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:
0 Werner-PC [192.168.0.77]
1 192.168.0.1
2 41-133-128-1.dsl.mweb.co.za [41.133.128.1]
3 tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
4 vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 TenGigE0-0-0-0.11.vic-up-1.mweb.co.za [196.22.169.225]
6 196.22.169.46
7 Vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
8 196-28-178-66.adsl.mweb.co.za [196.28.178.66]
9 cte-core-sw2.vwol.net [196.41.144.35]
10 www.mweb.co.za [196.2.63.110]

Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Werner-PC [192.168.0.77]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
1/ 100 = 1% |
2 113ms 4/ 100 = 4% 3/ 100 = 3% 41-133-128-1.dsl.mweb.co.za [41.133.128.1]
0/ 100 = 0% |
3 56ms 1/ 100 = 1% 0/ 100 = 0% tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
0/ 100 = 0% |
4 64ms 7/ 100 = 7% 6/ 100 = 6% vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
0/ 100 = 0% |
5 114ms 1/ 100 = 1% 0/ 100 = 0% TenGigE0-0-0-0.11.vic-up-1.mweb.co.za [196.22.169.225]
0/ 100 = 0% |
6 138ms 3/ 100 = 3% 2/ 100 = 2% 196.22.169.46
0/ 100 = 0% |
7 139ms 2/ 100 = 2% 1/ 100 = 1% Vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
0/ 100 = 0% |
8 80ms 1/ 100 = 1% 0/ 100 = 0% 196-28-178-66.adsl.mweb.co.za [196.28.178.66]
2/ 100 = 2% |
9 136ms 3/ 100 = 3% 0/ 100 = 0% cte-core-sw2.vwol.net [196.41.144.35]
2/ 100 = 2% |
10 99ms 5/ 100 = 5% 0/ 100 = 0% www.mweb.co.za [196.2.63.110]

Trace complete.



C:\Users\Werner>tracert mweb.co.za

Tracing route to 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 * 60 ms 64 ms 41-133-128-1.dsl.mweb.co.za [41.133.128.1]
3 43 ms 38 ms 47 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
4 45 ms 45 ms 44 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 106 ms 101 ms 85 ms TenGigE0-0-0-0.11.vic-up-1.mweb.co.za [196.22.169.225]
6 * 110 ms 115 ms 196.22.169.46
7 137 ms 112 ms 113 ms Vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
8 74 ms 84 ms 92 ms 196-28-178-66.adsl.mweb.co.za [196.28.178.66]
9 128 ms 132 ms 98 ms cte-core-sw2.vwol.net [196.41.144.35]
10 67 ms 65 ms 68 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
Last edited:
Soulcode said:
Getting bad latency and some packet loss today =/

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

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=67ms TTL=118
Reply from 196.2.63.110: bytes=32 time=66ms TTL=118
Reply from 196.2.63.110: bytes=32 time=69ms TTL=118
Reply from 196.2.63.110: bytes=32 time=65ms TTL=118
Reply from 196.2.63.110: bytes=32 time=96ms TTL=118
Reply from 196.2.63.110: bytes=32 time=77ms TTL=118
Reply from 196.2.63.110: bytes=32 time=72ms TTL=118
Reply from 196.2.63.110: bytes=32 time=84ms TTL=118
Reply from 196.2.63.110: bytes=32 time=95ms TTL=118
Reply from 196.2.63.110: bytes=32 time=102ms TTL=118
Request timed out.
Reply from 196.2.63.110: bytes=32 time=99ms TTL=118
Reply from 196.2.63.110: bytes=32 time=72ms TTL=118
Reply from 196.2.63.110: bytes=32 time=973ms TTL=118
Reply from 196.2.63.110: bytes=32 time=104ms TTL=118
Reply from 196.2.63.110: bytes=32 time=66ms TTL=118
Reply from 196.2.63.110: bytes=32 time=97ms TTL=118
Reply from 196.2.63.110: bytes=32 time=95ms TTL=118
Reply from 196.2.63.110: bytes=32 time=88ms TTL=118
Reply from 196.2.63.110: bytes=32 time=103ms TTL=118
Reply from 196.2.63.110: bytes=32 time=78ms TTL=118
Reply from 196.2.63.110: bytes=32 time=71ms TTL=118
Reply from 196.2.63.110: bytes=32 time=106ms TTL=118
Reply from 196.2.63.110: bytes=32 time=78ms TTL=118
Request timed out.
Reply from 196.2.63.110: bytes=32 time=65ms TTL=118
Reply from 196.2.63.110: bytes=32 time=95ms TTL=118
Reply from 196.2.63.110: bytes=32 time=98ms TTL=118
Reply from 196.2.63.110: bytes=32 time=80ms TTL=118
Reply from 196.2.63.110: bytes=32 time=65ms TTL=118
Reply from 196.2.63.110: bytes=32 time=274ms TTL=118
Reply from 196.2.63.110: bytes=32 time=93ms TTL=118
Reply from 196.2.63.110: bytes=32 time=97ms TTL=118
Reply from 196.2.63.110: bytes=32 time=174ms TTL=118
Reply from 196.2.63.110: bytes=32 time=98ms TTL=118
Reply from 196.2.63.110: bytes=32 time=81ms TTL=118
Reply from 196.2.63.110: bytes=32 time=67ms TTL=118
Reply from 196.2.63.110: bytes=32 time=65ms TTL=118
Reply from 196.2.63.110: bytes=32 time=67ms TTL=118
Reply from 196.2.63.110: bytes=32 time=86ms TTL=118
Reply from 196.2.63.110: bytes=32 time=67ms TTL=118
Reply from 196.2.63.110: bytes=32 time=147ms TTL=118
Reply from 196.2.63.110: bytes=32 time=67ms TTL=118

Ping statistics for 196.2.63.110:
Packets: Sent = 43, Received = 41, Lost = 2 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 65ms, Maximum = 973ms, Average = 112ms
Click to expand...

Hi SoulCode,

I have refreshed your MWEB account. Please power down your router for 20-30min and do another test.

Kind regards,

MWEB Guy
 
Ok, so if i sign up with mweb, (I'm in CT), and it doesnt work so well, can I cancel without having to be billed for another month? or is it 30 days required for cancellation?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X