certain websites are failing to load on home broadband but everything on mobile is fine

Forums › One New Zealand (including Vodafone, WxC, Farmside) › certain websites are failing to load on home broadband but everything on mobile is fine

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | ... | 11

250 posts

Master Geek

#902028 24-Sep-2013 18:58

Hmmm.. I seem to be suffering very similar issues. I have just recently (Monday) been upgraded to the Ultra Fast cable and had my old Motorola modem replaced with a new Cisco. Now I am finding some web sites (e.g. turbine.com, wikipedia.org) that will simply not load at all on any computer or device in the house. They load fine on mobile, and on the neighbours snap and vodafone dsl. The sites ping fine, resolve fine (using the .43 and .44 DNS with google as a backup) and traceroute gets all the way through - just no data loads. Other web sites will take between 20 and 40 seconds to load first time (including Vodafone ironically, IMDB, and parts of Geekzone).

Speedtests max out, connectivity to other sites are lovely and fast. I've bounced everything that is bouncable to no effect. I'm completely stumped. The worst part is, Lord of the Rings online no longer works (as it connects to the turbine servers) which means I am *this* close to being divorced by the wife and disowned by the kids. Help!

Any ideas?

I can't brain today. I have the dumb.

Coil

6614 posts

Uber Geek
Inactive user

#902036 24-Sep-2013 19:24

Mutly: Hmmm.. I seem to be suffering very similar issues. I have just recently (Monday) been upgraded to the Ultra Fast cable and had my old Motorola modem replaced with a new Cisco. Now I am finding some web sites (e.g. turbine.com, wikipedia.org) that will simply not load at all on any computer or device in the house. They load fine on mobile, and on the neighbours snap and vodafone dsl. The sites ping fine, resolve fine (using the .43 and .44 DNS with google as a backup) and traceroute gets all the way through - just no data loads. Other web sites will take between 20 and 40 seconds to load first time (including Vodafone ironically, IMDB, and parts of Geekzone).

Speedtests max out, connectivity to other sites are lovely and fast. I've bounced everything that is bouncable to no effect. I'm completely stumped. The worst part is, Lord of the Rings online no longer works (as it connects to the turbine servers) which means I am *this* close to being divorced by the wife and disowned by the kids. Help!

Any ideas?

Hi,
Please post tracert and pathpings to those websites.
Thanks.

Mutly

250 posts

Master Geek

#902039 24-Sep-2013 19:38

TimA:
Hi,
Please post tracert and pathpings to those websites.
Thanks.

Gidday,

here you go

PS C:\Users\Mutly> nslookup turbine.com
Server: ns1.telstraclear.net
Address: 203.97.78.43

Non-authoritative answer:
Name: turbine.com
Address: 74.201.102.41

Pinging turbine.com [74.201.102.41] with 32 bytes of data:
Reply from 74.201.102.41: bytes=32 time=234ms TTL=241
Reply from 74.201.102.41: bytes=32 time=222ms TTL=241
Reply from 74.201.102.41: bytes=32 time=221ms TTL=241
Reply from 74.201.102.41: bytes=32 time=245ms TTL=241

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

PS C:\Users\Mutly> pathping turbine.com

Tracing route to turbine.com [74.201.102.41]
over a maximum of 30 hops:
0 Loki [192.168.1.134]
1 JOKERNET [192.168.1.1]
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Loki [192.168.1.134]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% JOKERNET [192.168.1.1]

Trace complete.

PS C:\Users\Mutly> tracert turbine.com

