(Mods, if this should be in IMHO, please excuse me.)
I have Comcast cable internet and it is notoriously unreliable in this somewhat remote area (Clackamas County, OR). Much of the time the connection is entirely dead, but I’ve been noticing quite a few times when a shortlist of websites will open quickly, and nothing else will.
If I have access at all, many times I can open Google.com and all its subsidiaries, Facebook.com, and Wikipedia, but nothing else. I’ll have a dozen tabs open, all for huge web servers like nytimes.com, msn.com, washingtonpost.com, Google, Facebook, and Wikipedia, and I’ll go tripping through all the tabs trying to get them to load or refresh. Google/Facebook/Wikipedia will open and refresh instantaneously, repeatedly, where nothing else will.
I’d be VERY suspicious of deliberate throttling by Comcast, but for two things: (1) Wikipedia’s allowed? and (2) on these occasions, Comcast.net and Xfinity.com will NOT load.
Naturally, the only idea Comcast Customer Service ever has is to reboot the modem. This selective outage happens about once per day, sometimes for hours at a time. Sometimes rebooting the modem fixes the problem, but usually not. Any thoughts?
It could be a DNS problem. Basically the DNS (Domain Name Service) is what translates domain names (like http://www.wikipedia.org/) to IP addresses (like 208.80.154.224), which is what you need to actually connect. If the DNS goes down, you won’t be able to load sites you don’t already know the IP address of, but your browser might have the IP addresses of a few of the major sites (google, facebook, wikipedia) cached locally.
My guess is that all of those other sites use the same ad provider, and that ad provider is slow. Pages really ought to be designed to load everything else anyway while they’re waiting for the ad, but they usually aren’t.
I’m going to guess DNS, as above. Depending on how computer-savvy you are, there are diagnostic steps you can use to confirm. If you can open a command window (Start > Run > cmd) you can us ‘nslookup’ to query your DNS server and see if it’s responding.
I’ve run into this before, and it had to do with being unable to reach a DNS server. Those sites had their DNS cached, and thus worked.
I have also run into this problem on Wi-Fi, and I still don’t know the cause. It definitely was not a DNS thing, and it didn’t happen when directly connected.
It could, especially if they’re all full of background scripts, which many commercial sites are now. OTOH, that doesn’t explain why some sites reload super quick and other don’t reload at all.
Thanks all. I don’t think it’s an issue of too many tabs open, because it will happen with just one or two; nor of obnoxious scripts because I block those by default, and anyway, the problem will happen even with Web 1.0-type pages which normally load but on these occasions will not, even while Google, etc. will.
Without really understanding much at all, I’m able to run a command window and use nslookup, which in the case of google.com just now returns the following information:
Server: cdns01.comcast.net
Address: 2001:xxx:feed::1
DNS request timed out.
Timeout was 2 seconds.
Name: google.com
Address: 2607:f8b0:400a:xxx:100e
(Note: in a hyperabundance of caution I have changed two sets of 3 digits to x’s above, on the off-chance they reveal too much about my personal location.)
How would you interpret that? What other things might the command return on a different occasion or with a different input than google.com, that would mean something else?
There’s almost no reason not to use Google’s public DNS, unless you in a work intranet environment where your local DNS will have stuff that public DNS’s don’t.