Geekzone Bad Host error/page not available

Forums › Vodafone New Zealand › Geekzone Bad Host error/page not available

MaxLV

654 posts

Ultimate Geek

#147355 17-Jun-2014 00:06

Only seems to happen randomly between 11:45pm and midnight weekdays. I get very slow page opening times with a Please wait, resolving host errors, and/or sometimes Page Not Available errors.

On Google Chrome, (latest Version) Windows 8.1 update, Vodafone Cable.

nakedmolerat

4553 posts

Uber Geek

Trusted

Lifetime subscriber

#1067206 17-Jun-2014 00:11

One person supports this post

..... Vodafone Cable.

^ That is the answer to your problem

MaxLV

654 posts

Ultimate Geek

#1067209 17-Jun-2014 00:24

nakedmolerat:
..... Vodafone Cable.

^ That is the answer to your problem

I dont think so...

Anything constructive to offer?

nakedmolerat

4553 posts

Uber Geek

Trusted

Lifetime subscriber

#1067210 17-Jun-2014 00:29

MaxLV:
nakedmolerat:
..... Vodafone Cable.

^ That is the answer to your problem

I dont think so...

Anything constructive to offer?

Here you go http://www.geekzone.co.nz/forums.asp?forumid=40&topicid=147308

MaxLV

654 posts

Ultimate Geek

#1067213 17-Jun-2014 00:56

nakedmolerat:
MaxLV:
nakedmolerat:
..... Vodafone Cable.

^ That is the answer to your problem

I dont think so...

Anything constructive to offer?

Here you go http://www.geekzone.co.nz/forums.asp?forumid=40&topicid=147308

Interesting thread, but that's not what I'm talking about.

When I have the errors trying to access Geekzone as described in my OP, any other website I try are fine.

To http://www.geekzone.co.nz/forums.asp

Hop IP Address Host Name Response Time
=== ========== ========= =============
1 No reply from host
2 218.101.61.124 lo0.internet.ivpn.pe25.telstraclear.net 563 ms
3 203.98.50.2 ie2-g-0-0-0.telstraclear.net 34 ms
4 203.98.50.251 ge-0-2-0-1.xcore1.acld.telstraclear.net 24 ms
5 134.159.174.41 unknown.telstraglobal.net 36 ms
6 202.84.142.149 i-0-0-4-1.sydo-core02.bx.telstraglobal.net 51 ms
7 202.84.220.190 i-0-3-2-0.sydo-core01.bi.telstraglobal.net 51 ms
8 202.84.143.142 101 ms
9 202.84.143.94 i-6-0-0.6ntp-core01.bx.telstraglobal.net 151 ms
10 202.84.243.82 i-0-3-0-0.6ntp02.bi.telstraglobal.net 155 ms
11 202.126.173.98 pacnet-peer.6ntp02.pr.telstraglobal.net 152 ms
12 61.14.158.42 te0-3-0-3.wr2.sin0.asianetcom.net 154 ms
13 61.14.157.170 gi0-0-0.gw2.sin3.asianetcom.net 166 ms
14 202.147.32.101 te0-0-0-4.gw3.sin3.asianetcom.net 151 ms
15 No reply from host
16 162.159.242.82 150 ms
Trace complete

# IP Address Response Time TTL
= ========== ============= ===
1 No reply from host
2 No reply from host
3 No reply from host
4 No reply from host
5 162.159.242.82 153 ms 64
6 162.159.242.82 150 ms 64
7 162.159.242.82 150 ms 64
8 162.159.242.82 152 ms 64
9 162.159.242.82 151 ms 64
10 162.159.242.82 161 ms 64
11 162.159.242.82 153 ms 64
12 No reply from host
13 162.159.242.82 152 ms 64
14 No reply from host
15 162.159.242.82 152 ms 64
16 No reply from host
17 No reply from host
18 162.159.242.82 152 ms 64
19 162.159.242.82 154 ms 64
20 162.159.242.82 151 ms 64

sbiddle

28820 posts

Uber Geek

Moderator

Trusted

Biddle Corp

Lifetime subscriber

#1067232 17-Jun-2014 06:14

One person supports this post

In the past the issue has been a problem with the Vodafone transparent proxy and cloudfare CDN.

freitasm

BDFL - Memuneh
66335 posts

Uber Geek

Administrator

Trusted

Geekzone

Lifetime subscriber

#1067245 17-Jun-2014 07:47

Vodafone cable routes requests to Cloudflare via Singapore instead of Sydney, because that's how they roll. Any other network and you will get under 40ms pings to Cloudflare but on Vodafone is around 150ms.

That however doesn't seem to be the problem here as currently there's a DNS problem going on (not only for Geekzone but I get these errors in many other sites, most of them not on Cloudflare).

Unless you see a Cloudflare page saying "site offline" (which is a problem between Cloudflare and the origin server, nothing to do with Vodafone), then I'd say it either falls on DNS or proxy.

Unfortunatelly is hard for Vodafone to diagnose as those DNS failures happen and then all start working again the next second... Cache problems are more "persistent" and easier to see.