Tracing route to turbine.com [74.201.102.41]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms JOKERNET [192.168.1.1]
2 * * * Request timed out.
3 20 ms 27 ms 19 ms 218.101.61.101
4 25 ms 36 ms 22 ms ie2-g-0-0-0.telstraclear.net [203.98.50.2]
5 29 ms 24 ms 23 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
6 190 ms 175 ms 185 ms te7-3.ccr01.sjc05.atlas.cogentco.com [38.122.92.105]
7 177 ms 175 ms 177 ms te0-2-0-4.ccr21.sjc01.atlas.cogentco.com [154.54.84.53]
8 177 ms 180 ms 177 ms te0-0-0-4.ccr21.sfo01.atlas.cogentco.com [154.54.1.129]
9 199 ms 196 ms 188 ms be2132.ccr21.mci01.atlas.cogentco.com [154.54.30.54]
10 229 ms 225 ms 228 ms te0-5-0-1.ccr21.ord01.atlas.cogentco.com [154.54.84.74]
11 234 ms 223 ms 224 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43.194]
12 262 ms 255 ms 228 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
13 255 ms 230 ms 222 ms 38.104.252.70
14 252 ms 238 ms 240 ms border1.te8-1-bbnet2.bsn003.pnap.net [63.251.128.107]
15 230 ms 227 ms 227 ms turbine-7.border1.bsn003.pnap.net [64.95.76.202]
16 228 ms 223 ms 222 ms 74.201.102.154
17 223 ms 220 ms 220 ms 74.201.102.41

Trace complete.

PS C:\Users\Mutly> nslookup en.wikipedia.org
Server: ns1.telstraclear.net
Address: 203.97.78.43

Non-authoritative answer:
Name: wikipedia-lb.eqiad.wikimedia.org
Addresses: 2620:0:861:ed1a::1
208.80.154.225
Aliases: en.wikipedia.org
wikipedia-lb.wikimedia.org

Pinging wikipedia-lb.eqiad.wikimedia.org [208.80.154.225] with 32 bytes of data:
Reply from 208.80.154.225: bytes=32 time=239ms TTL=49
Reply from 208.80.154.225: bytes=32 time=238ms TTL=49
Reply from 208.80.154.225: bytes=32 time=241ms TTL=49
Reply from 208.80.154.225: bytes=32 time=239ms TTL=49

PS C:\Users\Mutly> pathping en.wikipedia.org

Tracing route to wikipedia-lb.eqiad.wikimedia.org [208.80.154.225]
over a maximum of 30 hops:
0 Loki [192.168.1.134]
1 JOKERNET [192.168.1.1]
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Loki [192.168.1.134]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% JOKERNET [192.168.1.1]

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

PS C:\Users\Mutly> tracert en.wikipedia.org

Tracing route to wikipedia-lb.eqiad.wikimedia.org [208.80.154.225]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms JOKERNET [192.168.1.1]
2 * * * Request timed out.
3 11 ms 17 ms 17 ms 218.101.61.101
4 30 ms 31 ms 26 ms ie2-g-0-0-0.telstraclear.net [203.98.50.2]
5 26 ms 43 ms * ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
6 25 ms 28 ms 27 ms unknown.telstraglobal.net [134.159.174.37]
7 150 ms 154 ms 149 ms i-0-0-4-0.tlot-core01.bx.telstraglobal.net [202.84.142.118]
8 197 ms 185 ms 186 ms i-0-1-0-0.eqnx-core01.bi.telstraglobal.net [202.84.144.202]
9 156 ms 157 ms 160 ms i-0-0-0-1.eqnx03.bi.telstraglobal.net [202.84.251.50]
10 170 ms 152 ms 175 ms gtt-peer.eqnx03.pr.telstraglobal.net [134.159.61.74]
11 225 ms 224 ms 224 ms xe-5-1-0.was10.ip4.tinet.net [141.136.108.198]
12 243 ms 239 ms 244 ms xe-5-3-1.cr2-eqiad.wikimedia.org [173.241.131.218]
13 239 ms 240 ms 243 ms wikipedia-lb.eqiad.wikimedia.org [208.80.154.225]

Trace complete.

I can't brain today. I have the dumb.

Mutly

250 posts

Master Geek

#902051 24-Sep-2013 20:24

Interesting. After reading this thread I installed Hola, set region to anything other than NZ and those sites load fine. Hola is useless as the solution though as it only works in Chrome so has no effect on game servers and mobile devices. Besides - I shouldn't have to use it.

I can't brain today. I have the dumb.

AidanS

458 posts

Ultimate Geek

#902052 24-Sep-2013 20:26

I too have noticed some issues lately. For me it's sites like TradeMe and Kiwibank. Though in saying that the issues seem to have stopped for tonight.

-Aidan.

Coil

