Bad Latency on MWEB 4mb uncapped

>tracert sabela.saix.net

Tracing route to sabela.saix.net [196.43.1.9]over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 11 ms 8 ms 41-133-108-0.dsl.mweb.co.za [41.133.108.0]
3 159 ms 159 ms 155 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 160 ms 159 ms 163 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 118 ms 118 ms 120 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 149 ms 141 ms 137 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 167 ms 166 ms 172 ms rrba-ip-essr-1-ge-4-1.telkom-ipnet.co.za [196.43.23.102]
8 108 ms 108 ms 102 ms sabela.saix.net [196.43.1.9]

>ping games.saix.net

Pinging games.saix.net [196.43.22.222] with 32 bytes of data:
Request timed out.
Reply from 196.43.22.222: bytes=32 time=145ms TTL=245
Reply from 196.43.22.222: bytes=32 time=139ms TTL=245
Reply from 196.43.22.222: bytes=32 time=144ms TTL=245

Ping statistics for 196.43.22.222:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 139ms, Maximum = 145ms, Average = 142ms

So much for Uncapped - cancelling MWEB Uncapped - it just doesnt deliver, constantly blaming Telkom, Neotel and Seacom.
 
This uncapped service sucks... even if you accept the shaping with torrents and NZB's - the damn pings are so high that even online gaming sucks!
 
gdiza said:
This uncapped service sucks... even if you accept the shaping with torrents and NZB's - the damn pings are so high that even online gaming sucks!
Click to expand...

Yup i could live with the shaping of p2p as the general service was good but the last month or so i cannot even game locally!!!!!!

Oddly enough when seacom is having problems my ping returns to 13ms.
 
Have seen an improvement in the past half hour check yours: (not great but definitely better)

Webpages still take +/- 20 seconds to load though.

>tracert sabela.saix.net

Tracing route to sabela.saix.net [196.43.1.9] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 7 ms 41-133-108-1.dsl.mweb.co.za [41.133.108.1]
3 120 ms 118 ms 119 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 29 ms 28 ms 29 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 50 ms 32 ms 31 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 122 ms 126 ms 123 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 99 ms 98 ms 100 ms rrba-ip-essr-1-ge-4-1.telkom-ipnet.co.za [196.43.23.102]
8 29 ms 29 ms 29 ms sabela.saix.net [196.43.1.9]

>ping games.saix.net

Pinging games.saix.net [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=33ms TTL=245
Reply from 196.43.22.222: bytes=32 time=33ms TTL=245
Reply from 196.43.22.222: bytes=32 time=31ms TTL=245
Reply from 196.43.22.222: bytes=32 time=31ms TTL=245

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

who.is.michael said:
>tracert sabela.saix.net

Tracing route to sabela.saix.net [196.43.1.9]over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 11 ms 8 ms 41-133-108-0.dsl.mweb.co.za [41.133.108.0]
3 159 ms 159 ms 155 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 160 ms 159 ms 163 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 118 ms 118 ms 120 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 149 ms 141 ms 137 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 167 ms 166 ms 172 ms rrba-ip-essr-1-ge-4-1.telkom-ipnet.co.za [196.43.23.102]
8 108 ms 108 ms 102 ms sabela.saix.net [196.43.1.9]

>ping games.saix.net

Pinging games.saix.net [196.43.22.222] with 32 bytes of data:
Request timed out.
Reply from 196.43.22.222: bytes=32 time=145ms TTL=245
Reply from 196.43.22.222: bytes=32 time=139ms TTL=245
Reply from 196.43.22.222: bytes=32 time=144ms TTL=245

Ping statistics for 196.43.22.222:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 139ms, Maximum = 145ms, Average = 142ms

So much for Uncapped - cancelling MWEB Uncapped - it just doesnt deliver, constantly blaming Telkom, Neotel and Seacom.
Click to expand...
 
I find when they are working on the seacom thing it comes right, when they say they have finished working it is crap again.

Hahah not sure how it works.
 
Ping01.jpg

Here is my ping to the Left 4 Dead 2 servers.
Igame is the only decent one there.
 
Back down to 15ms local tonight, 350ms international. That's how it should be! :)
 
Latency is abnormally high tonight. Normally I get consistent 33ms local latencies and 260ms to Europe, but tonight latency seems to be up about 100ms across the board.

I still have an Axxess account and latency seems fine there.
 
This morning I have an example showing that much of the current bottleneck on MWeb is due to congestion on the Telkom circuit. In this case latency to the SAIX DNS server (400ms) is twice that (via SEACOM) to the BBC in London!!?

Code: 
Tracing route to sabela.saix.net [196.43.1.9]
over a maximum of 30 hops:

   1   <10 ms     1 ms   <10 ms  home.gateway [192.168.1.254]
   2     8 ms     8 ms     9 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
   3    28 ms    29 ms    29 ms  tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.163.218]
   4   106 ms   113 ms   118 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
   5    93 ms    82 ms    48 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
   6   472 ms   469 ms   471 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
   7   469 ms   467 ms   471 ms  rrba-ip-essr-1-ge-4-1.telkom-ipnet.co.za [196.43.23.102]
   8   477 ms   475 ms   474 ms  sabela.saix.net [196.43.1.9]

