LATENCY!!!

i am slowly getting the hang of this "testing of speed" business ... anybody care to explain to me in one sentence the diffs between a Ping test and a Tracert test?
 
dagwood4455 said:
i am slowly getting the hang of this "testing of speed" business ... anybody care to explain to me in one sentence the diffs between a Ping test and a Tracert test?
Click to expand...

To put it very simply, a ping test is a test of the round trip delay to a node and back. A traceroute is a list of ping tests to all nodes along the way to the destination node.
 
LoL@nicomz.

Maybe someone should rename this thread to, CT-Latency Issues

Thanks for the feedback Will, really appreciate the effort
 
**Update**

Apologies my post earlier was inaccurate - I did actually receive some feedback very late this afternoon that hit my mailbox in between the office and home. Apparently there is a link error and traffic has been diverted so that it can be repaired without service disruption. I will be requesting clarity on what that entails and the ETA. I've also been asked to resubmit evidence indicating that the problem is still current so please fire away with fresh traces if you are reading and have a moment :)

@nicomz We understand your frustration, I know that you have had strong opinions about our uncapped products for quite some time now and I respect that, but I can assure you that there is no hidden agenda at work here. Unless you consider a geniune concern for improving the service delivery to all our customers and trying to make the Internet better for every South African to be an agenda.
 
I am not on MWEB but I am on the Clareinch exchange (021 671) and I am getting the same latency issues as other users.

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

  1     5 ms     5 ms     6 ms  41.0.60.1 
  2   277 ms   183 ms   189 ms  41.0.9.214 
  3   169 ms   164 ms   167 ms  41.0.72.1 
  4   159 ms   155 ms   151 ms  41.0.9.61 
  5   166 ms   166 ms   178 ms  41.0.0.5 
  6   176 ms   186 ms   190 ms  rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.253.109] 
  7   186 ms   180 ms   172 ms  wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30] 
  8   185 ms   194 ms   192 ms  wblv-ip-www-1.saix.net [196.25.1.200] 

Trace complete.

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

  1    <1 ms    <1 ms    <1 ms  home.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   169 ms   161 ms   159 ms  cdsl2-rba-vl2663.ip.isnet.net [196.38.73.25] 
  4   158 ms   163 ms   169 ms  cdsl2-rba-vl150.ip.isnet.net [196.38.73.9] 
  5   179 ms   171 ms   163 ms  196.26.0.61 
  6   171 ms   184 ms   243 ms  196.26.0.10 
  7   160 ms   150 ms   142 ms  rrba-ip-spe-2-wan.telkom-ipnet.co.za [196.25.127.181] 
  8   181 ms   185 ms   184 ms  196.43.25.137 
  9   189 ms   178 ms   170 ms  wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30] 
 10   186 ms   192 ms   192 ms  wblv-ip-www-1.saix.net [196.25.1.200] 

Trace complete.

Thank you Will@mweb for your effort in trying to get Telkom to acknowledge the problem.
 
Thanks Chris, those are consistent with my own readings and it's my pleasure :)
 
Will@MWEB said:
I've also been asked to resubmit evidence indicating that the problem is still current so please fire away with fresh traces if you are reading and have a moment :)
Click to expand...

Gladly :)
I'm in Plumstead and on the Wynberg Exchange (021 797)
I'm not using an MWeb account, but with a Webafrica account:

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

1 19 ms 16 ms 16 ms dsl-185-88-1.dynamic.wa.co.za [41.185.88.1]
2 18 ms 18 ms 20 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
3 21 ms 22 ms 19 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
4 21 ms 20 ms 22 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
5 129 ms 135 ms 135 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
6 151 ms 151 ms 156 ms wa-acc1.wadns.net [196.220.39.253]
7 166 ms 163 ms 163 ms 196.220.58.66

Trace complete.

And with a Telkom account:

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