6614 posts

Uber Geek
Inactive user

#902057 24-Sep-2013 20:39

Mutly: Interesting. After reading this thread I installed Hola, set region to anything other than NZ and those sites load fine. Hola is useless as the solution though as it only works in Chrome so has no effect on game servers and mobile devices. Besides - I shouldn't have to use it.

Hi,

Hola is an in browser VPN solution. This is ADSL or Coax? (Excuse me if im not looking through every post)
Tried DNS servers. I have not had any luck replicating your issue.
The Pathping, nslookup and tracert's all look good. (Test to onshore sites and the one shaving the issues)

Thanks.

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

1 1 ms <1 ms 1 ms router [192.168.2.1]
2 37 ms 17 ms 11 ms be2-100.bras1ldv.akl.vf.net.nz.129.109.203.in-ad
dr.arpa [203.109.129.45]
3 11 ms 10 ms 27 ms be5-100.ppnzldv01.akl.vf.net.nz.129.109.203.in-a
ddr.arpa [203.109.129.46]
4 14 ms 13 ms 41 ms be7.ppnzldv02.akl.vf.net.nz [203.109.180.242]
5 11 ms 11 ms 15 ms UNASSIGNED.vf.net.nz [203.109.180.205]
6 14 ms 11 ms 14 ms UNASSIGNED.vf.net.nz [203.109.180.204]
7 76 ms 52 ms 52 ms gg-dom1.ihug.net [203.109.130.97]
8 * * * Request timed out.
9 * 22 ms 28 ms 202.50.234.78
10 104 ms 111 ms 128 ms 202.21.128.139
11 59 ms 69 ms 97 ms www.trademe.co.nz [202.162.72.2]

Trace complete.

AidanS

458 posts

Ultimate Geek

#902058 24-Sep-2013 20:41

What I found happening is TradeMe would "load" (displaying a blank page) for about 15 seconds and at the last second the entire page would just "insta-load".

However it seems to be fine for me now. Not sure about the other guy though.

-Aidan.

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

Mutly

250 posts

Master Geek

#902062 24-Sep-2013 20:44

TimA: Hi,

Hola is an in browser VPN solution. This is ADSL or Coax? (Excuse me if im not looking through every post)
Tried DNS servers. I have not had any luck replicating your issue.

My issues are with coax cable. I'm not too worried about the odd slow load time on some site. What gets me is sites and servers returning NO data at all (like turbine and wikipedia - both sites used a lot by my family). I was just proving a point with Hola that those sites are actually up and can load for me locally via VPN. It's not a solution.

I can't brain today. I have the dumb.

Shoes2468

785 posts

Ultimate Geek

#902086 24-Sep-2013 21:23

Mutly:
TimA: Hi,

Hola is an in browser VPN solution. This is ADSL or Coax? (Excuse me if im not looking through every post)
Tried DNS servers. I have not had any luck replicating your issue.

My issues are with coax cable. I'm not too worried about the odd slow load time on some site. What gets me is sites and servers returning NO data at all (like turbine and wikipedia - both sites used a lot by my family). I was just proving a point with Hola that those sites are actually up and can load for me locally via VPN. It's not a solution.

This exact same issue is happening to me tonight(in general there has been others too I have noticed over the past week or so). been trying to look at Wikipedia but just getting the exact same issue, nothing happens but when using a vpn solution it works fine, it seems like a transparent proxy issue that seems to be an on going issue with tcl/Vodafone, I was hoping Vodafone would iron these issues out and maybe they will given more time. But seriously looking at other isps and will really start looking when ufb becomes available in the next 9 months or so.

insane

3239 posts

Uber Geek

ID Verified

Trusted

#902089 24-Sep-2013 21:34

AidanS: What I found happening is TradeMe would "load" (displaying a blank page) for about 15 seconds and at the last second the entire page would just "insta-load".

However it seems to be fine for me now. Not sure about the other guy though.

-Aidan.

Install firebug or similar and see which requests are holding things up

AidanS

458 posts

Ultimate Geek

#902098 24-Sep-2013 22:00

Just had this issue with loading Stuff.co.nz

Traceroute (while the page was trying to load).

