Forum Discussion

whysalives's avatar
whysalives
Sophomore
8 years ago
Solved

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...
  • Amanda's avatar
    Amanda
    8 years ago

    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

C0RR0SIVE's avatar
C0RR0SIVE
Associate Professor
8 years ago
whysalives wrote:

 

Here is a trace with a direct cable connection from the modem to my laptop:

 

For some reason that trace doesn't strike me as normal... Not used to seeing a lot of in-addr.arpa entries like that.

All that aside, it could have been anything really... Amazon, DNS, broken routing somewhere... No telling.

MarkJFine's avatar
MarkJFine
Professor
8 years ago

Yeah, almost looks like either qwest or most likely amazon.

Did notice that the IP resolved from 54.239.25.208 before complete reboot to 54.239.17.6 after, so could have also been the local DNS getting stuck on something weird.

 

Edit: Either way... looks like a team win.

  • GabeU's avatar
    GabeU
    Distinguished Professor IV
    8 years ago

    For some reason I tend to have a lot of issues with Amazon.  Not much else, but Amazon gives me non connection issues on a semi regular basis.  What I usually do to rectify it is flush the DNS.  It happens most often when I am using Google's DNS, not when I'm using Hughesnet's.  The DNS flush normally does the trick, though the issue does tend to crop back up after a time.  

     

    I don't know what it is about Amazon that causes this, but I don't see it very often with other web sites.