Great down sync rate, web pages take minutes to load

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › Great down sync rate, web pages take minutes to load

kiwiNZL

14 posts

Geek

#84509 1-Jun-2011 12:09

Hi guys,

To clarify, my ISP is Orcon.

I previously had a huge drop in sync rates, it turns out (as one of you guys correctly suspected) that Telecom had installed a cabinet in my area causing my traffic to be routed around it apparently.

Eventually they decided to move me over to their wholesale service (I'm not quite sure what this means). Regardless, my down sync rates went from 2xxxk's to 16xxx's (great, but my uprate went from 1xxxk to 7xxk's however).

My problem is that despite my great downsync rate's the result is an unusable internet.

Speedtest.net looks like this:
(I'm trying to upload it but because of my internet I can't even upload the picture it's so slow)
https://www.speedtest.net/result/1320893798.png

Basically web pages take minutes to load, pictures (like the one above stall and never finish), online games lag terribly, and basically the entire thing is a miserable experience.

Does anyone have any idea what could be causing this? Anything I can do to fix it? I've sent off another email but I'm sure I won't hear from them for days. Any chance this is on my end?

1 | 2

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#476668 1-Jun-2011 13:25

Are you using the correct DNS servers? What are your pings like?

kiwiNZL

14 posts

Geek

#476671 1-Jun-2011 13:31

Primary DNS:
121.98.0.1

Secondary DNS:
121.98.0.2

Yup,

some pings:

ping digg.com

Pinging digg.com [64.191.203.30] with 32 bytes of data:
Reply from 64.191.203.30: bytes=32 time=373ms TTL=245
Request timed out.
Request timed out.
Reply from 64.191.203.30: bytes=32 time=155ms TTL=245
ping facebook.com

Pinging facebook.com [69.63.181.12] with 32 bytes of data:
Reply from 69.63.181.12: bytes=32 time=157ms TTL=245
Request timed out.
Reply from 69.63.181.12: bytes=32 time=149ms TTL=245
Reply from 69.63.181.12: bytes=32 time=228ms TTL=245

ping google.com

Pinging google.com [74.125.237.50] with 32 bytes of data:
Reply from 74.125.237.50: bytes=32 time=66ms TTL=56
Reply from 74.125.237.50: bytes=32 time=58ms TTL=56
Reply from 74.125.237.50: bytes=32 time=38ms TTL=56
Reply from 74.125.237.50: bytes=32 time=52ms TTL=56
ping trademe.co.nz

Pinging trademe.co.nz [202.162.72.2] with 32 bytes of data:
Reply from 202.162.72.2: bytes=32 time=29ms TTL=251
Reply from 202.162.72.2: bytes=32 time=31ms TTL=251
Reply from 202.162.72.2: bytes=32 time=48ms TTL=251
Reply from 202.162.72.2: bytes=32 time=63ms TTL=251

There is a noticeable difference between international and local traffic.

For instance, trademe.co.nz loads up all the text immediately, but still takes some time to continue loading pictures (reminds me of dialup days)
while facebook is almost close to unusable.

xpd

Geek @ Coastguard NZ
13765 posts

Uber Geek

Retired Mod

ID Verified

Trusted

Lifetime subscriber

#476678 1-Jun-2011 13:40

Try 60.234.1.1 and 2.2 for DNS.
Potentially point to same server but maybe not (havent checked myself but I always use the 60.x range)

Gavin / xpd / FastRaccoon / Geek of Coastguard New Zealand

LinkTree

kiwiNZL

14 posts

Geek

#476683 1-Jun-2011 13:48

I appreciate the help guys,

unfortunately changing DNS appears to make no difference, oddly can't connect to most international sites now (changed back and forth my DNS settings) but I would be surprised if that is a result of a DNS change for instance I can still visit NZ sites.

kiwiNZL

14 posts

Geek

#476695 1-Jun-2011 14:45

Luckily I have an old traceroute from before they switched me to a wholesale line. International traffic is definitely suffering from something.

Here's the old connection:

Route to google.com [74.125.237.80]

1 2 ms 1 ms 1 ms home [10.1.1.1]
2 23 ms 22 ms 23 ms lo1.ras1.nct.orcon.net.nz [60.234.8.201]
3 23 ms 22 ms 23 ms xe-1-0-0.cre1.nct.orcon.net.nz [121.98.9.13]
4 25 ms 22 ms 23 ms 121.99.12.0
5 46 ms 46 ms 46 ms 72.14.214.5
6 45 ms 46 ms 46 ms 72.14.214.6
7 47 ms 46 ms 46 ms 66.249.95.232
8 48 ms 47 ms 45 ms 72.14.237.55
9 47 ms 48 ms 46 ms 74.125.237.80

Here's the new one:
Route to google.com [74.125.237.51]

1 1 ms 1 ms 1 ms home [10.1.1.1]
2 16 ms 17 ms 17 ms lo1.erx1.nct.orcon.net.nz [60.234.8.17]
3 16 ms 14 ms 15 ms ge-0-0-3-200.cre1.nct.orcon.net.nz [121.98.9.17]
4 15 ms 15 ms 15 ms 121.99.12.0
5 39 ms 38 ms 38 ms 72.14.214.5
6 39 ms 38 ms 38 ms 72.14.214.6
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
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.

As I said local traffic is not perfect either but I think this is a pretty clear issue by itself.

This is Orcon's problem right? Nothing I can do here?

freitasm

BDFL - Memuneh
79263 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#476696 1-Jun-2011 14:56

What IP address do you get when you ping cdn.geekz1.com?

kiwiNZL

14 posts

Geek

#476697 1-Jun-2011 14:57

ping cdn.geekz1.com

Pinging nzcdn.geekz1.com [202.175.128.164] with 32 bytes of data:
Reply from 202.175.128.164: bytes=32 time=169ms TTL=122
Reply from 202.175.128.164: bytes=32 time=152ms TTL=122
Reply from 202.175.128.164: bytes=32 time=136ms TTL=122
Reply from 202.175.128.164: bytes=32 time=229ms TTL=122

Tradepub

Free professional, reference and technical white papers (affiliate link).

freitasm

BDFL - Memuneh
79263 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#476698 1-Jun-2011 14:58

Good... Just to make sure your DNS was resolving our New Zealand IP, not our CDN (overseas). It means your DNS is probably ok.

Even so the times are bad... I get 20ms ping from WLG to our server in AKL (on TelstraClear).

Ragnor

8219 posts

Uber Geek

Trusted

#476706 1-Jun-2011 15:27

kiwiNZL: Luckily I have an old traceroute from before they switched me to a wholesale line. International traffic is definitely suffering from something.

Here's the old connection:

Route to google.com [74.125.237.80]

1 2 ms 1 ms 1 ms home [10.1.1.1]
2 23 ms 22 ms 23 ms lo1.ras1.nct.orcon.net.nz [60.234.8.201]
3 23 ms 22 ms 23 ms xe-1-0-0.cre1.nct.orcon.net.nz [121.98.9.13]
4 25 ms 22 ms 23 ms 121.99.12.0
5 46 ms 46 ms 46 ms 72.14.214.5
6 45 ms 46 ms 46 ms 72.14.214.6
7 47 ms 46 ms 46 ms 66.249.95.232
8 48 ms 47 ms 45 ms 72.14.237.55
9 47 ms 48 ms 46 ms 74.125.237.80

Here's the new one:

Route to google.com [74.125.237.51]

1 1 ms 1 ms 1 ms home [10.1.1.1]
2 16 ms 17 ms 17 ms lo1.erx1.nct.orcon.net.nz [60.234.8.17]
3 16 ms 14 ms 15 ms ge-0-0-3-200.cre1.nct.orcon.net.nz [121.98.9.17]
4 15 ms 15 ms 15 ms 121.99.12.0
5 39 ms 38 ms 38 ms 72.14.214.5
6 39 ms 38 ms 38 ms 72.14.214.6
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
...

Looks like a problem after it gets to Orcon's core network. That would probably indicate there's something internal they haven't done in switching your plan.

Lodge a job with their helpdesk to investigate imo.

kiwiNZL

14 posts

Geek

#476846 1-Jun-2011 21:04

Ragnor was right, it looks like Orcon had not completed transferring the plan, I got an email tonight saying everything was up and running and so it was.

As always I appreciate all the help, you guys are awesome - Looks like I'm a happy Orcon customer again!

Athlonite

1828 posts

Uber Geek
Inactive user

#481556 15-Jun-2011 17:49

freitasm: What IP address do you get when you ping cdn.geekz1.com?

hmmm interesting I get this :

ping cdn.geekz1.com

Pinging geekz1.sohosolutionsltd.netdna-cdn.com [67.201.31.3] with 32 bytes of data:
Reply from 67.201.31.3: bytes=32 time=174ms TTL=56
Reply from 67.201.31.3: bytes=32 time=173ms TTL=56
Reply from 67.201.31.3: bytes=32 time=174ms TTL=56
Reply from 67.201.31.3: bytes=32 time=173ms TTL=56

Ping statistics for 67.201.31.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 173ms, Maximum = 174ms, Average = 173ms

dns servers are 208.67.220.220 and 208.67.222.222 (openDNS)

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#481578 15-Jun-2011 18:42

Athlonite:
freitasm: What IP address do you get when you ping cdn.geekz1.com?

hmmm interesting I get this :

ping cdn.geekz1.com

Pinging geekz1.sohosolutionsltd.netdna-cdn.com [67.201.31.3] with 32 bytes of data:
Reply from 67.201.31.3: bytes=32 time=174ms TTL=56
Reply from 67.201.31.3: bytes=32 time=173ms TTL=56
Reply from 67.201.31.3: bytes=32 time=174ms TTL=56
Reply from 67.201.31.3: bytes=32 time=173ms TTL=56

Ping statistics for 67.201.31.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 173ms, Maximum = 174ms, Average = 173ms

dns servers are 208.67.220.220 and 208.67.222.222 (openDNS)

That's exactly the key downside of using OpenDNS on any ISP in New Zealand. Because 3rd party DNS servers can't understand CDN's traffic that should be local including such things as YouTube caches all get messed up.

IMHO there is no valid reason for using OpenDNS in NZ, any benefits such as the content filtering are completely outweighted by the numerous downsides.

Sounddude

I fix stuff!
1928 posts

Uber Geek

Trusted

2degrees

Lifetime subscriber

#481637 15-Jun-2011 22:09

Athlonite: [
dns servers are 208.67.220.220 and 208.67.222.222 (openDNS)

I highly recommend using the Orcon DNS servers. Otherwise youtube and Akamai etc will be served from overseas rather than local caches.

freitasm

BDFL - Memuneh
79263 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#481694 16-Jun-2011 07:49

Athlonite:
freitasm: What IP address do you get when you ping cdn.geekz1.com?

hmmm interesting I get this :

ping cdn.geekz1.com

Pinging geekz1.sohosolutionsltd.netdna-cdn.com [67.201.31.3] with 32 bytes of data:
Reply from 67.201.31.3: bytes=32 time=174ms TTL=56

dns servers are 208.67.220.220 and 208.67.222.222 (openDNS)

And that's the problem of using OpenDNS, Google DNS, Symantec DNS and others. They will tell you to use an IP address that most likely will be in the US, making everything slow for you. Change to your ISP DNS and you should see a huge improvement.

FYI, we use a balanced DNS configuration. If you are in New Zealand you download resources for Geekzone directly from our servers. If you are outside New Zealand DNS will point you to the Anycast CDN provider. Your traffic to Geekzone (images, CSS, scripts) is probably coming from Los Angeles, the closest CDN POP.

Athlonite

1828 posts

Uber Geek
Inactive user

#481952 16-Jun-2011 17:15

result from dns change back to ISP's dns (orcon)

C:\Windows\system32>ping cdn.geekz1.com

Pinging nzcdn.geekz1.com [202.175.128.164] with 32 bytes of data:
Reply from 202.175.128.164: bytes=32 time=41ms TTL=122
Reply from 202.175.128.164: bytes=32 time=41ms TTL=122
Reply from 202.175.128.164: bytes=32 time=41ms TTL=122
Reply from 202.175.128.164: bytes=32 time=41ms TTL=122

Ping statistics for 202.175.128.164:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:

Minimum = 41ms, Maximum = 41ms, Average = 41ms

Much better than last result

1 | 2