Durban MWEB Uncapped Users

L

linkinpark

Expert Member
Joined
Jun 27, 2005
Messages
1,465
Reaction score
225
I've been experiencing very high latency since Wednesday the 7th and it looks like a problem with the new POP in the Durban data centre.
Could any Durban MWEB users check their account as well as MWEB just called me and told me that i'm the only one that reported this so far. It's quite likely affected others, they just haven't noticed it. I only realised a problem when i tried to play a game online.

Here is a tracert:

Tracing route to google.com [74.125.233.17]
over a maximum of 30 hops:

1 7 ms 6 ms 7 ms ###-###-###-###.dsl.mweb.co.za [###.###.###.###]
2 8 ms 8 ms 7 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
3 8 ms 7 ms 7 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
4 240 ms 241 ms 255 ms 197-82-3-1.dbn.mweb.co.za [197.82.3.1]
5 241 ms 239 ms 243 ms tengig0-0-0-0.vic-p-1.mweb.co.za [197.84.4.38]
6 237 ms 274 ms 237 ms pos0-3-2-0.lon-up-1.mweb.co.za [197.80.5.7]
7 257 ms 255 ms 255 ms pos0-3-0-0.vic-p-1.mweb.co.za [197.80.5.6]
8 256 ms 256 ms 255 ms tengig0-7-0-0.vic-p-2.mweb.co.za [197.84.4.36]
9 256 ms 256 ms 257 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]
10 253 ms 254 ms 253 ms gi0-2-cpt-cinx.mweb.co.za [196.28.178.133]
11 254 ms 254 ms 254 ms google.cinx.net.za [196.223.22.41]
12 254 ms 254 ms 254 ms 64.233.174.105
13 254 ms 254 ms 254 ms cpt01s01-in-f17.1e100.net [74.125.233.17]

Trace complete.


As you can see, something is very wrong between the 3rd and 4th hop which looks to be in the same centre.
Also a speedtest to various servers around the country show a download average of 0.7mbps as opposed to my normal of around 4.5mbps.

So any Durban users, please do a trace and check your speeds. Thanks :)
 
Pinetown:

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

tracert google.com

Tracing route to google.com [74.125.233.18]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 7 ms 7 ms 41-132-60-1.dsl.mweb.co.za [41.132.60.1]
3 8 ms 8 ms 8 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 8 ms 11 ms 8 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 244 ms 243 ms 243 ms 197-82-3-1.dbn.mweb.co.za [197.82.3.1]
6 241 ms 239 ms 240 ms tengig0-0-0-0.vic-p-1.mweb.co.za [197.84.4.38]
7 237 ms 237 ms 237 ms pos0-3-2-0.lon-up-1.mweb.co.za [197.80.5.7]
8 213 ms 215 ms 214 ms 196.22.164.1
9 211 ms 210 ms 210 ms gi0-2-cpt-cinx.mweb.co.za [196.28.178.133]
10 211 ms 211 ms 210 ms google.cinx.net.za [196.223.22.41]
11 211 ms 211 ms 213 ms 64.233.174.105
12 211 ms 211 ms 212 ms cpt01s01-in-f18.1e100.net [74.125.233.18]

Trace complete.

My Modern Warfare 3 is farked since Wednesday. Follow my thread on MWEB gaming forum here: http://forums.gamezone.co.za/viewto...20dce8fb083d5f82e0b012cd2a8c339d&p=5220#p5220

Something is horribly wrong and I am getting peeved off now! BTW get same tracert results to Google.co.za
 
Last edited:
Same story here (in Durban):

Code: 
$ traceroute google.com
traceroute to google.com (74.125.233.19), 30 hops max, 60 byte packets
 1  192.168.1.254 (192.168.1.254)  11.005 ms  11.079 ms  11.162 ms
 2  41-132-60-1.dsl.mweb.co.za (41.132.60.1)  11.491 ms  13.384 ms  15.418 ms
 3  197-82-5-250.dbn.mweb.co.za (197.82.5.250)  19.822 ms  22.446 ms  25.149 ms
 4  197-82-2-3.dbn.mweb.co.za (197.82.2.3)  27.685 ms  29.809 ms  32.629 ms
 5  197-82-3-1.dbn.mweb.co.za (197.82.3.1)  360.951 ms  366.169 ms  372.223 ms
 6  tengig0-0-0-0.vic-p-1.mweb.co.za (197.84.4.38)  377.403 ms  249.658 ms  253.833 ms
 7  pos0-3-2-0.lon-up-1.mweb.co.za (197.80.5.7)  255.756 ms  258.313 ms  260.270 ms
 8  pos0-3-0-0.vic-p-2.mweb.co.za (197.80.5.8)  276.196 ms 196.22.164.1 (196.22.164.1)  234.560 ms  240.434 ms
 9  tengig0-1-0-0.cpt-up-1.mweb.co.za (197.84.4.34)  289.447 ms tengig0-7-0-0.vic-p-2.mweb.co.za (197.84.4.36)  283.279 ms  294.639 ms
