[Snap] [Snap] International connectivity

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › [Snap] [Snap] International connectivity

1 | 2 | 3 | 4 | 5 | 6 | 7

1134 posts

Uber Geek

Lifetime subscriber

#988185 16-Feb-2014 12:56

astrial: Looks like this is still an issue today, and is not restricted to international traffic - tests run just now; although I am a bit puzzled why my router is taking so long to respond at times..

Pinging www.trademe.co.nz [202.162.72.2] with 32 bytes of data:

1 1 ms 2 ms 121 ms 192.168.1.1

*****

Pinging www.google.com [74.125.237.180] with 32 bytes of data:

1 138 ms 172 ms 67 ms 192.168.1.1

if you are pinging 1-172+ms to your own router, you need to address that first, something is probably not right on your end, you may find fixing the cause of that will solve your other issues, i doubt your issues are related to this thread.

astrial

29 posts

Geek

#988220 16-Feb-2014 13:45

My router and I had a man-to-man chat and we seem to have resolved our differences.

The issue however still appears to remain:

Pinging www.google.com [74.125.237.180] with 32 bytes of data:
Ping statistics for 74.125.237.180:
Packets: Sent = 24, Received = 22, Lost = 2 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 2320ms, Average = 421ms

Tracing route to www.google.com [74.125.237.180]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 152 ms 55 ms 108 ms 16.17.69.111.static.snap.net.nz [111.69.17.16]
3 24 ms 5 ms 8 ms 54.32.69.111.static.snap.net.nz [111.69.32.54]
4 73 ms 131 ms 78 ms xe-0-0-2-0.eqx.snap.net.nz [111.69.56.2]
5 190 ms 330 ms 223 ms peer-google.snap.net.nz [111.69.56.3]
6 1159 ms 1567 ms 1444 ms 66.249.95.232
7 460 ms 239 ms 113 ms 72.14.232.31
8 628 ms 410 ms 183 ms syd01s18-in-f20.1e100.net [74.125.237.180]

*****

Pinging www.trademe.co.nz [202.162.72.2] with 32 bytes of data:
Ping statistics for 202.162.72.2:
Packets: Sent = 25, Received = 24, Lost = 1 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 632ms, Average = 112ms

Tracing route to www.trademe.co.nz [202.162.72.2]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 * 219 ms 859 ms 16.17.69.111.static.snap.net.nz [111.69.17.16]
3 982 ms 2269 ms * 54.32.69.111.static.snap.net.nz [111.69.32.54]
4 2022 ms 1592 ms 1479 ms TenGigabitEthernet0-2-0-917.aknnr-rt1.fx.net.nz
[131.203.243.57]
5 1282 ms 1314 ms 2017 ms TenGigabitEthernet0-1-0-534.wnwnr-rt1.fx.net.nz
[202.53.187.146]
6 1212 ms 2056 ms 656 ms TenGigabitEthernet0-2-0-911.wnmur-rt1.fx.net.nz
[131.203.246.137]
7 2114 ms * * trademe-wnmur.fx.net.nz [131.203.246.138]
8 115 ms 150 ms 174 ms 202.21.128.135
9 577 ms 148 ms 30 ms www.trademe.co.nz [202.162.72.2]

hio77

12999 posts

Uber Geek

ID Verified

Trusted

Lizard Networks

#988222 16-Feb-2014 13:47

by the looks of it, you still have a fair bit of saturation on your line, causing high pings.

if i had to pick it, your on adsl and files are being uploaded.

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

JamesL

956 posts

Ultimate Geek
Inactive user

#988225 16-Feb-2014 13:54

Using echoping dns to query www.google.co.nz using google and snap DNS

insane

3240 posts

Uber Geek

ID Verified

Trusted

#988227 16-Feb-2014 13:58

JamesL: Using echoping dns to query www.google.co.nz using google and snap DNS

Some great consistency there, by Google ;)

nzgeek

618 posts

Ultimate Geek

#988251 16-Feb-2014 14:33

astrial: My router and I had a man-to-man chat and we seem to have resolved our differences.

The issue however still appears to remain

The problem appears to be somewhere at your end. I'm getting a consistent connection with Trade Me:

Pinging www.trademe.co.nz [202.162.72.2] with 32 bytes of data:
Ping statistics for 202.162.72.2:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 18ms, Average = 16ms

Tracing route to www.trademe.co.nz [202.162.72.2]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms fritz.box [172.20.10.1]
2 7 ms 7 ms 7 ms 16.17.69.111.static.snap.net.nz [111.69.17.16]
3 7 ms 6 ms 6 ms 54.32.69.111.static.snap.net.nz [111.69.32.54]
4 8 ms 6 ms 6 ms TenGigabitEthernet0-2-0-917.aknnr-rt1.fx.net.nz [131.203.243.57]
5 16 ms 23 ms 16 ms TenGigabitEthernet0-1-0-510.akkin-rt2.fx.net.nz [202.53.187.82]
6 16 ms 15 ms 15 ms TenGigabitEthernet0-2-0-911.wnmur-rt1.fx.net.nz [131.203.246.137]
7 16 ms 16 ms 16 ms trademe-wnmur.fx.net.nz [131.203.246.138]
8 16 ms 16 ms 16 ms 202.21.128.135
9 16 ms 16 ms 15 ms www.trademe.co.nz [202.162.72.2]

