LATENCY!!!

Will: Same as everybody else, but I don't have any graphs.

The onset is very erratic, but seems to persist almost the whole day, and worst in the late evenings.

It seems to be correlated to overall traffic, such as this daily CINX graph:
http://stats.cinx.net.za/

P.S. It must be a really crappy router somewhere, if 1Gbps traffic overwhelms it!?
 
Will@MWEB said:
Thanks absynth, my last request for feedback was to try and ascertain the full extent of the fault that has now been acknowledged - it may turn out to be the same issue that's affecting you. If not we'll take it on in the next round.
Click to expand...

Thanks for helping out Will@MWEB!!!!It is very much appreciated:)
 
In the CBD it starts from 9am and at its worst during midday,normally back to normal at about 10pm.

Hope that helps in any way.
 
WA issue not reloved, but better:

Telkom

Tracing route to webafrica.co.za [196.220.58.66] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 <1 ms <1 ms <1 ms 192.168.0.1
3 5 ms 6 ms 6 ms dsl-240-0-01.telkomadsl.co.za [41.240.0.1]
4 5 ms 5 ms 5 ms 196.43.51.26
5 52 ms 59 ms 62 ms vl102.er.gw.cpt.za.wa.co.za [196.220.59.229]
6 45 ms 42 ms 39 ms vl35.cr.gw.cpt.za.wa.co.za [41.185.0.37]
7 40 ms 42 ms 43 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
8 61 ms 61 ms 66 ms wa-acc1.wadns.net [196.220.39.253]
9 12 ms 12 ms 11 ms 196.220.58.66

Trace complete.


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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 <1 ms <1 ms <1 ms 192.168.0.1
3 5 ms 5 ms 5 ms dsl-240-0-01.telkomadsl.co.za [41.240.0.1]
4 6 ms 5 ms 6 ms wblv-ip-lir-1-gig-4-0-0.telkom-ipnet.co.za [196.43.8.190]
5 6 ms 6 ms 6 ms 196.43.25.206
6 12 ms 18 ms 7 ms ge0-3.br2.cpt1.za.mtnbusiness.net [196.7.8.206]
7 39 ms 33 ms 28 ms 196.30.1.21
8 30 ms 31 ms 27 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
9 35 ms 42 ms 29 ms 196.30.213.108
10 28 ms 37 ms 30 ms firewall1.jnb2.host-h.net [196.7.216.173]
11 33 ms 31 ms 34 ms mybroadband.co.za [41.203.21.137]

Trace complete.


WebAfrica

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 4 ms 4 ms 4 ms dsl-185-86-1.dynamic.wa.co.za [41.185.86.1]
3 14 ms 6 ms 7 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 9 ms 7 ms 6 ms vl34.er.gw.cpt.za.wa.co.za [41.185.0.34]
5 7 ms 6 ms 6 ms upstream.vl101.gw.cpt.za.wa.co.za [196.220.59.226]
6 7 ms 6 ms 7 ms wblv-ip-lir-1-gig-4-0-0.telkom-ipnet.co.za [196.43.8.190]
7 7 ms 7 ms 7 ms 196.43.25.206
8 13 ms * * ge0-3.br2.cpt1.za.mtnbusiness.net [196.7.8.206]
9 30 ms 30 ms 38 ms 196.30.1.21
10 30 ms 35 ms 36 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
11 * * * Request timed out.
12 * 35 ms * firewall1.jnb2.host-h.net [196.7.216.173]
13 36 ms 32 ms 32 ms mybroadband.co.za [41.203.21.137]

Trace complete.


Tracing route to webafrica.co.za [196.220.58.66] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 4 ms 5 ms dsl-185-86-1.dynamic.wa.co.za [41.185.86.1]
3 7 ms 6 ms 6 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 7 ms 6 ms 6 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
5 7 ms 6 ms 6 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
6 7 ms 6 ms 6 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
7 7 ms * 7 ms wa-acc1.wadns.net [196.220.39.253]
8 11 ms 7 ms 8 ms 196.220.58.66

Trace complete.
 
Code: 
Tracing route to saix.net [196.25.1.200]
over a maximum of 30 hops:

  1     3 ms     1 ms     1 ms  rb.toady.ctwug.za.net [172.18.42.110]
  2     8 ms     8 ms     9 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
  3   150 ms   142 ms   135 ms  196-28-178-202.adsl.mweb.co.za [196.28.178.202]

  4   160 ms   170 ms   176 ms  196.22.169.49
  5   163 ms   166 ms   166 ms  196.22.169.61
  6   220 ms   232 ms   232 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
  7   183 ms   185 ms   186 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
  8   222 ms   208 ms   196 ms  wblv-ip-essr-1-atm-2-0-0-1.telkom-ipnet.co.za [1
96.43.11.22]
  9   212 ms   209 ms   203 ms  wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.

