Bad Latency on MWEB 4mb uncapped

milomak · May 30, 2010

Here are my ping results

Code:

--- sabela.saix.net ping statistics ---
53 packets transmitted, 53 received, 0% packet loss, time 52074ms
rtt min/avg/max/mdev = 15.774/39.655/92.096/13.147 ms

and traceroutre

Code:

$ traceroute sabela.saix.net -t 50
traceroute to sabela.saix.net (196.43.1.9), 30 hops max, 60 byte packets
 1  upstairs (192.168.1.1)  2.418 ms  2.632 ms  2.877 ms
 2  41-133-84-1.dsl.mweb.co.za (41.133.84.1)  22.854 ms  23.090 ms  23.281 ms
 3  tengig-0-0-0-107.vic-ipc-1.mweb.co.za (196.22.169.158)  31.760 ms  35.068 ms  37.504 ms
 4  vl-92.vic-hscore-2.mweb.co.za (196.22.189.3)  31.264 ms  33.540 ms  35.689 ms
 5  tengig-0-0-0-0-11.vic-up-1.mweb.co.za (196.22.169.225)  39.803 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za (196.22.169.241)  68.138 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za (196.22.169.225)  46.736 ms
 6  rrba-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.8.249)  46.092 ms  57.812 ms  58.055 ms
 7  rrba-ip-essr-2-ge-4-1.telkom-ipnet.co.za (196.43.23.106)  62.744 ms  21.332 ms  27.385 ms
 8  sabela.saix.net (196.43.1.9)  14.194 ms  16.247 ms  18.736 ms

Gordon_R · Jun 1, 2010

Gordon_R said:

Local latency has been fine for weeks, but suddenly it has gotten very slow this evening. I'm in Kenilworth, Cape Town.

Code:

Tracing route to sabela.saix.net [196.43.1.9]
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   142 ms   144 ms   145 ms  tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.169.134]
   4    83 ms    81 ms    85 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
   5   118 ms   116 ms   118 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
   6   100 ms   100 ms    93 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
   7    60 ms    59 ms    57 ms  rrba-ip-essr-1-ge-4-1.telkom-ipnet.co.za [196.43.23.102]
   8    72 ms    73 ms    75 ms  sabela.saix.net [196.43.1.9]

Trace complete.

Bad latency again at lunchtime on Tuesday.

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

1 1 ms <10 ms <10 ms home.gateway [192.168.1.254]
2 8 ms 10 ms 8 ms 41-132-48-1.dsl.mweb.co.za [41.132.48.1]
3 247 ms 247 ms 244 ms tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.169.134]
4 250 ms 253 ms 253 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 182 ms 181 ms 185 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 154 ms 157 ms 156 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 258 ms 263 ms 252 ms rrba-ip-essr-1-ge-4-1.telkom-ipnet.co.za [196.43.23.102]
8 160 ms 157 ms 160 ms sabela.saix.net [196.43.1.9]

Trace complete.

Edit: Around 14h00 latency seemed to return to 'normal'...

vinnigepiet · Jun 1, 2010

./wondering if this is still being looked at by Mweb....

killadoob · Jun 2, 2010

I think it may finally be fixed, yesterday average pings of nearly 200, today:

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

saffakanera · Jun 2, 2010

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

1 4 ms 1 ms 3 ms home.gateway [192.168.1.254]
2 9 ms 8 ms 8 ms 41-132-20-1.dsl.mweb.co.za [41.132.20.1]
3 176 ms 172 ms 171 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.16
3.206]
4 183 ms 186 ms 190 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 237 ms 241 ms 243 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 158 ms 163 ms 163 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
7 110 ms 111 ms 111 ms rrba-ip-essr-1-ge-4-1.telkom-ipnet.co.za [196.43
.23.102]
8 250 ms 254 ms 253 ms sabela.saix.net [196.43.1.9]

Trace complete.

joeyhza · Jun 2, 2010

I'm in the same boat as most of the people - experiencing extremely horrific service from these A$swipes and i'm getting more and more fukkked off with these stooopid kuntts.....i've experienced max download speeds of <50Kb/s for the past 3 days, phoned mweb and telkom repeatedly today . ....no effin joy!!!!! And to think i actually pay my bills timeously for this effin crap service . . . fukkkk you MWEB -
Way to go MWEB - proving that you guys can offer the world and actually deliver for 2 days in an entire month - I so wish we had other options so i could phone MWEB support and tell them they can suck my KOKK and fukkkk off with their ****tttyyyy service -