Tracing route to stuff.co.nz [202.21.128.102]
over a maximum of 30 hops:

1 2 6 ms 6 ms 6 ms be2-100.bras1ftc.akl.vf.net.nz.129.109.203.in-ad
dr.arpa [203.109.129.37]
3 7 ms 5 ms 6 ms be5-100.ppnzftc01.akl.vf.net.nz.129.109.203.in-a
ddr.arpa [203.109.129.38]
4 6 ms 5 ms 7 ms be7-188.ppnzftc02.akl.vf.net.nz.180.109.203.in-a
ddr.arpa [203.109.180.226]
5 6 ms 6 ms 6 ms be8-188.ppnzftc02.akl.vf.net.nz.180.109.203.in-a
ddr.arpa [203.109.180.225]
6 7 ms 6 ms 7 ms gi3-2-3318.akl-sky-bdr1.ihug.net [203.109.130.98 ]
7 46 ms 86 ms 46 ms gg-dom1.ihug.net [203.109.130.97]
8 * * * Request timed out.
9 17 ms 16 ms 17 ms 202.50.234.78
10 17 ms * 17 ms 202.21.128.129
11 16 ms 16 ms 17 ms 202.21.128.102

Trace complete.

(notice the timeout on number 8 and the timeout on number 10)

The page loads after about 15-20 seconds of blank page loading.

-Aidan.

r2b2

586 posts

Ultimate Geek

#902138 24-Sep-2013 23:29

I echo insane's recommendation. These days most pages (especially Stuff!) display a wide variety of information (read Adverts) from a wide variety of websites. Therefore even if the ping times & routes look ok to the particular site in question, one of the other various servers that are serving up the rest of the info can cause issues.

Of course if your site is written correctly then this shouldn't be the case but quite often, unfortunately, it doesn't appear to be the case even with all the info out there on how to not run into the issue...

AidanS

458 posts

Ultimate Geek

#902179 25-Sep-2013 07:28

r2b2: I echo insane's recommendation. These days most pages (especially Stuff!) display a wide variety of information (read Adverts) from a wide variety of websites. Therefore even if the ping times & routes look ok to the particular site in question, one of the other various servers that are serving up the rest of the info can cause issues.

Of course if your site is written correctly then this shouldn't be the case but quite often, unfortunately, it doesn't appear to be the case even with all the info out there on how to not run into the issue...

I used firebug for Stuff and nothing in the network tab showed up until after the 15-20 second delay when the site actually started loading.

Not to mention this is a new issue.

-Aidan.

ajam

8 posts

Wannabe Geek

#902435 25-Sep-2013 13:35

AidanS: I used firebug for Stuff and nothing in the network tab showed up until after the 15-20 second delay when the site actually started loading.