I think Gordon is on the right track here, seems to be an overload on a router somewhere as its usually good between 00:00 - 09:00, after that it goes pear-shaped for the rest of the day when traffics at its peak
 
Still the same

Below Tracert using Axxess Account @ 4:48

Tracing route to mix.isgaming.co.za [196.38.180.45]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Billion.800VGT [10.0.0.2]
2 8 ms 7 ms 7 ms dsl-242-172-01.telkomadsl.co.za [41.242.172.1]
3 152 ms 156 ms 160 ms cdsl1-rba-vl2460.ip.isnet.net [196.38.72.217]
4 183 ms 180 ms 172 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 156 ms 152 ms 149 ms 196.26.0.60
6 171 ms 167 ms 165 ms 168.209.100.238
7 146 ms 153 ms 159 ms 168.209.218.22
8 169 ms 169 ms 169 ms mix.isgaming.co.za [196.38.180.45]

Trace complete.
 
acidrain said:
Code: 
Tracing route to saix.net [196.25.1.200]
over a maximum of 30 hops:

  1     3 ms     1 ms     1 ms  rb.toady.ctwug.za.net [172.18.42.110]
  2     8 ms     8 ms     9 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
  3   150 ms   142 ms   135 ms  196-28-178-202.adsl.mweb.co.za [196.28.178.202]

  4   160 ms   170 ms   176 ms  196.22.169.49
  5   163 ms   166 ms   166 ms  196.22.169.61
  6   220 ms   232 ms   232 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
  7   183 ms   185 ms   186 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
  8   222 ms   208 ms   196 ms  wblv-ip-essr-1-atm-2-0-0-1.telkom-ipnet.co.za [1
96.43.11.22]
  9   212 ms   209 ms   203 ms  wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.

I think Gordon is on the right track here, seems to be an overload on a router somewhere as its usually good between 00:00 - 09:00, after that it goes pear-shaped for the rest of the day when traffics at its peak
Click to expand...

I think I would have to agree. If you look here, http://stats.cinx.net.za/showtotal.php, under the "last 30 days" graph, it seems to correspond pretty well with when many people started having issues.
 
Webafrica:

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

C:\Users\duaN>ping www.webafrica.co.za

Pinging www.webafrica.co.za [196.220.58.66] with 32 bytes of data:
Reply from 196.220.58.66: bytes=32 time=151ms TTL=121
Reply from 196.220.58.66: bytes=32 time=149ms TTL=121
Reply from 196.220.58.66: bytes=32 time=150ms TTL=121
Reply from 196.220.58.66: bytes=32 time=155ms TTL=121

Ping statistics for 196.220.58.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 149ms, Maximum = 155ms, Average = 151ms

C:\Users\duaN>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=231ms TTL=246
Reply from 196.43.22.222: bytes=32 time=170ms TTL=246
Reply from 196.43.22.222: bytes=32 time=166ms TTL=246
Reply from 196.43.22.222: bytes=32 time=194ms TTL=246

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

C:\Users\duaN>tracert www.webafrica.co.za

Tracing route to www.webafrica.co.za [196.220.58.66]
over a maximum of 30 hops:

1 6 ms 6 ms 6 ms dsl-185-88-1.dynamic.wa.co.za [41.185.88.1]
2 9 ms 8 ms 8 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
3 16 ms 15 ms 13 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
4 19 ms 18 ms 20 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
5 127 ms 133 ms 140 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
6 151 ms 146 ms 140 ms wa-acc1.wadns.net [196.220.39.253]
7 144 ms 145 ms 153 ms 196.220.58.66

Trace complete.

C:\Users\duaN>tracert games.saix.net

Tracing route to games.saix.net [196.43.22.222]
over a maximum of 30 hops:

1 6 ms 6 ms 6 ms dsl-185-88-1.dynamic.wa.co.za [41.185.88.1]
2 8 ms 15 ms 8 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
3 9 ms 8 ms 9 ms vl34.er.gw.cpt.za.wa.co.za [41.185.0.34]
4 156 ms 158 ms 149 ms upstream.vl101.gw.cpt.za.wa.co.za [196.220.59.22
6]
5 188 ms 194 ms 200 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.4
3.11.166]
6 162 ms 163 ms 162 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
7 202 ms 187 ms 179 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
8 187 ms 200 ms 193 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.
 
MWeb, Clareinch, 384k, 2010-10-14 05:20 PM