Apologies for my tone - but i'm sick and tired - and all those people that tell me that i can cancel my subscription so they can benefit from one less MWEB user and have an overall better internet experience - i say - wake up...smell the roses - one less person aint gonna make a difference to your internet experience - hell a 100 000 less people wont - you know why - mWEB is just out to make money - load up on as many subscriptions - split the load and see how far and feasible it can be till they can the service - throw it out as an unfeasible venture yet extremely profitable venture while it lasted.

I would strongly discourage new DSL user to go the MWEB route - rather support a less crappy Service Provider. There are none out that are good enough - but theres tons out there thats less crappy than the FUKKKNUTS!

aj11 · Jun 2, 2010

LOL! NNTP speeds are like really sucky.

joeyhza · Jun 2, 2010

yeah...thats ONLY 'coz MWEB are really sucky

Gordon_R · Jun 3, 2010

Ignoring the silly posts above...

This morning I'm getting bad latency on MWeb-Telkom links (and local sites incl myBB), but fine on SEACOM, SAT-3, JINX-TENET, etc.

Code:

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

   1   <10 ms   <10 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    33 ms    33 ms    34 ms  tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.169.134]
   4    33 ms    33 ms    33 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
   5    40 ms    36 ms    44 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
   6   105 ms   105 ms   106 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
   7   103 ms   105 ms   107 ms  rrba-ip-essr-2-ge-4-1.telkom-ipnet.co.za [196.43.23.106]
   8   126 ms   132 ms   130 ms  sabela.saix.net [196.43.1.9]

Trace complete.

Update: Half an hour later latency seems to be back to normal. I can only suggest that congestion on particular lines causes these 'spikes'.

Adenoid Hynkel · Jun 7, 2010

Been getting this since i signed up with mweb.

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

1 * * * Request timed out.
2 9 ms 9 ms 9 ms 41-133-102-1.dsl.mweb.co.za [41.133.102.1]
3 156 ms 163 ms 164 ms tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.16
9.134]
4 198 ms 189 ms 188 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 188 ms 188 ms 190 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 199 ms 206 ms 204 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
7 220 ms 225 ms 231 ms rrba-ip-essr-1-ge-4-1.telkom-ipnet.co.za [196.43
.23.102]
8 202 ms 202 ms 201 ms sabela.saix.net [196.43.1.9]

Trace complete.

LennZA · Jun 7, 2010

Mweb Business UNSHAPED uncapped 4096 (Telkom Line rental) :

Code:

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

  1    <1 ms    <1 ms    <1 ms  10.0.0.2
  2   139 ms   139 ms   140 ms  tengig-0-0-0.vic-lns-2.mweb.co.za [196.22.189.12]
  3   123 ms   122 ms   120 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  4   186 ms   174 ms   206 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
  5   248 ms   243 ms   237 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
  6   250 ms   264 ms   268 ms  rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.43.8.198]
  7   226 ms   223 ms   220 ms  196.43.25.138
  8   265 ms   270 ms   274 ms  ge0-2.br1.jnb6.za.mtnbusiness.net [196.30.16.181]
  9   266 ms   260 ms   248 ms  ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
 10   246 ms   411 ms   252 ms  vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
 11   414 ms   420 ms   417 ms  196.30.213.108
 12   390 ms   377 ms   378 ms  firewall1.jnb2.host-h.net [196.7.216.173]
 13   389 ms   394 ms   400 ms  mybroadband.co.za [41.203.21.136]

Trace complete.

Code:

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

  1    <1 ms    <1 ms    <1 ms  10.0.0.2
  2   136 ms   139 ms   139 ms  tengig-0-0-0.vic-lns-2.mweb.co.za [196.22.189.12]
  3   133 ms   141 ms   142 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  4   158 ms   156 ms   158 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
  5   196 ms   204 ms   207 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
  6   205 ms   213 ms   213 ms  rrba-ip-essr-1-ge-4-1.telkom-ipnet.co.za [196.43.23.102]
  7   221 ms   218 ms   222 ms  sabela.saix.net [196.43.1.9]

Trace complete.

Code:

Pinging games.saix.net [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=178ms TTL=247
Reply from 196.43.22.222: bytes=32 time=171ms TTL=247
Reply from 196.43.22.222: bytes=32 time=167ms TTL=247
Reply from 196.43.22.222: bytes=32 time=153ms TTL=247

From Pretoria [Static IP : 41.134.32.201]

Gordon_R · Jun 7, 2010

It's gotten much worse this afternoon, over 200ms latency from CT-Jhb...

Code:

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

   1   <10 ms   <10 ms   <10 ms  home.gateway [192.168.1.254]
   2     8 ms     8 ms     7 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
   3   164 ms   158 ms   153 ms  tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.169.134]
   4   172 ms   181 ms   182 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
   5   200 ms   206 ms   226 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
   6   193 ms   193 ms   196 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
   7   179 ms   176 ms   174 ms  rrba-ip-essr-2-ge-4-1.telkom-ipnet.co.za [196.43.23.106]
   8   209 ms   215 ms   215 ms  sabela.saix.net [196.43.1.9]

