- Joined
- Apr 13, 2010
- Messages
- 10,689
- Reaction score
- 7
I have read and replied.Hi MWEB Guy
Please check the pm I sent u
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
I have read and replied.Hi MWEB Guy
Please check the pm I sent u
Test conducted on Sat Aug 11 2012 21:18:07 GMT+0200 (South Africa Standard Time)
Download Speed: 3685 kbps (460.6 KB/sec transfer rate)
Upload Speed: 289 kbps (36.1 KB/sec transfer rate)
Latency: 291 ms
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
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=276ms TTL=239
Reply from 212.58.241.131: bytes=32 time=282ms TTL=239
Reply from 212.58.241.131: bytes=32 time=281ms TTL=239
Reply from 212.58.241.131: bytes=32 time=283ms 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 = 276ms, Maximum = 283ms, Average = 280ms
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=394ms TTL=48
Reply from 74.208.47.190: bytes=32 time=388ms TTL=48
Reply from 74.208.47.190: bytes=32 time=388ms TTL=48
Reply from 74.208.47.190: bytes=32 time=388ms TTL=48
Ping statistics for 74.208.47.190:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 388ms, Maximum = 394ms, Average = 389ms

I am also seeing a roughly 70ms increase above normal latency. This is unrelated to the PM I sent you, MWEB Guy![]()
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.1.1
2 26 ms 25 ms 26 ms 41-133-128-1.dsl.mweb.co.za [41.133.128.1]
3 34 ms 35 ms 35 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.163.206]
4 34 ms 34 ms 34 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 60 ms 58 ms 59 ms tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.226]
6 57 ms 58 ms 60 ms TenGigE0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]
7 56 ms 54 ms 54 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
8 55 ms 55 ms 55 ms 196.28.178.66
9 55 ms 54 ms 55 ms cte-core-sw2.vwol.net [196.41.144.35]
10 55 ms 55 ms 56 ms www.mweb.co.za [196.2.63.110]
Trace complete.
C:\Users\Werner>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms 192.168.1.1
2 25 ms 26 ms 25 ms 41-133-128-1.dsl.mweb.co.za [41.133.128.1]
3 34 ms 35 ms 36 ms 41-86-107-6.mweb.co.za [41.86.107.6]
4 34 ms 35 ms 35 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 282 ms 279 ms 279 ms tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.226]
6 278 ms 280 ms 279 ms pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
7 268 ms 266 ms 267 ms 176.67.177.131
8 283 ms 276 ms 278 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
9 279 ms 267 ms 274 ms vl-3604-ve-228.csw2.London1.Level3.net [4.69.166.157]
10 282 ms 276 ms 278 ms ae-24-52.car3.London1.Level3.net [4.69.139.100]
11 271 ms 265 ms 264 ms 195.50.90.162
12 * * * Request timed out.
13 271 ms 266 ms 265 ms ae1.er01.thdow.bbc.co.uk [132.185.254.18]
14 273 ms 265 ms 268 ms 132.185.255.92
15 265 ms 266 ms 265 ms 212.58.241.131
Trace complete.
Hi Guys,
Please let me know if things have improved your side.
We've been experiencing this for the last two days, on an uncapped 10Mbps line:
![]()
tracert mweb.co.za
Tracing route to mweb.co.za [196.2.63.110] over a maximum of 30 hops:
1 9 ms 10 ms 11 ms 192.168.1.1
2 17 ms 165 ms 60 ms 41-133-138-1.dsl.mweb.co.za [41.133.138.1]
3 14 ms 11 ms 10 ms te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178]
4 16 ms 14 ms 13 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 11 ms 14 ms 18 ms 196.28.178.66
6 22 ms 13 ms 11 ms cte-core-sw2.vwol.net [196.41.144.35]
7 9 ms 17 ms 9 ms www.mweb.co.za [196.2.63.110]
tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.241.131] over a maximum of 30 hops:
1 4 ms 3 ms 4 ms 192.168.1.1
2 13 ms 69 ms 42 ms 41-133-138-1.dsl.mweb.co.za [41.133.138.1]
3 17 ms 886 ms 21 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 10 ms 9 ms * 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 195 ms 189 ms 190 ms TenGigE0-7-0-3.12.cpt-p-1.mweb.co.za [196.28.178.113]
6 158 ms 155 ms 163 ms 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
7 186 ms 155 ms 163 ms 176.67.177.131
8 165 ms 167 ms 155 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
9 163 ms 156 ms 157 ms vl-3504-ve-118.csw1.London1.Level3.net [4.69.166.141]
10 277 ms 190 ms 189 ms ae-14-51.car3.London1.Level3.net [4.69.139.68]
11 271 ms 200 ms 202 ms 195.50.90.162
12 * * * Request timed out.
13 319 ms 174 ms 185 ms ae1.er01.thdow.bbc.co.uk [132.185.254.18]
14 168 ms 154 ms 164 ms 132.185.255.92
15 213 ms 154 ms 161 ms 212.58.241.131
Hi Awesum
I checked the account and line. The line readings are a bit irregular. Attenuation is very high. I would suggest contacting Telkom, have them re-create the port and investigate what is causing the attenuation to be that high as well. .
A technician checked my line and said everything is ok.
He said the reason my attenuation is 63 is because Im about 3.5 Kms from the exchange.
Good Afternoon Awesum, under normal circumstances anything below 4km's would be acceptable. Strange that you are at 3.5km's and the reason for high attenuation is distance.
I would suggest calling them and finding out what an acceptable distance is.
Have a look at our pricing hbelow.
http://www.mweb.co.za/productspricing/InternetAccess/ADSL/BigtimeSurfer.aspx
Hi MWEB Guy,
Do you know when the new telkom pricing will take affect as I have my line with them and 1mbps uncapped with you? Reason I ask is that I see MWEB has the reduced pricing on their site already. I.e. is the whole of August at the reduced adsl access rate or from end September?