Trace complete.

5 mins later the latency is back down to 100 ms. Weird...
 
lol, everyday 5 PM i cant game anymore on COD, HoN, WoW, but when the shaping is at the fullest during business hours i can game download etc without any issues full kb/s
 
My ping times have been fairly stable during the World Cup, but suddenly today (Tues 29th) when there is a very big game (Spain v Portugal) in Cape Town, latency between CT and MWeb-VIC is terrible! I guess this is congestion, but anyway...

Code: 
Tracing route to www.dstv.com [196.28.65.142]
over a maximum of 30 hops:

   1   <10 ms   <10 ms   <10 ms  home.gateway [192.168.1.254]
   2     8 ms     8 ms     8 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
   3   227 ms   225 ms   227 ms  tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
   4   104 ms   102 ms   103 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
   5   155 ms   152 ms   147 ms  tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.66]
   6   185 ms   187 ms   192 ms  135.75.28.196.netactive.net [196.28.75.135]
   7   195 ms   196 ms   201 ms  192.168.196.17
   8   243 ms   246 ms   249 ms  www.dstv.com [196.28.65.142]

Trace complete.
 
Similar here:
Code: 
Tracing route to mybroadband.co.za [41.203.21.136]
over a maximum of 30 hops:

  1    <1 ms    <1 ms     1 ms  router [192.168.1.1]
  2    17 ms    16 ms    15 ms  41-133-132-1.dsl.mweb.co.za [41.133.132.1]
  3   370 ms   361 ms   368 ms  tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
  4   364 ms   360 ms   355 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5   463 ms   455 ms   446 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
  6   342 ms   345 ms   345 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
  7   436 ms   445 ms   453 ms  rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.
43.8.198]
  8   369 ms   371 ms   371 ms  196.43.25.138
  9   406 ms   403 ms   402 ms  ge0-2.br1.jnb6.za.mtnbusiness.net [196.30.16.181
]
 10   396 ms   400 ms   399 ms  196.30.1.21
 11   382 ms   393 ms   387 ms  vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
 12   450 ms   458 ms   493 ms  196.30.213.108
 13   473 ms   480 ms   486 ms  firewall2.jnb2.host-h.net [196.7.216.174]
 14   401 ms   394 ms   401 ms  mybroadband.co.za [41.203.21.136]

Trace complete.
 
Same from Durban to JHB today :/

Tracing route to sip.voip.mweb.net [196.28.95.12] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Billion.800VGT [172.16.65.254]
2 20 ms 28 ms 20 ms 41-132-8-1.dsl.mweb.co.za [41.132.8.1]
3 337 ms 340 ms 332 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
4 305 ms 323 ms 318 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 253 ms 247 ms 251 ms tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.66]
6 260 ms 256 ms 264 ms wavestream.20 [196.44.195.20]
7 281 ms 285 ms 292 ms sip.voip.mweb.net [196.28.95.12]

Trace complete.

Switching to an IS 10GB account yeild's better results :)

Tracing route to sip.voip.mweb.net [196.28.95.12] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Billion.800VGT [172.16.65.254]
2 159 ms 41 ms 32 ms 196-210-132-1.dynamic.isadsl.co.za [196.210.132.1]
3 66 ms 257 ms 60 ms cdsl1-rba-vl2360.ip.isnet.net [196.38.73.133]
4 36 ms 39 ms 38 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 39 ms 36 ms 43 ms core5a-rba-gi1-0-0.ip.isnet.net [168.209.1.164]
6 107 ms 111 ms 43 ms 196.26.0.10
7 37 ms 38 ms 40 ms rrba-ip-spe-2-wan.telkom-ipnet.co.za [196.25.127.181]
8 44 ms 41 ms 37 ms 196.43.25.137
9 38 ms 37 ms 40 ms 196.43.51.6
10 41 ms 42 ms 51 ms mweb-gw.telkom-ipnet.co.za [196.25.8.250]
11 36 ms 40 ms 38 ms vl-11.vic-hscore-1.mweb.co.za [196.22.169.227]
12 113 ms 108 ms 113 ms tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.66]
13 40 ms 38 ms 39 ms wavestream.20 [196.44.195.20]
14 43 ms 38 ms 39 ms sip.voip.mweb.net [196.28.95.12]

Trace complete.

Definitely something not cosy with MWEB today.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X