Code: 
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.254
  2    21 ms    19 ms    19 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
  3   169 ms   173 ms   172 ms  196-28-178-166.adsl.mweb.co.za [196.28.178.166]

  4   151 ms   148 ms   149 ms  196.41.144.36
  5   166 ms   171 ms   177 ms  www.mweb.co.za [196.2.63.110]

Trace complete.


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

  1     1 ms    <1 ms    <1 ms  192.168.1.254
  2    20 ms    19 ms    18 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
  3   171 ms   165 ms   162 ms  196-28-178-166.adsl.mweb.co.za [196.28.178.166]
  4   187 ms   185 ms   189 ms  196.22.169.41
  5   173 ms   177 ms   185 ms  196.22.169.61
  6   214 ms   210 ms   220 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
  7   184 ms   191 ms   191 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
  8   209 ms   194 ms   220 ms  wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30]
  9   186 ms   187 ms   193 ms  wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.
 
raVid said:
I think I would have to agree. If you look here, http://stats.cinx.net.za/showtotal.php, under the "last 30 days" graph, it seems to correspond pretty well with when many people started having issues.
Click to expand...

I intentionally didn't post the 30 days graph, since that seems to coincide with a testing spike done via TENET. That spike had nothing to do with ADSL traffic AFAIK.

The trend in the last 7 days also coincides with MWeb's Cape Town IPC going live, which put extra traffc onto CINX.

Again I must stress that the CINX graph is a 'proxy' for the Southern Suburbs traffic. In fact it really doesn't reflect anything other than cyclical (mostly daily) trends in usage...
 
IS Capped, Clareinch (671)
Code: 
Tracing route to www.saix.net [196.25.1.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  jacobs.local [10.9.8.2] 
  2     7 ms     6 ms     6 ms  196-209-24-1.dynamic.isadsl.co.za [196.209.24.1] 
  3   171 ms   170 ms   163 ms  cdsl1-rba-vl2460.ip.isnet.net [196.38.72.217] 
  4   155 ms   157 ms   158 ms  cdsl1-rba-vl150.ip.isnet.net [196.38.73.17] 
  5   136 ms   141 ms   142 ms  168.209.1.139 
  6   161 ms   158 ms   167 ms  196.26.0.130 
  7   169 ms   157 ms   160 ms  rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.46.89] 
  8   154 ms   150 ms   155 ms  196.43.25.137 
  9   174 ms   170 ms   167 ms  wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30] 
 10   176 ms   179 ms   184 ms  wblv-ip-www-1.saix.net [196.25.1.200] 
Trace complete.

Openweb uncapped gold (Vodacom)
Code: 
Tracing route to www.saix.net [196.25.1.200]
over a maximum of 30 hops:

  1     6 ms     6 ms     5 ms  41.0.60.1 
  2   158 ms   164 ms   165 ms  41.0.9.214 
  3   153 ms   155 ms   161 ms  41.0.72.1 
  4   169 ms   178 ms   179 ms  41.0.9.61 
  5   154 ms   176 ms   157 ms  41.0.0.5 
  6   155 ms   185 ms   163 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.253.109] 
  7   183 ms   181 ms   181 ms  wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30] 
  8   188 ms   187 ms   189 ms  wblv-ip-www-1.saix.net [196.25.1.200] 

Trace complete.
 
WebAfrica's connetivity is better but not quite what it was:

Ping statistics for 196.25.1.200:
Packets: Sent = 243, Received = 243, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 29ms, Average = 7ms (normally constant at 4 ms and occasionally fluctuate by 1 ms)

Ping statistics for 196.220.58.66:
Packets: Sent = 186, Received = 186, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 24ms, Average = 7ms (normally constant at 4 ms and occasionally fluctuate by 1 ms)
 
teRRRier said:
Lets see if this works. It's a link to a 48Hrs graph from my Ping Plotter. http://img829.imageshack.us/img829/9489/tenetcinxnetza.png

It runs a tracert every 5s - you can see how it deteriorates during the day.
Click to expand...

Nice graph! That coincides exactly with my individual measurements during the recent 48 hours...

BTW: The gateway tenet.cinx.net.za is certainly the closest and fastest route out of the Southern Suburbs IMO. I also tried is.cinx.net.za, which is much slower for some reason...
 
Last edited:
I wish I could "like" the graph. That's definitely the same pattern for our latency issues.
 
jpmonster said:
Someone please rename this to Southern Suburb CT LATENCY !!!
Click to expand...

No need to be rude.Ive been on this thread for awhile now and its affecting more areas in Cape Town than just the Southern Suburbs.The more people the quicker it could get sorted.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X