Latency on web africa

Morning guys,

Had a chat with the DSL Manager this morning.
Apparently we did receive a few calls into Customer Care yesterday about latency, however traffic and packets were running through our network as per normal.

Are any of you still experiencing this?
 
Fulton17 said:
http://www.speedtest.net/result/1115314666.png

I am in Durban

I do not understand trace routes, but here is one to the New York Times:


Tracing route to www.nytimes.com [199.239.136.200]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 11 ms 10 ms ndn-ip-esr-3.ipnet.wa.co.za [41.185.66.1]
3 35 ms 35 ms 34 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 35 ms 34 ms 34 ms vl31.er.gw.cpt.za.wa.co.za [41.185.0.153]
5 35 ms 35 ms 35 ms 41.66.150.177
6 185 ms 184 ms 185 ms 41.66.132.49
7 187 ms * 185 ms vl467.mpd01.lon01.atlas.cogentco.com [149.6.146.
157]
8 186 ms 185 ms 185 ms te3-2.ccr01.lon01.atlas.cogentco.com [130.117.1.
73]
9 266 ms 266 ms 265 ms te0-0-0-4.ccr22.bos01.atlas.cogentco.com [130.11
7.0.46]
10 266 ms 265 ms 266 ms 154.54.44.53
11 266 ms 266 ms 266 ms te2-2.ccr01.jfk07.atlas.cogentco.com [154.54.1.2
18]
12 265 ms 267 ms 265 ms ntt.jfk07.atlas.cogentco.com [154.54.11.66]
13 265 ms 263 ms 264 ms ae-2.r23.nycmny01.us.bb.gin.ntt.net [129.250.4.1
48]
14 265 ms 266 ms 266 ms po-3.r02.nycmny01.us.bb.gin.ntt.net [129.250.2.4
1]
15 365 ms 406 ms 412 ms ge-1-1.a00.nycmny01.us.da.verio.net [129.250.30.
113]
16 * * * Request timed out.
17 * * * Request timed out.
18 128.241.244.54 reports: Destination net unreachable.

Trace complete.
Click to expand...

Hi Tinuva,

I would appreciate your comments on my trace route as I am not really too sure how to read them? Thanks so much
 
DIJ031

Today seems reasonable, however trying to reach secure M$oft sites yesterday, was hit and miss...


Tracing route to bbc.co.uk [212.58.224.138] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 6 ms 6 ms wbs-ip-esr-4.ipnet.wa.co.za [41.185.86.1]
3 8 ms 8 ms 7 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 8 ms 8 ms 8 ms vl31.er.gw.cpt.za.wa.co.za [41.185.0.153]
5 9 ms 7 ms 8 ms 41.66.150.177
6 159 ms 160 ms 166 ms 41.66.132.49
7 296 ms 171 ms 159 ms vl467.mpd01.lon01.atlas.cogentco.com [149.6.146.157]
8 160 ms 162 ms 162 ms te2-1.3493.mpd02.lon01.atlas.cogentco.com [130.117.2.18]
9 160 ms 159 ms 160 ms ldn-b4-link.telia.net [213.248.70.237]
10 163 ms 160 ms 159 ms ldn-bb1-link.telia.net [80.91.252.197]
11 159 ms 162 ms 170 ms ldn-b3-link.telia.net [80.91.251.165]
12 161 ms 162 ms 180 ms siemens-ic-119241-ldn-b2.c.telia.net [213.248.104.70]
13 166 ms 160 ms 160 ms 212.58.238.149
14 159 ms 160 ms 160 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.


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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 7 ms 6 ms wbs-ip-esr-4.ipnet.wa.co.za [41.185.86.1]
3 9 ms 8 ms 8 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 8 ms 8 ms 8 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
5 9 ms 8 ms 9 ms wa-acc1.wadns.net [196.220.39.253]
6 11 ms 11 ms 75 ms 196.220.58.66


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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 6 ms 5 ms wbs-ip-esr-4.ipnet.wa.co.za [41.185.86.1]
3 8 ms 7 ms 7 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 9 ms 9 ms 8 ms vl30.er.gw.cpt.za.wa.co.za [41.185.0.145]
5 8 ms 7 ms 8 ms 41.66.150.41
6 159 ms 160 ms 159 ms 41.66.132.49
7 159 ms 178 ms * vl467.mpd01.lon01.atlas.cogentco.com [149.6.146.157]
8 160 ms 160 ms 159 ms te3-1.mpd02.lon01.atlas.cogentco.com [130.117.2.26]
9 233 ms 233 ms 239 ms te0-2-0-4.ccr21.bos01.atlas.cogentco.com [66.28.4.189]
10 239 ms 239 ms 240 ms te0-0-0-3.mpd21.jfk02.atlas.cogentco.com [154.54.6.2]
11 245 ms 245 ms 245 ms te0-3-0-6.mpd21.dca01.atlas.cogentco.com [154.54.41.21]
12 247 ms 245 ms 246 ms te0-3-0-1.mpd21.iad02.atlas.cogentco.com [154.54.41.242]
13 250 ms 248 ms 245 ms 206.111.0.229.ptr.us.xo.net [206.111.0.229]
14 253 ms 247 ms 259 ms vb2000d1.rar3.washington-dc.us.xo.net [207.88.13.62]
15 260 ms 260 ms 260 ms ae0d0.mcr2.smyrna-ga.us.xo.net [216.156.0.70]
16 259 ms 264 ms 262 ms ae1d0.mcr1.smyrna-ga.us.xo.net [216.156.1.33]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


