Poor latency and international speeds.

vinodh

vinodh

Expert Member
Joined
Jan 11, 2009
Messages
2,979
Reaction score
31
Location
Centurion
I've been experiencing really bad international speeds and latency recently.

Here's a ping test:

PING www.gpvwc.com (66.7.212.109): 56 data bytes
64 bytes from 66.7.212.109: icmp_seq=0 ttl=46 time=342.833 ms
64 bytes from 66.7.212.109: icmp_seq=1 ttl=46 time=410.263 ms
64 bytes from 66.7.212.109: icmp_seq=2 ttl=46 time=457.251 ms
64 bytes from 66.7.212.109: icmp_seq=3 ttl=46 time=363.316 ms
64 bytes from 66.7.212.109: icmp_seq=4 ttl=46 time=303.427 ms
64 bytes from 66.7.212.109: icmp_seq=5 ttl=46 time=286.323 ms
64 bytes from 66.7.212.109: icmp_seq=6 ttl=46 time=301.686 ms
64 bytes from 66.7.212.109: icmp_seq=7 ttl=46 time=295.896 ms
64 bytes from 66.7.212.109: icmp_seq=8 ttl=46 time=291.064 ms
64 bytes from 66.7.212.109: icmp_seq=9 ttl=46 time=349.335 ms
64 bytes from 66.7.212.109: icmp_seq=10 ttl=46 time=710.666 ms
Request timeout for icmp_seq 11
64 bytes from 66.7.212.109: icmp_seq=11 ttl=46 time=1227.713 ms
64 bytes from 66.7.212.109: icmp_seq=12 ttl=46 time=388.374 ms
Request timeout for icmp_seq 14
64 bytes from 66.7.212.109: icmp_seq=13 ttl=46 time=2263.616 ms
64 bytes from 66.7.212.109: icmp_seq=14 ttl=46 time=1338.646 ms
64 bytes from 66.7.212.109: icmp_seq=15 ttl=46 time=600.683 ms
64 bytes from 66.7.212.109: icmp_seq=16 ttl=46 time=2044.588 ms
64 bytes from 66.7.212.109: icmp_seq=17 ttl=46 time=1283.187 ms
64 bytes from 66.7.212.109: icmp_seq=18 ttl=46 time=974.393 ms
64 bytes from 66.7.212.109: icmp_seq=19 ttl=46 time=895.759 ms
64 bytes from 66.7.212.109: icmp_seq=20 ttl=46 time=372.039 ms
64 bytes from 66.7.212.109: icmp_seq=21 ttl=46 time=395.040 ms
64 bytes from 66.7.212.109: icmp_seq=22 ttl=46 time=406.102 ms

Traceroute:

traceroute to www.iracing.com (54.243.35.169), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 1.746 ms 1.238 ms 1.290 ms
2 41-133-94-1.dsl.mweb.co.za (41.133.94.1) 15.849 ms 24.993 ms 105.246 ms
3 197-80-96-186.jhb.mweb.co.za (197.80.96.186) 21.740 ms 61.832 ms 57.321 ms
4 vl-92-vic-hscore-1.mweb.co.za (197.80.2.1) 37.852 ms 61.743 ms 41.633 ms
5 tengig-0-0-0-2-11-vic-p-1.mweb.co.za (197.80.5.225) 597.046 ms 406.872 ms 490.326 ms
6 s2-pos0-3-0-0-pos0-3-2-0-thd-p-2.mweb.co.za (197.80.5.7) 307.588 ms 202.021 ms 253.108 ms
7 be-3-777-thd-up-1.mweb.co.za (176.67.177.131) 3822.849 ms 614.111 ms 1843.008 ms
8 xe-8-3-1.edge3.london1.level3.net (195.50.124.133) 220.847 ms 194.249 ms 189.944 ms
9 * * *

Video streaming and gaming is now impossible. I called Telkom and they did a port reset but it made no difference. I switched to my free FNB account and it did the same thing.
 
Here'a ping test to mybroadband:

Ping has started…

PING www.mybroadband.co.za (197.242.89.170): 56 data bytes
64 bytes from 197.242.89.170: icmp_seq=0 ttl=52 time=258.190 ms
Request timeout for icmp_seq 1
64 bytes from 197.242.89.170: icmp_seq=1 ttl=52 time=1260.974 ms
64 bytes from 197.242.89.170: icmp_seq=2 ttl=52 time=1489.276 ms
64 bytes from 197.242.89.170: icmp_seq=3 ttl=52 time=486.537 ms
64 bytes from 197.242.89.170: icmp_seq=4 ttl=52 time=12.613 ms
64 bytes from 197.242.89.170: icmp_seq=5 ttl=52 time=21.367 ms
64 bytes from 197.242.89.170: icmp_seq=6 ttl=52 time=37.615 ms
64 bytes from 197.242.89.170: icmp_seq=7 ttl=52 time=36.569 ms
64 bytes from 197.242.89.170: icmp_seq=8 ttl=52 time=75.305 ms
64 bytes from 197.242.89.170: icmp_seq=9 ttl=52 time=14.116 ms
64 bytes from 197.242.89.170: icmp_seq=10 ttl=52 time=28.929 ms
64 bytes from 197.242.89.170: icmp_seq=11 ttl=52 time=59.075 ms
64 bytes from 197.242.89.170: icmp_seq=12 ttl=52 time=249.268 ms
64 bytes from 197.242.89.170: icmp_seq=13 ttl=52 time=113.143 ms
64 bytes from 197.242.89.170: icmp_seq=14 ttl=52 time=15.540 ms
64 bytes from 197.242.89.170: icmp_seq=15 ttl=52 time=142.063 ms
64 bytes from 197.242.89.170: icmp_seq=16 ttl=52 time=25.342 ms
64 bytes from 197.242.89.170: icmp_seq=17 ttl=52 time=35.834 ms
64 bytes from 197.242.89.170: icmp_seq=18 ttl=52 time=115.274 ms
64 bytes from 197.242.89.170: icmp_seq=19 ttl=52 time=61.006 ms
64 bytes from 197.242.89.170: icmp_seq=20 ttl=52 time=110.241 ms
64 bytes from 197.242.89.170: icmp_seq=21 ttl=52 time=21.374 ms
64 bytes from 197.242.89.170: icmp_seq=22 ttl=52 time=40.755 ms
64 bytes from 197.242.89.170: icmp_seq=23 ttl=52 time=16.684 ms
64 bytes from 197.242.89.170: icmp_seq=24 ttl=52 time=1083.454 ms
Request timeout for icmp_seq 26
64 bytes from 197.242.89.170: icmp_seq=25 ttl=52 time=2687.425 ms
64 bytes from 197.242.89.170: icmp_seq=26 ttl=52 time=1687.960 ms
64 bytes from 197.242.89.170: icmp_seq=27 ttl=52 time=683.933 ms
64 bytes from 197.242.89.170: icmp_seq=28 ttl=52 time=23.838 ms
64 bytes from 197.242.89.170: icmp_seq=29 ttl=52 time=520.657 ms
64 bytes from 197.242.89.170: icmp_seq=30 ttl=52 time=121.304 ms
64 bytes from 197.242.89.170: icmp_seq=31 ttl=52 time=529.489 ms

