LATENCY!!!

acidrain said:
You are so lucky 506 :(

Seems like it's definitely dslam related then
Click to expand...

Well - it could be higher up in the chain. But I wouldn't call 506 lucky yet. I also had some fantastic ping times the past couple of weeks. This problem does not seem to be very consistent. I also suspect it is not normal congestion - because it doesn't seem like the ping times degrade linearly, they seem to be bad or good - with no middle ground. Also - the latency seems to be time-dependent, but not dependent on traditional business hours. I have horrible latency right now - Sunday night.

What would be an interesting experiment is to get a couple of the affected people to get dyndns addresses, and then let a central person run pings from a stable connection to these affected users and get decent statistics.
 
Johand said:
Well - it could be higher up in the chain.
Click to expand...

What makes me think he is lucky, is he's 3rd hop is exactly the same as mine ( and my problems start there ) so seems something between me and that hop is causing the problem.

What would be an interesting experiment is to get a couple of the affected people to get dyndns addresses, and then let a central person run pings from a stable connection to these affected users and get decent statistics.
Click to expand...

I'm already on dyndns so wouldn't mind trying it out
 
acidrain said:
What makes me think he is lucky, is he's 3rd hop is exactly the same as mine ( and my problems start there ) so seems something between me and that hop is causing the problem.
Click to expand...

Was actually referring to the fact that he might have done the traceroutes at a time where the problem didn't manifest and that he might get hit at any time. I would however be careful when trying to interpret the traceroute paths - Telkom's use of VRF in IPConnect can make it slightly difficult. When trying the different ISPs the problem manifests itself tat different hop-counts.
 
My ping times are down to 9ms at 7am this morning, so it's almost certainly congestion related.

It's been 'up and down' for more than a week now, so I'm assuming the problem will be back later today.

This is the first time I have 'benefited' from MWeb's Cape Town based IPC, although to be honest there are only a very small number of sites based in the Cape (UCT, etc).
 
Yep mine is back to normal again too - it dropped off at 11:10pm and by 11:54pm it was back to normal. I've been testing to an IS gaming server (using ping Plotter) but I would like to use the same IP for testing that everyone else is using, to get a proper comparison. Gordon_R - which IP were you using this morning?
 
teRRRier said:
Yep mine is back to normal again too - it dropped off at 11:10pm and by 11:54pm it was back to normal. I've been testing to an IS gaming server (using ping Plotter) but I would like to use the same IP for testing that everyone else is using, to get a proper comparison. Gordon_R - which IP were you using this morning?
Click to expand...

Several local routes seem to give the same result. (BTW: MWeb seems to have at least 2 major IPC routes in CT).

Here are 2 tracerts, but as you say, between hop 2 and 3 there are a lot of intermediate steps:

Code: 
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

   1   <10 ms   <10 ms     1 ms  home.gateway [192.168.1.254]
   2     7 ms     8 ms     7 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
   3     7 ms     7 ms     7 ms  196-28-178-166.adsl.mweb.co.za [196.28.178.166]
   4     8 ms     8 ms     8 ms  196.41.144.36
   5     8 ms     8 ms     9 ms  www.mweb.co.za [196.2.63.110]

Trace complete.

Code: 
Tracing route to tenet.cinx.net.za [198.32.214.33]
over a maximum of 30 hops:

   1   <10 ms   <10 ms   <10 ms  home.gateway [192.168.1.254]
   2     7 ms     7 ms     7 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
   3     8 ms     8 ms     8 ms  196-28-178-202.adsl.mweb.co.za [196.28.178.202]
   4     9 ms     9 ms     9 ms  196-28-178-133.adsl.mweb.co.za [196.28.178.133]
   5     9 ms     9 ms    26 ms  tenet.cinx.net.za [198.32.214.33]

Trace complete.
 
Latency has started creeping up at 8.45am. It's not sudden, since it first hit 20ms, then 40ms, and its sporadic, since it rises and falls.

Up to 40-60ms at 8.47am. Back to 15ms at 8.49am. Up to 25ms at 8.50am. Down to 9ms at 8.51am. Etc...

I also checked and it happens simultaneously on both MWeb IPC routers (196-28-178-166.adsl.mweb.co.za and 196-28-178-202.adsl.mweb.co.za).
 
It is 100% not ISP related. It is happening on Mweb/Axxess/Afrihost/WebAfrica/Telkom Accounts.

It is also happening to all users and when I spoke to a Telkom Dslam technician he told me that during those times there are routing the "traffic" from the Dslam that are being upgraded to the "Higher" latency ones.
As far as I know, this is not going to be sorted any time soon. I wish it does, but it is highly unlikely, Over the last 6 weeks its just been happening more and more, and for more users at various Dslams. The technician told me Telkom will only look at " Disconnects " and " speed issues" as a problem. Latency is not regarded as a Problem as you line speed is still full.
 
jpmonster said:
It is 100% not ISP related. It is happening on Mweb/Axxess/Afrihost/WebAfrica/Telkom Accounts.

It is also happening to all users and when I spoke to a Telkom Dslam technician he told me that during those times there are routing the "traffic" from the Dslam that are being upgraded to the "Higher" latency ones.
As far as I know, this is not going to be sorted any time soon. I wish it does, but it is highly unlikely, Over the last 6 weeks its just been happening more and more, and for more users at various Dslams. The technician told me Telkom will only look at " Disconnects " and " speed issues" as a problem. Latency is not regarded as a Problem as you line speed is still full.
Click to expand...

Latency and jitter is one of their KPI's, but as far as I understand they just have to publish it - they are not required to maintain it. Government Gazette Notice http://www.info.gov.za/view/DownloadFileAction?id=58376. Telkom's KPI's are published at http://www.telkom.co.za/products_services/dsl/conditions.html.
 
They have not posted it for the 2nd Quarter at all. The problem with those stats is that it is probably being done from there offices. Its not a Graph of different areas and different times.

I tried reading a bit of the stuff and yup they do not need to maintain them, just post them to the public, which they have done. I mean even if there stats are totally off the rocks, no one really checks these at all.

In the Gov Notice,

Port Prioritisation

Telkom, SNO and lSPs shall not be allowed to impose port prioritisation on their
subscribers.

There must be an updated version of this, because all our ISP's Prioritise ports and state them on there sites
 
Here are statistics from my side for Cape Town CBD



Pinging www.saix.net [196.25.1.200] with 32 bytes of data:
Reply from 196.25.1.200: bytes=32 time=317ms TTL=250
Reply from 196.25.1.200: bytes=32 time=283ms TTL=250
Reply from 196.25.1.200: bytes=32 time=274ms TTL=250
Reply from 196.25.1.200: bytes=32 time=286ms TTL=250

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 274ms, Maximum = 317ms, Average = 290ms

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

1 292 ms 289 ms 327 ms dsl-144-152-01.telkomadsl.co.za [41.144.152.1]
2 339 ms 331 ms 271 ms wblv-ip-essr-1-atm-2-0-0-1.telkom-ipnet.co.za [1
96.43.11.22]
3 283 ms 286 ms 244 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.

Hope this helps Will@MWEB
 
Cape Town, Table View (021-557). On WebAfrica

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

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

Pinging webafrica.co.za [196.220.58.66] with 32 bytes of data:
Reply from 196.220.58.66: bytes=32 time=127ms TTL=121
Reply from 196.220.58.66: bytes=32 time=118ms TTL=121
Reply from 196.220.58.66: bytes=32 time=126ms TTL=121
Reply from 196.220.58.66: bytes=32 time=114ms 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 = 114ms, Maximum = 127ms, Average = 121ms

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=125ms TTL=246
Reply from 196.43.22.222: bytes=32 time=128ms TTL=246
Reply from 196.43.22.222: bytes=32 time=116ms TTL=246
Reply from 196.43.22.222: bytes=32 time=120ms 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 = 116ms, Maximum = 128ms, Average = 122ms

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

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

  1     6 ms     7 ms     6 ms  dsl-185-88-1.dynamic.wa.co.za [41.185.88.1]
  2     8 ms     8 ms     8 ms  vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
  3     9 ms     8 ms     8 ms  vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
  4     8 ms     8 ms     8 ms  vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
  5   101 ms   109 ms   107 ms  fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
  6   103 ms    97 ms   102 ms  wa-acc1.wadns.net [196.220.39.253]
  7    86 ms    81 ms    81 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     8 ms     8 ms  vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
  3     9 ms     8 ms     8 ms  vl35.er.gw.cpt.za.wa.co.za [41.185.0.38]
  4    78 ms    79 ms    80 ms  upstream.vl102.gw.cpt.za.wa.co.za [196.220.59.23
0]
  5   120 ms   113 ms   117 ms  rrba-ip-esr-1-pos-8-0-0.telkom-ipnet.co.za [196.
43.8.146]
  6   117 ms   119 ms   117 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
  7   122 ms   120 ms   117 ms  nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
  8   110 ms   111 ms   110 ms  nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.
 
I like how they report their national average latency....they can basically pick the best 9 ESR's for their report and thus always look good.
If their attitude is to not give a *** about latency, then my money won't give a *** about reaching their bank accounts anymore :D
 
LoL. Well I am going to see until the end of the month. That will be 2 months of this.
 
Tracing route to 41.185.60.18 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms home.gateway [10.0.0.2]
2 * * * Request timed out.
3 9 ms 8 ms 8 ms 196-28-178-166.adsl.mweb.co.za [196.28.178.166]
4 9 ms 10 ms 9 ms 196-28-178-133.adsl.mweb.co.za [196.28.178.133]
5 10 ms 10 ms 10 ms 198.32.214.45
6 10 ms 11 ms 11 ms vl40.cr.gw.cpt.za.wa.co.za [41.185.0.97]
7 12 ms 11 ms 11 ms 41.185.60.18

Trace complete.

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

1 <1 ms <1 ms <1 ms home.gateway [10.0.0.2]
2 * * * Request timed out.
3 8 ms 8 ms 8 ms 196-28-178-202.adsl.mweb.co.za [196.28.178.202]
4 9 ms 8 ms 8 ms 196.41.144.36
5 11 ms 14 ms 14 ms www.mweb.co.za [196.2.63.110]

Trace complete.

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

1 <1 ms <1 ms <1 ms home.gateway [10.0.0.2]
2 * * * Request timed out.
3 9 ms 10 ms 9 ms 196-28-178-166.adsl.mweb.co.za [196.28.178.166]
4 33 ms 33 ms 33 ms 196.22.169.49
5 34 ms 33 ms 33 ms 196.22.169.61
6 76 ms 78 ms 75 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
7 34 ms 33 ms 34 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
8 33 ms 33 ms 33 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
9 34 ms 34 ms 34 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
10 36 ms 36 ms 36 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
11 36 ms 36 ms 35 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

Still ok
 
Any1 got any updates on this? It's getting bloody annoying that my local pings are the same as my international pings.
 
yup my pings to saix are high again. Seems to be night time related though since this afternoon it was low
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X