1 20 ms 18 ms 20 ms dsl-144-160-01.telkomadsl.co.za [41.144.160.1]
2 192 ms 198 ms 192 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
3 40 ms 39 ms 40 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
4 49 ms 42 ms 42 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
5 185 ms 169 ms 166 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

An with an IS account:

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

1 2 ms 2 ms 2 ms home.gateway [192.168.0.1]
2 19 ms 20 ms 18 ms 196-210-152-1.dynamic.isadsl.co.za [196.210.152.1]
3 193 ms 194 ms 194 ms cdsl1-rba-vl2460.ip.isnet.net [196.38.72.217]
4 216 ms 206 ms 197 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 143 ms 135 ms 125 ms 168.209.1.139
6 182 ms 184 ms 188 ms 168.209.1.170
7 183 ms 192 ms 192 ms rrba-ip-spe-2-wan.telkom-ipnet.co.za [196.25.127.181]
8 190 ms 192 ms 187 ms 196.43.25.137
9 179 ms 190 ms 182 ms rrba-ip-esr-1-pos-8-0-0.telkom-ipnet.co.za [196.43.8.146]
10 211 ms 206 ms 202 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
11 163 ms 168 ms 176 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
12 220 ms 220 ms 208 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.
 
Last edited:
Will@MWEB said:
fire away with fresh traces if you are reading and have a moment :)
Click to expand...
Thanks Will
Tracing route to www.saix.net [196.25.1.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 6 ms 7 ms 41-132-48-1.dsl.mweb.co.za [41.132.48.1]
3 159 ms 166 ms 167 ms 196-28-178-202.adsl.mweb.co.za [196.28.178.202]

4 136 ms 124 ms 141 ms 196.22.169.49
5 157 ms 168 ms 173 ms 196.22.169.61
6 198 ms 192 ms 204 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
7 147 ms 143 ms 136 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
8 166 ms 172 ms 188 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
9 195 ms 200 ms 207 ms wblv-ip-www-1.saix.net [196.25.1.200]

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

1 1 ms 1 ms 1 ms rb.toady.ctwug.za.net [172.18.42.110]
2 8 ms 7 ms 8 ms 41-132-48-1.dsl.mweb.co.za [41.132.48.1]
3 99 ms 97 ms 101 ms 196-28-178-166.adsl.mweb.co.za [196.28.178.166]

4 136 ms 148 ms 150 ms 196.22.169.41
5 232 ms 226 ms 202 ms 196.22.169.61
6 175 ms 187 ms 183 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
7 164 ms 152 ms 165 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
8 207 ms 212 ms 203 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
9 184 ms 180 ms 173 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.
 
That's almost under 100ms acidrain, be careful or you won't be able to be in our club anymore :D
 
jpmonster said:
LoL@nicomz.

Maybe someone should rename this thread to, CT-Latency Issues

Thanks for the feedback Will, really appreciate the effort
Click to expand...


I kinda like the three exclamation marks :-)

Will - we will probably owe you a case of beer/bottle of something nice/or a cow's worth of biltong if you manage to sort this out (what is MWeb's policy on gifts? :-) )


Now for the news everybody is waiting for - Tonight's (23:30) traceroutes on Rondebosch Exchange (021686 xxxx) - WebAfrica network (but this is for information only - I am not knocking them, I am sure this is a Telkom problem so please don't rant about WA based on the result below).

tracert www.webafrica.co.za

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

1 <1 ms <1 ms <1 ms 192.168.66.1
2 7 ms 7 ms 6 ms dsl-185-88-1.dynamic.wa.co.za [41.185.88.1]
3 9 ms 8 ms 8 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 9 ms 8 ms 8 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
5 9 ms 8 ms 8 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
6 160 ms 161 ms 165 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
7 154 ms 157 ms 155 ms wa-acc1.wadns.net [196.220.39.253]
8 131 ms 131 ms 135 ms 196.220.58.66

Trace complete.