I'm getting consistent pings with www.google.co.nz too, 29-31ms with no packet loss.

JamesL

956 posts

Ultimate Geek
Inactive user

#988276 16-Feb-2014 15:28

insane:
JamesL: Using echoping dns to query www.google.co.nz using google and snap DNS

Some great consistency there, by Google ;)

Not really a fair test I know :p

Quic Broadband

Move to New Zealand's best fibre broadband service (affiliate link). Free setup code: R587125ERQ6VE. Note that to use Quic Broadband you must be comfortable with configuring your own router.

astrial

29 posts

Geek

#988315 16-Feb-2014 16:20

hio77: by the looks of it, you still have a fair bit of saturation on your line, causing high pings.

if i had to pick it, your on adsl and files are being uploaded.

Quick update on the semi-possible-hijacking of this thread

No, I had nothing uploading or downloading at the time in any serious way after I reset the router.

nzgeek:
astrial: My router and I had a man-to-man chat and we seem to have resolved our differences.

The issue however still appears to remain

The problem appears to be somewhere at your end. I'm getting a consistent connection with Trade Me:

I have my doubts that there were at my end. I've made no changes since the last posting of stats and the connection is now like the following (i.e. resolved) - although any further information might be interesting to see:

Pinging www.trademe.co.nz [202.162.73.2] with 32 bytes of data:
Ping statistics for 202.162.73.2:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 9ms, Average = 6ms

Pinging www.google.com [74.125.237.178] with 32 bytes of data:
Ping statistics for 74.125.237.178:
Packets: Sent = 117, Received = 117, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 40ms, Average = 30ms

hio77

12999 posts

Uber Geek

ID Verified

Trusted

Lizard Networks

#988318 16-Feb-2014 16:22

maybe a mobile phone or something?

defiantly looks like you were saturated, and now your happy.

your jitter still does seem a little delightful though.

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

Psilan

856 posts

Ultimate Geek

#988806 17-Feb-2014 12:30

Can anyone get to www.timeanddate.com ?

Voyager referral - https://refer.voyager.nz/68QKJ8XKK

hio77

12999 posts

Uber Geek

ID Verified

Trusted

Lizard Networks

#988809 17-Feb-2014 12:31

Psilan: Can anyway get to www.timeanddate.com ?

unrelated ild say.

webserver is responding, but simply with a 3 line, blank file.

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

Psilan

856 posts

Ultimate Geek

#988812 17-Feb-2014 12:33

Strange. There are a few sites giving me this behavior today.
Thanks for checking for me.

Voyager referral - https://refer.voyager.nz/68QKJ8XKK

mercutio

1392 posts

Uber Geek

#988813 17-Feb-2014 12:33

Psilan: Can anyway get to www.timeanddate.com ?

i think that's a general cdn issue at the host... can connect to it.. but it doesn't load... works from overseras..

and works if you use dns from overseas to choose a different end point.

update:
there's a break in cable between australia and japan at 3:45 ADST which is like 5:45 am NZDT.

that is likely to hinder a lot of australian cdn's, as a lot of them go via singapore. and connectivity to singapore is outstretched at the best of times, and is likely to take some traffic that would normally go via japan.

part of the problem with people dumping is in "south east asia" which means we tend to have much traffic to hong kong, japan, singapore than users would normally make. with cdn's it's often difficult to figure out where they're fetching stuff from, but even if in australia, it doesn't mean the content is actually coming from australia, and it's not uncommon to come from asia. even with things like google.

quakeguy

111 posts

Master Geek

Trusted

#989854 18-Feb-2014 18:06

(Cross post, but) try downloading http://speedtest.fremont.linode.com/100MB-fremont.bin and see how fast you get - Snap has a ton of international capacity, which should be performing really well! For some reason, Speedtest.net is allocating a very small test file when testing to USA, and so it's not getting up to speed before the test finishes.

“I do not think there is any thrill that can go through the human heart like that felt by the inventor as he sees some creation of the brain unfolding to success... Such emotions make a man forget food, sleep, friends, love, everything.” - Nikola Tesla

Disclaimer: Views expressed in my posts do not necessarily reflect those views of my employer.

hio77

12999 posts

Uber Geek

ID Verified

Trusted

Lizard Networks

#989866 18-Feb-2014 18:20

quakeguy: (Cross post, but) try downloading http://speedtest.fremont.linode.com/100MB-fremont.bin and see how fast you get - Snap has a ton of international capacity, which should be performing really well! For some reason, Speedtest.net is allocating a very small test file when testing to USA, and so it's not getting up to speed before the test finishes.

i actually found the TCP ramp on that link rather slow, or the tcp/ip stack isnt as tuned as im used to, maxing out at about 2.5MB/s. i suspect it may be a time of day thing, since i normally ramp right up to 6.2MB/s within seconds to my NL dedi though on single threads.

will try it again later tonight though...

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

1 | 2 | 3 | 4 | 5 | 6 | 7