I have bypassed my router with a direct cable connection to the modem, turned off web acceleration, reset the MBX, and have attempted rebooting the modem. The problem is across computers, users, and browsers. I have attempted shuting off windows firewall and antivirus. All to no avail. Yesterday, while in the middle of browsing Amazon, images suddenly stopped loading. Today, in addition to few or no images, Amazon tries to load at a snails pace but the CSS never fully loads. This problem ONLY occures with Amazon and only started occuring yesterday. I have attempted clearing cookies and cache and uninstalled all extensions and tried incongnito mode and tried both chrome and explorer, but as I said, this problem is either at the modem or upstream from it. It doesn't matter if I'm using my laptop on wi-fi, my tower with network cable, any windows user, any browser, the problem persists. It only affects Amazon.com.
After a couple of trouble free days shopping on Amazon, the problem returned. I followed the same procedure as before and it appears to have resolved the issue, for the time being. I did a trace to Amazon while connected thru the router, both before and after the fix.
Before:
And After:
Unfortunately, I forgot to do a trace without the router prior to the fix, but I did take a trace without the router after.
Personally, I have no idea what the rest of you might see in these tea leaves. If the problem persists, I'll continue to remove steps from the solution to narrow it down.
Haven't had the Amazon problem today, myself, but I ran the traceroute just for the heck of it. Looks a lot different, though I don't know what any of it means.
@MarkJFine wrote:Google's DNS tend to work better, but are sometimes spoofed. Just need to be careful that you don't get re-routed to some sketchy part of the dark web.
Yep, one good thing about Chrome is it usually opens a new tab when redirected and I kill it immediately. Never visited the true dark web and no wish to. A bit like visiting North Korea IMO, why would one want to.
The "dark" web is called that for a reason.
Back to the real issue, I don't have the issues this topic brings up. I've used Google DNS servers for years now, I do remember issues back when I used default HughesNet servers. Sorry HughesNet. 
@BirdDog wrote:Personally don't care for the HughesNet DNS servers, I use the Google public ones, 8.8.8.8 and 8.8.4.4. No idea if anything to do with the problem but throwing it out here. Have'nt had this kind of problem for a long time since I switched servers.
For me, very oddly, and still, the problem doesn't seem to crop up nearly as much when using Hughesnet's DNS. Normally I use Google's, but on a whim I changed it back to Hughesnet's just to see what would happen, and since doing so I haven't had the problem pop up nearly as much. Just once or twice since changing, whereas usually it would happen more often than not when going to Amazon. That's not a joke. It was awful.
With that said, though, my issue may be a little different than the OP's, or even others that are posting, as when I would have the problem the page wouldn't load at all. It would give me an error. This is with a desktop using Windows 10 FCU and Chrome. But, as to why Hughesnet's DNS seems to work better for me, at least when it comes to Amazon, I'm stumped, as Google's should be the one to work better when going by the general success rate between the two.
Here's what I see when it happens, and again, no joke, it used to happen more often than not. This problem started for me about four months ago. But, with that said, I changed back to Hughesnet's DNS around the time of the W10 FCU, so that may have something to do with it, too. The following is a snapshot from a few weeks ago.
I should point out that if it keeps recurring for a specific site, such as Amazon, it's quite possible a rogue site or rogue ad is likely spoofing that local DNS entry... that includes some of those embedded "mraid" ads you get in phone apps.
And, before anyone says that they can't, I'm dealing with a ad company (to remain nameless) that rotates ads through some javascript code. They didn't know that one of their ads forwards to another malicious ad that captures the site (e.g., not a popup) for a phony Amazon Gift Card that's only targeted to Apple iPhones. Two guesses what else it does, and the first one don't count...
Though this is a little off topic, if I had all of those $50 Amazon Gift cards that I supposedly won I'd be a rich man. Every day there's another one or two in my spam, and every day it's a new domain, so blocking them is practically impossible. Still, it's somewhat comical how many I'm supposed to have won over time. Hundreds. 😛
