- Joined
- Apr 13, 2010
- Messages
- 10,689
- Reaction score
- 7
seems problem fixed itself now as speeds are restored![]()
Glad to hear it
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
seems problem fixed itself now as speeds are restored![]()
1 <1 ms <1 ms <1 ms home.gateway
2 4 ms 5 ms 4 ms dsl.mweb.co.za
3 4 ms 4 ms 4 ms tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.169.134]
4 4 ms 4 ms 4 ms 196.22.189.28
5 8 ms 6 ms 11 ms 196.22.169.90
6 8 ms 7 ms 7 ms 196.41.144.36
7 7 ms 7 ms 7 ms www.mweb.co.za [196.2.63.110]
2 12 ms 13 ms 7 ms dsl.mweb.co.za
3 * * 5 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 5 ms 7 ms 5 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 27 ms 21 ms 22 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 21 ms 23 ms 18 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
7 227 ms 112 ms 76 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 80 ms 103 ms 216 ms 195.66.224.125
9 * 227 ms 180 ms 64.233.175.25
10 252 ms 190 ms 182 ms 72.14.232.95
11 274 ms 195 ms 228 ms 64.233.174.41
12 171 ms 88 ms 176 ms 64.233.174.33
13 111 ms 138 ms 110 ms 64.233.174.107
14 92 ms 102 ms 96 ms cpt01s01-in-f104.1e100.net [64.233.179.104]
1 1 ms <1 ms <1 ms home.gateway
2 4 ms 3 ms 4 ms dsl.mweb.co.za
3 3 ms 4 ms 5 ms tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.163.218]
4 8 ms 7 ms 7 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 15 ms 14 ms 12 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 10 ms 10 ms 8 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
7 157 ms 193 ms 238 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 138 ms 100 ms 104 ms 79.141.38.37.available.above.net [79.141.38.37]
9 97 ms 144 ms 134 ms so-0-1-0.mpr1.dca2.us.above.net [64.125.27.57]
10 165 ms 86 ms 119 ms xe-1-3-0.cr1.dca2.us.above.net [64.125.29.21]
11 107 ms 257 ms 160 ms xe-1-0-0.cr2.dca2.us.above.net [64.125.28.250]
12 117 ms 253 ms 121 ms xe-2-2-0.cr2.lga5.us.above.net [64.125.26.106]
13 147 ms 244 ms 127 ms xe-0-2-0.cr2.ord2.us.above.net [64.125.27.33]
14 149 ms 155 ms 161 ms xe-1-1-0.mpr2.sea1.us.above.net [64.125.31.1]
15 122 ms 196 ms 315 ms 209.249.11.189.available.above.net [209.249.11.189]
16 258 ms 187 ms 153 ms 152.ge-1-3-0.sr2.sea5.speakeasy.net [69.17.82.54]
17 251 ms 217 ms 601 ms www.ookla.com [69.17.117.207]
1 <1 ms <1 ms <1 ms home.gateway
2 7 ms 7 ms 13 ms dsl.mweb.co.za
3 55 ms 48 ms 63 ms tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.169.134]
4 18 ms 11 ms 13 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 17 ms 11 ms 21 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 16 ms 23 ms 13 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 47 ms 76 ms 34 ms 196.43.39.22
8 47 ms 101 ms 119 ms vodacom-gw.telkom-ipnet.co.za [196.25.253.110]
9 18 ms 28 ms 21 ms 41.0.0.23
10 6 ms 16 ms 4 ms 41.0.4.2
11 31 ms 31 ms 72 ms vc-196-207-44-133.3g.vodacom.co.za [196.207.44.133]
12 14 ms 17 ms 73 ms 10.113.222.133
13 13 ms 8 ms 24 ms 10.113.222.134
14 8 ms 17 ms 9 ms 10.113.222.178
15 45 ms 12 ms 12 ms 41.1.224.101
Some feedback about my connection.
1. I checked and rechecked my hardware and router; redid the wiring and connection to phone wall socket. Still no difference.
2. Called Telkom--and my line went dead in the middle of reporting to the Consultant--after waiting on the line to get through for more than 45 mins.
3. I then drove to my local exchange (copper to fibre-booth) and lo and behold, those idots from Telkom were working on the box!
4. Those idiots disconnected me, my analogue line and all.
I am now back at home and those guys have gone--so it seems they may have fixed the problem.
Anyway, I wish to thank Will@MWEB for being helpful and asking me to check all paths from my phone to local exchange.
S
Some feedback about my connection.
1. I checked and rechecked my hardware and router; redid the wiring and connection to phone wall socket. Still no difference.
2. Called Telkom--and my line went dead in the middle of reporting to the Consultant--after waiting on the line to get through for more than 45 mins.
3. I then drove to my local exchange (copper to fibre-booth) and lo and behold, those idots from Telkom were working on the box!
4. Those idiots disconnected me, my analogue line and all.
I am now back at home and those guys have gone--so it seems they may have fixed the problem.
Anyway, I wish to thank Will@MWEB for being helpful and asking me to check all paths from my phone to local exchange.
S
traceroute to www.mweb.co.za (196.2.63.110), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 1.313 ms 1.866 ms 2.901 ms
2 41-132-4-1.dsl.mweb.co.za (41.132.4.1) 19.147 ms 21.494 ms 24.194 ms
3 tengig-0-0-0-100.vic-ipc-2.mweb.co.za (196.22.163.206) 36.515 ms 39.620 ms 41.593 ms
4 196.22.189.28 (196.22.189.28) 44.588 ms 47.844 ms 52.063 ms
5 196.22.169.90 (196.22.169.90) 73.145 ms 75.506 ms 77.932 ms
6 196.41.144.36 (196.41.144.36) 79.964 ms 324.190 ms 49.309 ms
7 * * *
It seems to have resolved the problem.
Mweb's shaper is now shaping ftp.
Some feedback about my connection.
1. I checked and rechecked my hardware and router; redid the wiring and connection to phone wall socket. Still no difference.
2. Called Telkom--and my line went dead in the middle of reporting to the Consultant--after waiting on the line to get through for more than 45 mins.
3. I then drove to my local exchange (copper to fibre-booth) and lo and behold, those idots from Telkom were working on the box!
4. Those idiots disconnected me, my analogue line and all.
I am now back at home and those guys have gone--so it seems they may have fixed the problem.
Anyway, I wish to thank Will@MWEB for being helpful and asking me to check all paths from my phone to local exchange.
S
2 17 ms 15 ms 16 ms 41-132-48-1.dsl.mweb.co.za [41.132.48.1]
3 203 ms 210 ms 205 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.2
9.146]
4 193 ms 201 ms 209 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
Dear Mweb.
Half our BC2 clan has 200 plus pings tonight. Everyone who is on mweb. We cannot play our BC2 league match with these kind of pings. Some of our opponents have the same problem. Personally, my ping is fine, but then I route my BC2 traffic through webafrica and let most of the rest go through mweb.
We are going to cancel our match tonight. Please fix your network or stop shaping our gaming protocol, especially since it's only local traffic we are doing.
Hi pmurgs
We definitely aren't shaping any BC2 traffic, the latency on the link in question climbed yesterday morning as well.
I raised it with our networks team and they were able to make some adjustments to reduce this. I will discuss this with them tomorrow morning and see what can be done about this.