Tracing route to www.nytimes.com [199.239.136.200] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 7 ms 9 ms wbs-ip-esr-4.ipnet.wa.co.za [41.185.86.1]
3 10 ms 8 ms 8 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 10 ms 8 ms 8 ms vl31.er.gw.cpt.za.wa.co.za [41.185.0.153]
5 17 ms 16 ms 33 ms 41.66.150.177
6 159 ms 162 ms 160 ms 41.66.132.49
7 162 ms 160 ms 159 ms vl467.mpd01.lon01.atlas.cogentco.com [149.6.146.157]
8 160 ms 159 ms 161 ms te3-1.mpd02.lon01.atlas.cogentco.com [130.117.2.26]
9 239 ms 239 ms 238 ms te0-3-0-4.ccr21.bos01.atlas.cogentco.com [154.54.30.129]
10 242 ms 246 ms 239 ms 154.54.44.25
11 239 ms 238 ms 241 ms te8-7.ccr01.jfk07.atlas.cogentco.com [154.54.1.222]
12 239 ms 238 ms 239 ms ntt.jfk07.atlas.cogentco.com [154.54.11.66]
13 243 ms 238 ms 241 ms ae-2.r22.nycmny01.us.bb.gin.ntt.net [129.250.4.174]
14 * * * Request timed out.
15 348 ms 247 ms 243 ms ge-1-2.a00.nycmny01.us.da.verio.net [129.250.30.193]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 128.241.244.54 reports: Destination net unreachable.

Trace complete.


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.1
2 6 ms 6 ms 6 ms wbs-ip-esr-4.ipnet.wa.co.za [41.185.86.1]
3 7 ms 7 ms 7 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
4 9 ms 7 ms 8 ms vl35.er.gw.cpt.za.wa.co.za [41.185.0.38]
5 8 ms 8 ms 7 ms upstream.vl102.gw.cpt.za.wa.co.za [196.220.59.230]
6 8 ms 12 ms 8 ms wblv-ip-essr-1-atm-2-0-0-1.telkom-ipnet.co.za [196.43.11.22]
7 9 ms 9 ms 8 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.
 
Last edited:
Fulton17 said:
Hi Tinuva,

I would appreciate your comments on my trace route as I am not really too sure how to read them? Thanks so much
Click to expand...
Yours look fine all the way up to the ISP network, where it seems that things go south. Your line and exchange looks 100%, as well as the exchange to the ISP looks 100%.
 
Durandal said:
Strange that it shows us in Pretoria North, as we are based in the Randburg CBD, Johannesburg. Maybe that's where WA's Gauteng connection is based. We were also told at the time that the whole peering thing with MWEB would affect us here, as WA had two separate ...for lack of better word, 'bases'. The CT one was okay because they could peer there, but not so the JHB one, so we were going to be slower. Don't know if that is still applicable, because the whole peering thing seems to have gone quiet.
Click to expand...
tprn-ip-esr-2.ipnet.wa.co.za

tprn is saix's name for Transvaal Pretoria North as far as I remember.

WA doesn't have any network equipment in Gauteng, so from what I can tell, your line somehow goes from Randburg to Pretoria North exchange (strange...) and then from there it goes to Cape Town. I think that could explain a lot why you have such a bad experience, your connection is going all over the place before it even reaches the internet.

In my personal opinion you have to ask Telkom to fix that and get your line moved to a closer exchange, thats horrible routing imho.
 
As much as there may be a problem, what I can say is I am impressed with WA giving a response and being interested in solving the problem.
I did a tracert and ping test last night to bbc.co.uk.
This all seems fine with ping's at around 200-250ms
ping bbc.co.uk -t for about 15 minutes had only 2 packets lost, which is ok.

I was using a test account from WA though. before 6pm I was getting the wow freeze ups and high latecy but not as bad as it was on my own account.
After 6PM the lag spikes went away and the rest of the evening was fine.

upstream SNR and attenuation is 12 which is good
downstream is 28 SNR & 25 attenuation which is ok
 
Tinuva said:
tprn-ip-esr-2.ipnet.wa.co.za

tprn is saix's name for Transvaal Pretoria North as far as I remember.

