WebAfrica/Vumatel Latency Issue

[Sn00zE]

Hi Guys,

Been getting strange latency issues for the last 2 and half weeks. In Cape Town on Webafrica/Vumatel fiber latency issues starting from around 19:30 and lasts most of the evening to around midnight. On weekends this starts around 17:00 - 18:00 in the evening. Playing international games become impossible. Have a ticket open with WA for a few days now, but not much coming from it. Any one else having latency issues?

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 1 ms 1 ms 196-212-63-1.wa.co.za [196.212.63.1]
3 1 ms 1 ms 1 ms 196.38.74.43
4 1 ms 1 ms 1 ms 196.35.115.140
5 1 ms 1 ms 1 ms mi-za-cpt-p7-te0-0-0-0.ip.isnet.net [168.209.6.12]
6 380 ms 334 ms 339 ms 168.209.100.101
7 25 ms 27 ms 28 ms 196.26.0.130
8 17 ms 18 ms 17 ms 72.14.205.16
9 31 ms 32 ms 32 ms 72.14.239.33
10 24 ms 23 ms 21 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.

Tracing route to google.com [216.58.223.46]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 1 ms <1 ms 196-212-63-1.wa.co.za [196.212.63.1]
3 1 ms 1 ms 1 ms 196.38.74.43
4 1 ms 1 ms 1 ms 196.35.115.140
5 1 ms 2 ms 1 ms mi-za-cpt-p7-te0-0-0-0.ip.isnet.net [168.209.6.12]
6 551 ms 489 ms 535 ms 168.209.100.101
7 168 ms 174 ms 165 ms pr2-pkl-xe-2-2-0.ip.isnet.net [168.209.1.179]
8 17 ms 17 ms 17 ms 72.14.205.16
9 19 ms 18 ms 17 ms 72.14.239.129
10 17 ms 17 ms 17 ms jnb01s08-in-f46.1e100.net [216.58.223.46]
Trace complete.

 

[websquadza]

Hi.
Besides the funny hops between their Cape Town core and what looks like Parklands IS in Joburg, your ping to the destination servers actually seems alright (+- 20ms Cape Town to Joburg).

Remember, the latency is measured from your router to each of those addresses, so a ping to each individual address on a path might be different to the continuous path taken by a packet. This happens if the advertised route to that device isn't advertised to the nearest routers directly. IE, their cape town core knows that Google sits behind hop 9, so the packet follows that path. But their cape town core learns that pkl-xe (parklands core)... is being advertised on an aggregated route (usually an upstream peering router), and if you ping that specific IP, it's quite a long route. You'll want to check for packet losses. Run an app called Win-MTR for a minute or two during peak and offpeak times and post those results. If you see packet loss, capacity between JHB and Cape Town is problematic, hence your problems.

 

[DERoestorf]

Hi Guys,

Been getting strange latency issues for the last 2 and half weeks. In Cape Town on Webafrica/Vumatel fiber latency issues starting from around 19:30 and lasts most of the evening to around midnight. On weekends this starts around 17:00 - 18:00 in the evening. Playing international games become impossible. Have a ticket open with WA for a few days now, but not much coming from it. Any one else having latency issues?

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 1 ms 1 ms 196-212-63-1.wa.co.za [196.212.63.1]
3 1 ms 1 ms 1 ms 196.38.74.43
4 1 ms 1 ms 1 ms 196.35.115.140
5 1 ms 1 ms 1 ms mi-za-cpt-p7-te0-0-0-0.ip.isnet.net [168.209.6.12]
6 380 ms 334 ms 339 ms 168.209.100.101
7 25 ms 27 ms 28 ms 196.26.0.130
8 17 ms 18 ms 17 ms 72.14.205.16
9 31 ms 32 ms 32 ms 72.14.239.33
10 24 ms 23 ms 21 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.

Tracing route to google.com [216.58.223.46]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 1 ms <1 ms 196-212-63-1.wa.co.za [196.212.63.1]
3 1 ms 1 ms 1 ms 196.38.74.43
4 1 ms 1 ms 1 ms 196.35.115.140
5 1 ms 2 ms 1 ms mi-za-cpt-p7-te0-0-0-0.ip.isnet.net [168.209.6.12]
6 551 ms 489 ms 535 ms 168.209.100.101
7 168 ms 174 ms 165 ms pr2-pkl-xe-2-2-0.ip.isnet.net [168.209.1.179]
8 17 ms 17 ms 17 ms 72.14.205.16
9 19 ms 18 ms 17 ms 72.14.239.129
10 17 ms 17 ms 17 ms jnb01s08-in-f46.1e100.net [216.58.223.46]
Trace complete.

Don't waste your time, switch to a proper fibre ISP. They won't ever admit it, but is comes down to capacity on their side.

I can recommend Cool Ideas from personal experience

 

[Sn00zE]

Thanks for the recommendations guys.

Ran MTR from my router just after i got home and then continuously till everything started slowing down at around 20:30..

Will look at CoolIdeas also if not resolved by end of October.

Below the results.

18:30
Forgot to do a speedtest but its usually around 1ms ping, 50Mbps Down and 50Mbps Up maxed.


20:30
Speedtest also http://www.speedtest.net/result/7722550421

 

[Sn00zE]

Then 22:15 it recovers by itself

 

[websquadza]

@Sn00zE thanks for posting these MTRs. They paint quite a picture. If you look at hop 4/5 on all the traceroutes, they're situated in Cape Town and the latencies are all over the place, with peak times adding 50ms to local (Cape Town only) routes. As an ISP, we won't comment more, but @DERoestorf hit the nail on the head, so to speak.

 

[Sn00zE]

MTR makes things so much clearer. Route 4/5 seems to be the biggest issue, if you add route 4's additional 150ms on top of the international route it explains the latency issues I'm experiencing with gaming I guess.

Lastnight was especially terrible again as it even impacted the browsing experience.

Can someone on Cool Ideas run MTR report on that VPN route at around 20:30 tonight and post results please?

@Sn00zE thanks for posting these MTRs. They paint quite a picture. If you look at hop 4/5 on all the traceroutes, they're situated in Cape Town and the latencies are all over the place, with peak times adding 50ms to local (Cape Town only) routes. As an ISP, we won't comment more, but @DERoestorf hit the nail on the head, so to speak.