connecting to google been touch and go last few days?

Forums › Spark New Zealand (including Skinny and BigPipe) › connecting to google been touch and go last few days?

qwerty7

434 posts

Ultimate Geek
Inactive user

#94646 15-Dec-2011 22:11

or is it just me. Several times over the last few days I have failed being able to connect to google and ended up using yahoo or some other search engine

Zippity

683 posts

Ultimate Geek

#558496 15-Dec-2011 22:39

No such problems at my end.

Paulthagerous

698 posts

Ultimate Geek

Trusted

#558502 15-Dec-2011 23:00

No issues here either

l43a2

1779 posts

Uber Geek

ID Verified

Trusted

#558508 15-Dec-2011 23:46

i've been having some issues with google... bloody proxy cache crap.

rscole86

4973 posts

Uber Geek

Moderator

Trusted

Lifetime subscriber

#558533 16-Dec-2011 06:37

No problems here. Have you reported it?

lxsa

26 posts

Geek

#559158 18-Dec-2011 09:43

No problems here, please report a fault.
Anyone else having problems

marmel

1924 posts

Uber Geek

ID Verified

Trusted

#559171 18-Dec-2011 10:17

Yes I have had problems off and on, times out before loading page. has been happening over the past 10 days.

lxsa

26 posts

Geek

#559289 18-Dec-2011 18:10

Telecom NZ employe the use of caches for international traffic.
Google site are bypassed/is never cached.
So it's definitely NOT proxy cache issue, and trust me if google site has issues it would become very apparent at a large scale issue.

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.

lxsa

26 posts

Geek

#559290 18-Dec-2011 18:12

Oh unless the issue is DNS related

izomezzo

39 posts

Geek

#559992 20-Dec-2011 16:33

Yeah I've been seeing this also. Resorted to Vodagone 3G and it was working ok, so some Telecom issue. Didn't affect any other sites for me though. Bit painful when using Chrome though.

Izo

tumnasgt

83 posts

Master Geek

#560704 22-Dec-2011 13:47

I have been having this problem, it is not possible to access Google (also with facebook and a couple of other sites) for several minutes, and then back to normal. Sometimes it will be happen several times an hour, and sometimes only once or twice a day, and has been happening for the last two weeks or so.

Originally I thought it was my end because I've been having some problems with my router's DNS caching (which I thought I had resolved), but after talking to a friend who is also on Telecom it doesn't seem to be an isolated issue.

Oh, just started happening again. I can ping google.co.nz, but Chrome reports that the connection was reset (error 101). Using HTTPS makes no difference (which I think means it isn't cache related).

lxsa

26 posts

Geek

#560707 22-Dec-2011 13:53

Have you tried changing to another DNS server like google or open public DNS and then monitor if the problem goes away?

tumnasgt

83 posts

Master Geek

#560721 22-Dec-2011 14:19

As I can ping google, I suspect it's not a DNS problem.

The router is set with the Xtra primary DNS as primary, and 8.8.8.8 as the secondary.

Also, Chrome has a different error for being unable to resolve a host, connection reset implies something is being dropped

tumnasgt

83 posts

Master Geek

#560835 22-Dec-2011 22:50

Spoke to Telecom for ages, at first they were adamant it was DNS, but after making me set the DNS on my computer and telling to call them back if it happened again, I only just hung up the phone before it happened again.

So now they are looking into it, though I'm 99% sure it's a proxy problem, as I just discovered that I can get around the problem by going via https instead of http. I wonder if the problem is mainly on big sites because of the higher demand for them is causing a problem in the cache.

I think tomorrow morning I'll give them a call and get my IP moved to the no-proxy list (already static, and I'm not bothered if I have to change once to be on the list).

Their higher level support has been pretty good, with the exception of making me change the DNS stuff and then call them back despite me giving evidence that it wasn't DNS (eg, I could still ping without issue and I could open a netcat session with the server, it only kicked me off after sending an HTTP request). I understand that they normally deal with people less technically inclined , but I do find it silly that higher level support can't use the evidence given to confirm something as working rather than working through a process.

eXDee

4032 posts

Uber Geek

Trusted

#560849 22-Dec-2011 23:54

tumnasgt: Spoke to Telecom for ages, at first they were adamant it was DNS, but after making me set the DNS on my computer and telling to call them back if it happened again, I only just hung up the phone before it happened again.

So now they are looking into it, though I'm 99% sure it's a proxy problem, as I just discovered that I can get around the problem by going via https instead of http. I wonder if the problem is mainly on big sites because of the higher demand for them is causing a problem in the cache.

I think tomorrow morning I'll give them a call and get my IP moved to the no-proxy list (already static, and I'm not bothered if I have to change once to be on the list).

Their higher level support has been pretty good, with the exception of making me change the DNS stuff and then call them back despite me giving evidence that it wasn't DNS (eg, I could still ping without issue and I could open a netcat session with the server, it only kicked me off after sending an HTTP request). I understand that they normally deal with people less technically inclined , but I do find it silly that higher level support can't use the evidence given to confirm something as working rather than working through a process.

Is it possible to get a case reference number? A telecom guy over at GP is willing to follow and look into the case number, and i'd be happy to call up and mention that i am having the same issue. The more people that report it, the more likely it'll get fixed.