WA doesn't have any network equipment in Gauteng, so from what I can tell, your line somehow goes from Randburg to Pretoria North exchange (strange...) and then from there it goes to Cape Town. I think that could explain a lot why you have such a bad experience, your connection is going all over the place before it even reaches the internet.

In my personal opinion you have to ask Telkom to fix that and get your line moved to a closer exchange, thats horrible routing imho.
Click to expand...

Well, I've PMed Jeff to see if they can detect anything their side. Our experience with WA was initially very good, then around the middle of last year it started to slow down, sort of stabilised, but since the start of work this year it's been awful. Possibly the rain has caused problems as well, who knows? But it's an exercise in futility the moment you bring Telkom into the picture - WA blames them, they blame WA, WA insists it's Telkom, Telkom insists it is WA... Reset modem, carry out tests I've had to do a gazillion times on the router...and you end up with everyone just shrugging their shoulders. The last time I spent two hours on the phone with no suitable resolution to the problem.
 
Well look I am not trying to blame anyone, but I can say that a JHB line shouldn't route through a PTA-North exchange. Sadly, no ISP will be able to get this changed for you other than Telkom themselves.
 
Tinuva said:
Well look I am not trying to blame anyone, but I can say that a JHB line shouldn't route through a PTA-North exchange. Sadly, no ISP will be able to get this changed for you other than Telkom themselves.
Click to expand...

Will see if I can maybe find a technician to email directly instead of going through the front line masses.
 
Durandal said:
Well, I've PMed Jeff to see if they can detect anything their side. Our experience with WA was initially very good, then around the middle of last year it started to slow down, sort of stabilised, but since the start of work this year it's been awful. Possibly the rain has caused problems as well, who knows? But it's an exercise in futility the moment you bring Telkom into the picture - WA blames them, they blame WA, WA insists it's Telkom, Telkom insists it is WA... Reset modem, carry out tests I've had to do a gazillion times on the router...and you end up with everyone just shrugging their shoulders. The last time I spent two hours on the phone with no suitable resolution to the problem.
Click to expand...

Thanks for the PM.
Had a look at it now and need all I have.

Will have a look at a few things from our end to see what's going on :)
If need be, I'll have a DSL consultant give you a shout for further troubleshooting.
 
Tinuva said:
Yours look fine all the way up to the ISP network, where it seems that things go south. Your line and exchange looks 100%, as well as the exchange to the ISP looks 100%.
Click to expand...

Thanks Tinuva.

I will be following up with WA
 
Durandal said:
Well, I've PMed Jeff to see if they can detect anything their side. Our experience with WA was initially very good, then around the middle of last year it started to slow down, sort of stabilised, but since the start of work this year it's been awful. Possibly the rain has caused problems as well, who knows? But it's an exercise in futility the moment you bring Telkom into the picture - WA blames them, they blame WA, WA insists it's Telkom, Telkom insists it is WA... Reset modem, carry out tests I've had to do a gazillion times on the router...and you end up with everyone just shrugging their shoulders. The last time I spent two hours on the phone with no suitable resolution to the problem.
Click to expand...

Heya Durandal,

I believe we've got to the bottom of this one?
Confirmed it's a line fault that is causing all these issues :(
 
Durandal said:
That and a weird route to Cape Town. Now the joy of trying to explain it to Telkom *sigh*
Click to expand...

Wish we could help out a little more.
Maybe you can consider moving your DSL line to WA? That completely skips the Telkom step as we can log faults for you ;)
 
WAJeff said:
Wish we could help out a little more.
Maybe you can consider moving your DSL line to WA? That completely skips the Telkom step as we can log faults for you ;)
Click to expand...

Ha, speaking to Telkom now - he says that's what you guys were supposed to do, lol, log it with them on my behalf.... Anyhow, he's working on it as we speak and there seems to be some improvement already, so crossing fingers and holding thumbs.
 
Durandal said:
Ha, speaking to Telkom now - he says that's what you guys were supposed to do, lol, log it with them on my behalf.... Anyhow, he's working on it as we speak and there seems to be some improvement already, so crossing fingers and holding thumbs.
Click to expand...

*sigh*
The Telkom guy seems a little confused. We can only ever log line faults if the line has been transferred to us. Which unfortunately isn't the case here :(
 
WAJeff said:
*sigh*
The Telkom guy seems a little confused. We can only ever log line faults if the line has been transferred to us. Which unfortunately isn't the case here :(
Click to expand...

Explain the implications of this? Costs, what's involved? It might be better for us to do that.
 
Durandal said:
Explain the implications of this? Costs, what's involved? It might be better for us to do that.
Click to expand...

It's stacks easier!
Price wise, depends on your data usage and line speed. You can have a look at our Complete range here for some pricing options.
All these include line rental with some awesome add-ons :D

If you like, I can get one of our Sales dudes or dude'ts to give you a shout for some further options?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X