Packet loss to Japan?

Forums › Spark New Zealand (including Skinny and BigPipe) › Packet loss to Japan?

jeeg

351 posts

Ultimate Geek

#127517 13-Aug-2013 12:38

Recently I've been getting timeouts while access Japan located websites, and youtube videos posted from Japan before getting cached seems to suffer from stutter.

I'm currently on VDSL and I understand my ping may be higher due to distance from exchange, but I wasn't getting these timeouts a few weeks ago.

I've pinged a few ip addresses and here are my results.

Final Fantasy XIV Japan datacenter
PING 202.67.53.202 (202.67.53.202): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 202.67.53.202: icmp_seq=1 ttl=45 time=241.526 ms
64 bytes from 202.67.53.202: icmp_seq=2 ttl=45 time=245.461 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 202.67.53.202: icmp_seq=5 ttl=45 time=247.927 ms
64 bytes from 202.67.53.202: icmp_seq=6 ttl=45 time=224.542 ms
Request timeout for icmp_seq 7
64 bytes from 202.67.53.202: icmp_seq=8 ttl=45 time=281.678 ms
64 bytes from 202.67.53.202: icmp_seq=9 ttl=45 time=281.172 ms
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
64 bytes from 202.67.53.202: icmp_seq=12 ttl=45 time=234.168 ms
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
64 bytes from 202.67.53.202: icmp_seq=16 ttl=45 time=291.421 ms
Request timeout for icmp_seq 17
64 bytes from 202.67.53.202: icmp_seq=18 ttl=45 time=251.157 ms
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
64 bytes from 202.67.53.202: icmp_seq=21 ttl=45 time=275.692 ms
^C
--- 202.67.53.202 ping statistics ---
22 packets transmitted, 10 packets received, 54.5% packet loss
round-trip min/avg/max/stddev = 224.542/257.474/291.421/21.884 ms

Yahoo JP
PING yahoo.co.jp (124.83.187.140): 56 data bytes
64 bytes from 124.83.187.140: icmp_seq=0 ttl=47 time=190.889 ms
64 bytes from 124.83.187.140: icmp_seq=1 ttl=47 time=187.722 ms
64 bytes from 124.83.187.140: icmp_seq=2 ttl=47 time=188.062 ms
Request timeout for icmp_seq 3
64 bytes from 124.83.187.140: icmp_seq=4 ttl=47 time=188.824 ms
64 bytes from 124.83.187.140: icmp_seq=5 ttl=47 time=187.600 ms
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
64 bytes from 124.83.187.140: icmp_seq=8 ttl=47 time=184.806 ms
Request timeout for icmp_seq 9
64 bytes from 124.83.187.140: icmp_seq=10 ttl=47 time=185.570 ms
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
64 bytes from 124.83.187.140: icmp_seq=14 ttl=47 time=190.584 ms
64 bytes from 124.83.187.140: icmp_seq=15 ttl=47 time=184.221 ms
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
64 bytes from 124.83.187.140: icmp_seq=20 ttl=47 time=189.373 ms
Request timeout for icmp_seq 21
64 bytes from 124.83.187.140: icmp_seq=22 ttl=47 time=190.539 ms
^C
--- yahoo.co.jp ping statistics ---
23 packets transmitted, 11 packets received, 52.2% packet loss
round-trip min/avg/max/stddev = 184.221/188.017/190.889/2.229 ms

plambrechtsen

1948 posts

Uber Geek
Inactive user

#876425 13-Aug-2013 13:05

Ping really isn't a great way to determine if you are getting connectivity through to countries.

Worth ringing up the broadband helpdesk on 0800 225598 and logging a network fault with them.

kyhwana2

2566 posts

Uber Geek

#876442 13-Aug-2013 13:20

Try a traceroute/winmtr. http://winmtr.net/

Kirdog

202 posts

Master Geek

#876444 13-Aug-2013 13:22

plambrechtsen: Ping really isn't a great way to determine if you are getting connectivity through to countries.

Worth ringing up the broadband helpdesk on 0800 225598 and logging a network fault with them.

I think he testing quality of connectivity for gaming (not actual fact of connectivity).

My ping to the same place:

Telecom. ADSL2+

Sorry about my English guys :>

Inphinity

2780 posts

Uber Geek

#876450 13-Aug-2013 13:24