10  google.cinx.net.za (196.223.22.41)  243.270 ms tengig0-1-0-0.cpt-up-1.mweb.co.za (197.84.4.34)  300.487 ms google.cinx.net.za (196.223.22.41)  529.934 ms
11  * ge1-0-1.cpt-cinx-2.mweb.co.za (196.28.178.137)  498.207 ms *
12  cpt01s01-in-f19.1e100.net (74.125.233.19)  219.978 ms  220.284 ms google.cinx.net.za (196.223.22.41)  283.620 ms

Pinging london1.linode.com gives a fairly low international ping time (244ms, similar to before).
Pinging mybroadband.co.za gives 218ms which means something is definitely wrong.
 
And the speedtest.net to Durban from Durban gives a ping of 250ms...
 


Any other server other than MWEB gives a 200+ ping ... WTF?

Durbs to Durbs Below OMFG ?!?!



I dont want freaking excuses ... FIX IT DAMMIT
 
Last edited:
Yep I tried a speedtest from Durban to Durban and it ends up being 250ms. Something is up.

See my tracert to the OP's IP address:
Note ping 1 was left off because it's my router IP :)
Tracing route to cpt01s01-in-f17.1e100.net [74.125.233.17]
over a maximum of 30 hops:
2 19 ms 18 ms 27 ms 41-132-6-1.dsl.mweb.co.za [41.132.6.1]
3 16 ms 23 ms 10 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 14 ms 16 ms 12 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 279 ms 268 ms 259 ms 197-82-3-1.dbn.mweb.co.za [197.82.3.1]
6 279 ms 240 ms 262 ms tengig0-0-0-0.vic-p-1.mweb.co.za [197.84.4.38]
7 256 ms 243 ms 325 ms pos0-3-2-0.lon-up-1.mweb.co.za [197.80.5.7]
8 393 ms 401 ms 428 ms pos0-3-0-0.vic-p-2.mweb.co.za [197.80.5.8]
9 469 ms 524 ms 594 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]

10 518 ms 470 ms 370 ms ge1-0-1.cpt-cinx-2.mweb.co.za [196.28.178.137]
11 449 ms 463 ms * google.cinx.net.za [196.223.22.41]
12 438 ms 342 ms 342 ms 64.233.174.105
13 307 ms 345 ms 391 ms cpt01s01-in-f17.1e100.net [74.125.233.17]

I hope they look at this ping issue before SWTOR goes live next week it would tick me off to no end if I can't play.
 
Also tracert to the Op's ip address

C:\Users\Screw>tracert 74.125.233.17

Tracing route to cpt01s01-in-f17.1e100.net [74.125.233.17]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms Billion.800VGT [10.0.0.2]
2 25 ms 27 ms 30 ms 41-133-70-1.dsl.mweb.co.za [41.133.70.1]
3 31 ms 30 ms 30 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 31 ms 30 ms 30 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 261 ms 269 ms 269 ms 197-82-3-1.dbn.mweb.co.za [197.82.3.1]
6 259 ms 258 ms 260 ms tengig0-0-0-0.vic-p-1.mweb.co.za [197.84.4.38]
7 263 ms 260 ms 258 ms pos0-3-2-0.lon-up-1.mweb.co.za [197.80.5.7]
8 235 ms 240 ms 238 ms 196.22.164.1
9 229 ms 232 ms 229 ms ge1-0-1.cpt-cinx-2.mweb.co.za [196.28.178.137]
10 234 ms 232 ms 229 ms google.cinx.net.za [196.223.22.41]
11 236 ms 228 ms 238 ms 64.233.174.105
12 231 ms 229 ms 229 ms cpt01s01-in-f17.1e100.net [74.125.233.17]

Trace complete.

Speedtest ping to Telkom Durban server 330ms
 
Last edited:
Yeah, my gaming has been fugged too.....absolutely frustrating.
Can someone at MWEB give an explanation, I'm on the verge of moving to another ISP.
Ping to JHB 305ms.
 
yip same here, posted it in the Mweb news server thread.... take out the dsl part of your username on your router, so it should be [email protected] that seems to route both my ADSL line through Cape Town which has a better latency.

and the best part is i am 100KM from Durban and the Cape Town Mweb POP is about 1200KM away and i get better latency....

Just went back to my @dslmweb.co.za to do a trace route it is terrible!!!

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

C:\Users\Ron>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 10.0.0.2
2 16 ms 18 ms 22 ms 41-133-244-1.dsl.mweb.co.za [41.133.244.1]
3 18 ms 13 ms 11 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 1174 ms 1184 ms 1465 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 1076 ms 1064 ms 1066 ms 197-82-3-1.dbn.mweb.co.za [197.82.3.1]
6 1138 ms 1155 ms 1252 ms tengig0-1-2-0.cpt-up-2.mweb.co.za [197.84.4.43]