I've been experiencing problems like this for a week or more but only on some sites, notably http://stackoverflow.com/
Today's problem is that I can't get any response (not even delayed) from some sites (for example: http://en.wikipedia.com/ ).

$ host en.wikipedia.com
en.wikipedia.com is an alias for wikipedia-lb.wikimedia.org.
wikipedia-lb.wikimedia.org is an alias for wikipedia-lb.eqiad.wikimedia.org.
wikipedia-lb.eqiad.wikimedia.org has address 208.80.154.225
wikipedia-lb.eqiad.wikimedia.org has IPv6 address 2620:0:861:ed1a::1

$ ping 'en.wikipedia.com'
PING wikipedia-lb.eqiad.wikimedia.org (208.80.154.225) 56(84) bytes of data.
64 bytes from wikipedia-lb.eqiad.wikimedia.org (208.80.154.225): icmp_req=1 ttl=48 time=236 ms
64 bytes from wikipedia-lb.eqiad.wikimedia.org (208.80.154.225): icmp_req=2 ttl=48 time=238 ms
^C

$ sudo traceroute -T -p 81 'en.wikipedia.com'
traceroute to en.wikipedia.com (208.80.154.225), 30 hops max, 60 byte packets
1 home-router.home.xxxxx.xx.xx (192.168.1.120) 15.278 ms 14.759 ms 14.467 ms
2 * * *
3 lo0.internet.ivpn.pe14.telstraclear.net (218.101.61.97) 32.151 ms 31.890 ms 31.626 ms
4 ie2-g-0-0-0.telstraclear.net (203.98.50.2) 56.101 ms 55.838 ms 48.079 ms
5 ge-0-2-0-1.xcore1.acld.telstraclear.net (203.98.50.251) 48.819 ms 48.556 ms 48.294 ms
6 unknown.telstraglobal.net (134.159.174.37) 43.782 ms unknown.telstraglobal.net (134.159.174.41) 28.633 ms 23.433 ms
7 i-0-6-4-0.tlot-core01.bx.telstraglobal.net (202.84.142.110) 164.967 ms 153.818 ms 153.359 ms
8 i-0-4-0-8.eqnx-core01.bi.telstraglobal.net (202.84.140.242) 179.850 ms 182.343 ms 186.592 ms
9 202.40.149.42 (202.40.149.42) 183.595 ms 184.844 ms 184.097 ms
10 gtt-peer.eqnx03.pr.telstraglobal.net (134.159.61.74) 211.082 ms 211.330 ms 203.583 ms
11 xe-1-2-1.was10.ip4.tinet.net (89.149.184.173) 249.309 ms xe-5-0-0.was10.ip4.tinet.net (141.136.108.194) 224.571 ms xe-5-1-0.was10.ip4.tinet.net (141.136.108.198) 253.305 ms
12 xe-5-3-1.cr2-eqiad.wikimedia.org (173.241.131.218) 238.816 ms 237.811 ms 236.314 ms
13 wikipedia-lb.eqiad.wikimedia.org (208.80.154.225) 236.317 ms 240.062 ms 238.067 ms

Running a TCP traceroute on port 80 shows there's a transparent proxy in the path:
$ sudo traceroute -T -p 80 'en.wikipedia.com'
traceroute to en.wikipedia.com (208.80.154.225), 30 hops max, 60 byte packets
1 home-router.home.xxxxx.xx.xx (192.168.1.120) 15.092 ms 14.570 ms 14.054 ms
2 * * *
3 lo0.internet.ivpn.pe14.telstraclear.net (218.101.61.97) 31.992 ms 31.457 ms 31.192 ms
4 ie2-g-0-0-0.telstraclear.net (203.98.50.2) 54.416 ms 53.156 ms 49.396 ms
5 wikipedia-lb.eqiad.wikimedia.org (208.80.154.225) 50.133 ms 50.369 ms 50.606 ms

Requesting the home page from the transparent proxy hangs:
$ telnet 'en.wikipedia.com' 80
Trying 208.80.154.225...
Connected to wikipedia-lb.eqiad.wikimedia.org.
Escape character is '^]'.
GET / HTTP/1.0

HTTP/1.1 200 OK
Content-Type: text/html
Pragma: no-cache
Refresh: 1; URL=http://208.80.154.225/
Connection: Close

<HTML></HTML>Connection closed by foreign host.
$

This just sat there for about a minute or two before returning the response.

--
Adrian

DavidVF

11 posts

Geek

Trusted

#902930 26-Sep-2013 10:43

The sites...resolve fine (using the .43 and .44 DNS with google as a backup)

I'd strongly suggest removing the google DNS servers and trying again.

Google DNS, CDNs and caching do not get along well.

CDNs such as Akamai use clever DNS tricks to point you to the CDN node closest to you; in practice this results in them pointing you towards the CDN node closest to your DNS server. The upshot of this is that if you're using google DNS all bets are off as to which CDN node you'll be pointed to - when I've tested this, it's tended to be Australian-based CDN nodes, but it varies a bit.

The issue with this is that the caches do their own DNS lookups when serving content (this is a measure to prevent cache poisoning), using internal DNS servers; if your DNS lookup resolved to an international host and the cache's lookup resolves to a domestic host, the cache will fail to serve the requested page (it's actually worse than that; the TCP session setup fails such that it times out rather than cleanly failing, so it takes an extended period of time to fail).

The solution is to use local DNS (we'd really prefer you to use Vodafone DNS, obviously), so that when you're served geo-localised DNS results, they're actually appropriate for you.

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | ... | 11