Traceroute to mybroadband:

traceroute to www.mybroadband.co.za (197.242.89.170), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 2.550 ms 1.418 ms 1.248 ms
2 41-133-94-1.dsl.mweb.co.za (41.133.94.1) 143.547 ms 12.983 ms 14.375 ms
3 197-80-96-186.jhb.mweb.co.za (197.80.96.186) 15.224 ms 50.028 ms 11.203 ms
4 vl-92-vic-hscore-1.mweb.co.za (197.80.2.1) 55.875 ms 8.382 ms 34.473 ms
5 tengig-0-0-0-2-11-vic-p-2.mweb.co.za (197.80.5.226) 14.835 ms 18.060 ms 68.254 ms
6 197-80-7-38.jhb.mweb.co.za (197.80.7.38) 16.515 ms 11.947 ms 97.549 ms
7 africainx.jb1.napafrica.net (196.46.25.135) 11.795 ms 9.019 ms 185.623 ms
8 core.gp-cn-het-mee-1.to.gp-hv-ict-mee-1.dfa.p2p.10g.za (41.84.13.66) 135.699 ms 35.580 ms 38.774 ms
9 41-66-132-246-f6.het001-cpe-1-to-gp-cn-het-mee-1.africainx.net (41.66.132.246) 111.819 ms 63.086 ms 550.681 ms
10 core-access-switch1.jnb1.host-h.net (197.189.193.1) 21.928 ms 12.929 ms 11.146 ms
11 row-access-switch1-row3-4.jnb1.host-h.net (197.189.193.36) 13.476 ms 20.032 ms 14.181 ms
12 197.242.89.170 (197.242.89.170) 12.947 ms 63.892 ms 26.098 ms
 
Looks like it could be exchange related, ping seems a bit high after it leaves the router.

Although wait for someone else to confirm this - in the meantime perhaps try a different ISP and see whether you have the same issue or not. WebAfrica's free 1GB account should work well :)
 
PsyCLown said:
Looks like it could be exchange related, ping seems a bit high after it leaves the router.

Although wait for someone else to confirm this - in the meantime perhaps try a different ISP and see whether you have the same issue or not. WebAfrica's free 1GB account should work well :)
Click to expand...

I tried the WebAfrica account as you suggested but it was the same. It's really frustrating but all I can do now is wait...
 
Reason I am suspecting exchange issue is due to the 2nd hop from the tracert:
2 41-133-94-1.dsl.mweb.co.za (41.133.94.1) 15.849 ms 24.993 ms 105.246 ms

I have heard that the 1st hop outside of your home network (once it leaves the router basically) is the exchange.
It isn't very consistent and most seem to get lower pings than 24 and 105ms.

When you say that the same happens on a different ISP then I think it is fairly safe to rule out the ISP if there are no known issues with the ISP's you tested.

I'd say drop TelkomZA a PM but they seem to be MIA recently :( You can try on Twitter though.
It may actually be an issue with your port on the exchange and not exchange congestion I guess.
 
Last edited:
JustinB said:
is it intermittent?
Click to expand...

Yes. Sometimes late in the evening it stabilises but it's bad most of the time.


PsyCLown said:
Reason I am suspecting exchange issue is due to the 2nd hop from the tracert:
2 41-133-94-1.dsl.mweb.co.za (41.133.94.1) 15.849 ms 24.993 ms 105.246 ms

I have heard that the 1st hop outside of your home network (once it leaves the router basically) is the exchange.
It isn't very consistent and most seem to get lower pings than 24 and 105ms.

When you say that the same happens on a different ISP then I think it is fairly safe to rule out the ISP if there are no known issues with the ISP's you tested.

I'd say drop TelkomZA a PM but they seem to be MIA recently :( You can try on Twitter though.
It may actually be an issue with your port on the exchange and not exchange congestion I guess.
Click to expand...

I did get Telkom to do a port reset but if anything, it made it worse. I did PM TelkomZA but I did not get an answer. The first time it happened, he replied but by then the problem was gone for a day or two. Since then, the problem has been there almost permanently but TelkomZA has not replied again after two more PM's.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X