7 1219 ms 1231 ms 1234 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
8 1134 ms 1236 ms 1176 ms 196-28-178-34.adsl.mweb.co.za [196.28.178.34]
9 1211 ms 1218 ms 1151 ms www.mweb.co.za [196.2.63.110]

Trace complete.

C:\Users\Ron>

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

C:\Users\Ron>tracert mybroadband.co.za

Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.2
2 19 ms 15 ms 19 ms 41-133-244-1.dsl.mweb.co.za [41.133.244.1]
3 17 ms 29 ms 20 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 * 218 ms 150 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 389 ms 357 ms 388 ms 197-82-3-1.dbn.mweb.co.za [197.82.3.1]
6 339 ms 399 ms 439 ms tengig0-1-2-0.cpt-up-2.mweb.co.za [197.84.4.43]

7 388 ms 410 ms 308 ms tengige0-3-0-0.12.cpt-up-1.mweb.co.za [196.28.17
8.113]
8 370 ms 367 ms 373 ms pos0-0-3-0.lon-up-1.mweb.co.za [196.22.164.2]
9 351 ms * 374 ms pos0-3-0-0.vic-p-1.mweb.co.za [197.80.5.6]
10 413 ms 440 ms 374 ms tengig0-7-0-0.vic-p-2.mweb.co.za [197.84.4.36]
11 387 ms * 373 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]

12 379 ms 387 ms 398 ms gi0-2-cpt-cinx.mweb.co.za [196.28.178.133]
13 335 ms 307 ms 385 ms mtn-pp.cpt-cinx-2.mweb.co.za [196.28.178.142]
14 * * * Request timed out.
15 317 ms 365 ms 375 ms rb-cr-1.za--ct-cr-1.za.mtnns.net [196.44.31.128]

16 * 365 ms 348 ms 196.44.31.97
17 * 385 ms 416 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.2
2]
18 384 ms 447 ms 392 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
19 * 491 ms 330 ms core-router1.jnb2.host-h.net [196.30.213.108]
20 * 393 ms 422 ms 41.72.136.53
21 490 ms 360 ms 368 ms mybroadband.co.za [41.203.21.137]

Trace complete.

C:\Users\Ron>

Why is Mybb going via London? or am I wrong?
 
Last edited:
Durban SpeedTests with Afrihost:





I would have to say that the results are conclusive, MWEB Durban = Farked. (Tested on same PC & ADSL line as previous MWEB speedtest results)
 
Hi All,

Thanks for the information you have provided. I will have to take this up with the relevant persons. Once we have information, we will provide you with feedback.

Kind regards,
MWEB Guy
 
Tracing route to google.com [74.125.233.16]
over a maximum of 30 hops:

1 27 ms 26 ms 25 ms 41-132-8-1.dsl.mweb.co.za [41.132.8.1]
2 28 ms 28 ms 30 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
3 31 ms 41 ms 29 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
4 273 ms 272 ms 274 ms 197-82-3-1.dbn.mweb.co.za [197.82.3.1]
5 268 ms 269 ms 270 ms tengig0-0-0-0.vic-p-1.mweb.co.za [197.84.4.38]
6 264 ms 264 ms 264 ms pos0-3-2-0.lon-up-1.mweb.co.za [197.80.5.7]
7 241 ms 241 ms 240 ms 196.22.164.1
8 233 ms 233 ms 235 ms gi0-2-cpt-cinx.mweb.co.za [196.28.178.133]
9 236 ms 234 ms 234 ms google.cinx.net.za [196.223.22.41]
10 234 ms 233 ms 236 ms 64.233.174.105
11 236 ms 234 ms 234 ms cpt01s01-in-f16.1e100.net [74.125.233.16]

Trace complete.

Im from newcastle and experiencing the same issue. Quite frustrating that we have to buy account FROM OTHER ISPs to play.
Regards
 
Yeah its all the MWEB clients that connect via the new Durban Data center as per the OP's post. So that would probably be 90% of KZN?
 
I'm glad im not the only one. It's clearly a problem within the data centre.



Sent from my GT-I9100 using Tapatalk
 
Bloody frustrating, given I complained on Friday already.... Have to use Afrihost to play :(

More irritating is that we have to get "numbers" of people to complain before they take us seriously... not lie I'm a freakin noob who does not know what I'm talking about!
 
So is it too much to expect that Mweb reimburse me the amount spent for having to buy from another ISP.....after all, you cant expect me to pay for an incomplete service in full?
I doubt they'd be so understanding if I were to experience a payment "glitch".

Fix it dammit.
 
Well,Im shocked that mweb cant tell us the fault?Im pretty certain they say technical stays open every day?

Cancel time! This account looking like a big mistake.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X