International (As far as I know cnn.com doesn't reply to ICMP requests so the last hop does time out normally):

tracert www.cnn.com

Tracing route to www.cnn.com [157.166.255.19]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.66.1
2 6 ms 6 ms 6 ms dsl-185-88-1.dynamic.wa.co.za [41.185.88.1]
3 8 ms 8 ms 8 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 8 ms 8 ms 8 ms vl33.er.gw.cpt.za.wa.co.za [41.185.0.30]
5 154 ms 160 ms 169 ms upstream.vl102.gw.cpt.za.wa.co.za [196.220.59.23
6 368 ms 356 ms 347 ms ams-ip-dir-globalc-gig-1-0-1-1028.telkom-ipnet.c
7 316 ms 337 ms 352 ms 212.72.45.225
8 346 ms 333 ms 333 ms ae-33-51.ebr1.Amsterdam1.Level3.net [4.69.139.12
9 364 ms 353 ms 341 ms ae-48-48.ebr2.Dusseldorf1.Level3.net [4.69.143.2
10 341 ms 343 ms 351 ms ae-1-100.ebr1.Dusseldorf1.Level3.net [4.69.141.1
11 372 ms 341 ms 325 ms ae-47-47.ebr2.Frankfurt1.Level3.net [4.69.143.17
12 454 ms 477 ms 488 ms ae-42-42.ebr2.Washington1.Level3.net [4.69.137.5
13 434 ms 433 ms 427 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.1
14 459 ms 460 ms 449 ms ae-81-81.ebr1.Washington1.Level3.net [4.69.134.1
15 440 ms 443 ms 460 ms ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
16 * 434 ms 446 ms ae-11-51.car1.Atlanta1.Level3.net [4.68.103.2]
17 * * * Request timed out.
 
Last edited:
Will@MWEB said:
That's almost under 100ms acidrain, be careful or you won't be able to be in our club anymore :D
Click to expand...

It seems my time in the club is coming to a close, 3rd hop is slowly creeping down now but I'll wait til tomorrow to re-evaluate my gaming status... hopefully it will be all lights green, then you'll have one less pesty customer for you :D

100ms i can deal with for gaming, so fingers crossed
 
I have a telkom and mweb account... on my mweb uncapped I have latency in excess of 8000ms playing world of warcraft tonight but when I switch to my telkom account my latency is around 250 - 350ms .... explain that!!!

Ps. I play on the US servers and with my webafrica account I cant even connect to wow (permenantly)!!
 
Last edited:
acidrain said:
It seems my time in the club is coming to a close, 3rd hop is slowly creeping down now but I'll wait til tomorrow to re-evaluate my gaming status... hopefully it will be all lights green, then you'll have one less pesty customer for you :D

100ms i can deal with for gaming, so fingers crossed
Click to expand...

Haha - don't count you chickens before they hatched. Latency seem to get better late at nights, and then the problem re-appears the next day!

@23:50

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

1 <1 ms <1 ms <1 ms 192.168.66.1
2 6 ms 6 ms 7 ms dsl-185-88-1.dynamic.wa.co.za [41.185.88.1]
3 8 ms 8 ms 8 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 8 ms 8 ms 8 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
5 8 ms 8 ms 8 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
6 63 ms 61 ms 58 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
7 57 ms 58 ms 60 ms wa-acc1.wadns.net [196.220.39.253]
8 50 ms 51 ms 51 ms 196.220.58.66

Trace complete.

@23:55

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

1 <1 ms <1 ms <1 ms 192.168.66.1
2 7 ms 6 ms 6 ms dsl-185-88-1.dynamic.wa.co.za [41.185.88.1]
3 8 ms 8 ms 8 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 9 ms 8 ms 8 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
5 8 ms 8 ms 9 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
6 56 ms 54 ms 58 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
7 71 ms 67 ms 67 ms wa-acc1.wadns.net [196.220.39.253]
8 73 ms 76 ms 72 ms 196.220.58.66

Trace complete.


@00:00


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

1 <1 ms <1 ms <1 ms 192.168.66.1
2 7 ms 6 ms 6 ms dsl-185-88-1.dynamic.wa.co.za [41.185.88.1]
3 8 ms 8 ms 8 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 10 ms 8 ms 8 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
5 9 ms 8 ms 8 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
6 37 ms 37 ms 36 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
7 38 ms 38 ms 36 ms wa-acc1.wadns.net [196.220.39.253]
8 12 ms 13 ms 12 ms 196.220.58.66

Trace complete.

@00:05 (This results seems nonsensical, but I did gather some ping statistics and it is because the jitter is off the charts).
Tracing route to www.webafrica.co.za [196.220.58.66]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.66.1
2 7 ms 6 ms 6 ms dsl-185-88-1.dynamic.wa.co.za [41.185.88.1]
3 8 ms 8 ms 8 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 8 ms 9 ms 8 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
5 8 ms 8 ms 8 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
6 105 ms 91 ms 91 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
7 70 ms 70 ms 73 ms wa-acc1.wadns.net [196.220.39.253]
8 59 ms 61 ms 65 ms 196.220.58.66

Trace complete.

Ping Stats @ 00:05
Minimum = 27ms, Maximum = 105ms, Average = 67ms
 
Mweb tracert to ccn.com

C:\Windows\system32>tracert cnn.com

Tracing route to cnn.com [157.166.226.25]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * * Request timed out.
3 * 384 ms 365 ms 196-28-178-178.adsl.mweb.co.za [196.28.178.178]

4 249 ms 287 ms 280 ms 196.22.169.41
5 245 ms 245 ms 228 ms 196.22.169.61
6 327 ms 370 ms 390 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
7 383 ms * 401 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]

8 496 ms 549 ms 629 ms PO9-0.lon-001-access-1.interoute.net [89.202.130
.181]
9 577 ms 523 ms 561 ms xe-1-3-0-0.lon-001-score-1-re0.interoute.net [84
.233.218.178]
10 695 ms 626 ms 605 ms 212.113.16.109
11 602 ms 655 ms 662 ms ae-34-52.ebr2.London1.Level3.net [4.69.139.97]
12 642 ms 610 ms 636 ms ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]

13 723 ms 723 ms 691 ms ae-10-10.ebr2.Washington12.Level3.net [4.69.148.
50]
14 642 ms 700 ms 678 ms ae-1-100.ebr1.Washington12.Level3.net [4.69.143.
213]
15 649 ms 620 ms 623 ms ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
16 740 ms 717 ms 752 ms ae-1-51.edge4.Atlanta2.Level3.net [4.68.103.14]

17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.


and games.saix.net

C:\Windows\system32>tracert games.saix.net

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

1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * * Request timed out.
3 364 ms 326 ms 361 ms 196-28-178-190.adsl.mweb.co.za [196.28.178.190]

4 432 ms 426 ms 410 ms 196.22.169.45
5 273 ms 358 ms 439 ms 196.22.169.61
6 413 ms 381 ms 426 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
7 387 ms 425 ms 419 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
8 368 ms 239 ms 227 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.4
3.11.166]
9 304 ms 351 ms 416 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
10 420 ms 393 ms 303 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
11 405 ms 413 ms 407 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.



Trace complete.
 
Last edited:
I've just figured out one possible explanation (irony intended).

The 'alternative routing' that Will@MWeb mentions is actually Winston the pigeon! The South Easter wind has been very strong during the day in Cape Town this week, and gradually calms down during the night. This explains the increased latency at peak periods. Its all to do with the weather, and nothing to do with human factors ;-)
 
Gordon_R said:
I've just figured out one possible explanation (irony intended).

The 'alternative routing' that Will@MWeb mentions is actually Winston the pigeon! The South Easter wind has been very strong during the day in Cape Town this week, and gradually calms down during the night. This explains the increased latency at peak periods. Its all to do with the weather, and nothing to do with human factors ;-)
Click to expand...

zapiro1509_77314d.jpg
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X