Trace complete.

Update: The JINX traffic grpah between 13h00 and 15h00 looks like someone took a 'bite' out of it!!
http://stats.jinx.net.za/

By 17h30 latency seems back to normal. Must be congestion...

killadoob · Jun 7, 2010

Going to be fun gaming tonight

Pinging games.saix.net [196.43.22.222] with 32 bytes of
Reply from 196.43.22.222: bytes=32 time=295ms TTL=245
Request timed out.
Reply from 196.43.22.222: bytes=32 time=257ms TTL=245
Reply from 196.43.22.222: bytes=32 time=275ms TTL=245

mika1000 · Jun 7, 2010

Request timed out.

BrendanMc · Jun 7, 2010

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

1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]
2 * * * Request timed out.
3 151 ms 154 ms 155 ms tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.16
3.218]
4 175 ms 177 ms 171 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 156 ms 151 ms 144 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 134 ms 133 ms 129 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
7 177 ms 173 ms 173 ms rrba-ip-essr-1-ge-4-1.telkom-ipnet.co.za [196.43
.23.102]
8 146 ms 146 ms 146 ms sabela.saix.net [196.43.1.9]

Trace complete.

Bothasig Cape Town....Yippeee

killadoob · Jun 7, 2010

You think you have it bad

20:22. I thought hmmm some bfbc2 would be nice then bam!!!!!!!!

Pinging games.saix.net [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=298ms TTL=245
Reply from 196.43.22.222: bytes=32 time=277ms TTL=245
Reply from 196.43.22.222: bytes=32 time=276ms TTL=245
Reply from 196.43.22.222: bytes=32 time=288ms TTL=245

Adenoid Hynkel · Jun 7, 2010

Pinging games.saix.net [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=226ms TTL=245
Reply from 196.43.22.222: bytes=32 time=274ms TTL=245
Reply from 196.43.22.222: bytes=32 time=202ms TTL=245
Reply from 196.43.22.222: bytes=32 time=220ms TTL=245
Reply from 196.43.22.222: bytes=32 time=220ms TTL=245
Reply from 196.43.22.222: bytes=32 time=215ms TTL=245
Reply from 196.43.22.222: bytes=32 time=297ms TTL=245
Reply from 196.43.22.222: bytes=32 time=430ms TTL=245
Reply from 196.43.22.222: bytes=32 time=388ms TTL=245
Reply from 196.43.22.222: bytes=32 time=276ms TTL=245
Reply from 196.43.22.222: bytes=32 time=372ms TTL=245
Reply from 196.43.22.222: bytes=32 time=387ms TTL=245
Reply from 196.43.22.222: bytes=32 time=334ms TTL=245
Reply from 196.43.22.222: bytes=32 time=238ms TTL=245
Reply from 196.43.22.222: bytes=32 time=256ms TTL=245

FFS mweb, do somethig about this!!!!!!

techead · Jun 7, 2010

im trying to play hon on a LOCAL SERVER on 250ms

FFS

killadoob · Jun 7, 2010

Can you guys test another provider?

I get the same pings with my axxesslite account.

killadoob · Jun 7, 2010

Ok axxesslite

Reply from 196.43.22.222: bytes=32 time=105ms TTL=244
Reply from 196.43.22.222: bytes=32 time=132ms TTL=244
Reply from 196.43.22.222: bytes=32 time=104ms TTL=244
Reply from 196.43.22.222: bytes=32 time=112ms TTL=244

Much better

Pinging games.saix.net [196.43.22.222] with 32 bytes of
Reply from 196.43.22.222: bytes=32 time=132ms TTL=244
Reply from 196.43.22.222: bytes=32 time=76ms TTL=244
Reply from 196.43.22.222: bytes=32 time=38ms TTL=244
Reply from 196.43.22.222: bytes=32 time=117ms TTL=244

I normally get 13ms

, i would be happy with consistent 40. I have seen 13ms on mweb when seacom is down hahahahah

Join the MyBroadband community

Get started

Bad Latency on MWEB 4mb uncapped

Honorary Master

Honorary Master

Well-Known Member

Honorary Master

Expert Member

Senior Member

Member

Senior Member

Honorary Master

Executive Member

Member

Honorary Master

Honorary Master

Expert Member

Expert Member

Honorary Master

Executive Member

Honorary Master

Honorary Master

Honorary Master