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.