Forum Discussion
Unable to load Amazon, Problem Upstream From Modem
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...
Good morning everyone,
Just got word that Amazon should be working properly now. If you made any workaround changes, please revert back to your original settings and give it a test run.
Thank you,
Amanda
Looks like it's not getting the css. That's usually a DNS issue.
DNS's propagate, so if you're rebooting the modem and router while the computer is up and it's DNS is corrupted, you're not doing anything to clear the computer's local DNS.
Either bring everything down simultaneously or flush the computer's DNS cache.
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.
Same here, after a few days of trouble-free Amazon shopping, I'm unable to utilize the service, once more. It's frustrating having to reboot the modem over and over. Also, I noticed other web sites having similar problems until I reboot the modem, then they all appear normal again. I gather it's a technical glitch on the HughesNet end?
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.
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.