PING 202.67.53.202 (202.67.53.202) 56(84) bytes of data.
64 bytes from 202.67.53.202: icmp_seq=1 ttl=43 time=111 ms
64 bytes from 202.67.53.202: icmp_seq=2 ttl=43 time=109 ms
64 bytes from 202.67.53.202: icmp_seq=3 ttl=43 time=109 ms
64 bytes from 202.67.53.202: icmp_seq=4 ttl=43 time=122 ms
64 bytes from 202.67.53.202: icmp_seq=5 ttl=43 time=110 ms
64 bytes from 202.67.53.202: icmp_seq=6 ttl=43 time=109 ms
64 bytes from 202.67.53.202: icmp_seq=7 ttl=43 time=109 ms
64 bytes from 202.67.53.202: icmp_seq=8 ttl=43 time=109 ms
64 bytes from 202.67.53.202: icmp_seq=9 ttl=43 time=107 ms
64 bytes from 202.67.53.202: icmp_seq=10 ttl=43 time=107 ms
64 bytes from 202.67.53.202: icmp_seq=11 ttl=43 time=111 ms
64 bytes from 202.67.53.202: icmp_seq=12 ttl=43 time=122 ms
64 bytes from 202.67.53.202: icmp_seq=13 ttl=43 time=109 ms
64 bytes from 202.67.53.202: icmp_seq=14 ttl=43 time=107 ms
64 bytes from 202.67.53.202: icmp_seq=15 ttl=43 time=114 ms
64 bytes from 202.67.53.202: icmp_seq=16 ttl=43 time=118 ms
64 bytes from 202.67.53.202: icmp_seq=17 ttl=43 time=109 ms
64 bytes from 202.67.53.202: icmp_seq=18 ttl=43 time=122 ms
64 bytes from 202.67.53.202: icmp_seq=19 ttl=43 time=107 ms
64 bytes from 202.67.53.202: icmp_seq=20 ttl=43 time=108 ms
64 bytes from 202.67.53.202: icmp_seq=21 ttl=43 time=109 ms
64 bytes from 202.67.53.202: icmp_seq=22 ttl=43 time=111 ms
64 bytes from 202.67.53.202: icmp_seq=23 ttl=43 time=111 ms
64 bytes from 202.67.53.202: icmp_seq=24 ttl=43 time=109 ms
64 bytes from 202.67.53.202: icmp_seq=25 ttl=43 time=122 ms
^C
--- 202.67.53.202 ping statistics ---
25 packets transmitted, 25 received, 0% packet loss, time 24383ms
rtt min/avg/max/mdev = 107.537/112.076/122.926/5.172 ms

Seems OK to me

jeeg

351 posts

Ultimate Geek

#876464 13-Aug-2013 13:40

Thanks for the reply guys, yeah I'm mainly concerned for gaming.

I'll give help desk a call later when I get home

jeeg

351 posts

Ultimate Geek

#876595 13-Aug-2013 16:59

hmm wheres the edit button?

anyway I got home and it seems my packet loss issue is gone :O

PING 202.67.53.202 (202.67.53.202): 56 data bytes
64 bytes from 202.67.53.202: icmp_seq=0 ttl=45 time=235.866 ms
64 bytes from 202.67.53.202: icmp_seq=1 ttl=45 time=218.641 ms
64 bytes from 202.67.53.202: icmp_seq=2 ttl=45 time=229.273 ms
64 bytes from 202.67.53.202: icmp_seq=3 ttl=45 time=224.221 ms
64 bytes from 202.67.53.202: icmp_seq=4 ttl=45 time=218.706 ms
64 bytes from 202.67.53.202: icmp_seq=5 ttl=45 time=228.794 ms
64 bytes from 202.67.53.202: icmp_seq=6 ttl=45 time=220.703 ms
64 bytes from 202.67.53.202: icmp_seq=7 ttl=45 time=213.789 ms
64 bytes from 202.67.53.202: icmp_seq=8 ttl=45 time=215.392 ms
64 bytes from 202.67.53.202: icmp_seq=9 ttl=45 time=212.598 ms
64 bytes from 202.67.53.202: icmp_seq=10 ttl=45 time=221.566 ms
64 bytes from 202.67.53.202: icmp_seq=11 ttl=45 time=216.076 ms
64 bytes from 202.67.53.202: icmp_seq=12 ttl=45 time=218.682 ms
64 bytes from 202.67.53.202: icmp_seq=13 ttl=45 time=213.378 ms
64 bytes from 202.67.53.202: icmp_seq=14 ttl=45 time=213.377 ms
64 bytes from 202.67.53.202: icmp_seq=15 ttl=45 time=221.612 ms
64 bytes from 202.67.53.202: icmp_seq=16 ttl=45 time=219.236 ms
64 bytes from 202.67.53.202: icmp_seq=17 ttl=45 time=217.203 ms
64 bytes from 202.67.53.202: icmp_seq=18 ttl=45 time=216.817 ms
64 bytes from 202.67.53.202: icmp_seq=19 ttl=45 time=244.070 ms
64 bytes from 202.67.53.202: icmp_seq=20 ttl=45 time=218.442 ms
^C
--- 202.67.53.202 ping statistics ---
21 packets transmitted, 21 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 212.598/220.878/244.070/7.701 ms