Amazon is refusing to work on new EE Broadband.

[kevsully]

Hi, We've just upgraded to full fibre 900mb.  All devices connected no issues. TV streaming all good. Website access all good.   But Amazon seems to refuse. I've cleared all cache, I've rebooted the router, I've tested on various browsers. I've not got any other Amazon devices connected.  WOrks no issues via iPhone.  But not on laptop.   Just whirrs.  Cannot even logon since the 2 phase authorisation "enter the code" page never materialises on the laptop. 

e-Bay= instant access.  Google searches all instantly. Clicking onto any new websites and we get instant access. 
What's going on with Amazon and EE Fibre? 
Fails on Edge and Chrome and Safari  - so it's not the browsers or cache?
Fail on WI-fi or Ethernet connection. 
Wierd !! 

Any suggestions ? 

[kevsully]

THANKS for the input all.  Much appreciated.
AN UPDATE :-   
I decided to strip it back and restart everything.  I wiped all cache from browser on Windows (Chrome) 
I checked the patch cables (I have a Netgear Switch in Attic which feeds ethernet into all rooms).  So its "EE Router" to "Netgear Switch" to "Room Data port"  to "Laptop".   SPeed tests whow 900+ Mb and all works well. 
Yes I also have  Wi-fi and may not need the ethernet cables at all now, but it's there and all works superbly. Expecialy for Laptop to my NAS. 
I RESTARTED the Hub to ensure there were no crossed IP issues.  I restarted the laptop. 
WI-FI OFF on Laptop.   
Connected to browser and although Google and other sites  were INSTANT.   
Amazon.co.uk was slow to load  when I clicked on  SIGN IN.   A delay butthen something happened and unlike before - the sign in page appeared. Then the authentication page as normal and it seemed like it had woken. 

I was in.. I clicked on one of their links and........ DELAY DELAY DELAY then their page finally loaded..   

I click on their "gift ideas" link  and the little whirring logo whirred  and whirred , which is never normal . The Text arrived (grid mode)  instantly but no images and the page doesn't fully load for about 15 seconds or so.   
So it's working but very very slowly.

@Richardr66   So I tried Amazon.com  rather than .co.uk  as suggested  - the page simply wont load.  NOTHING after over 5 minutes. BLANK. 
Google.com  - instant.  Other US  based .com sites all instant access.  e-bay instant load.   BT , Youtube, Dell.com   ALL instant.     (yes I know some of .com's will have UK based entry points etc etc but.....  that aside) 
Amazon.com never loaded after over 5 minutes of whirring. 
Conclusion - Amazon doesn't like EE Fibre to Ethernet. 
SO I bypassed the switch. 
ROUTER to PatchPanel to ROOM Port (removed the switch) and used a different ROMM PORT. 
SAME ISSUES AS ABOVE.  

 SO - I move from Ethernet to Wi-Fi only. 
Disconnect the ethernet cable. 
ALL WORKS .  All pages open including Amazon.com  (within seconds). 
SO..,,, ,   at the moment  I am concluding,  that although this may appear to be MY network/Ethernet issue,  because ALL other websites appear to work perfectly over same ethernet  and as far as I am concerned, ONLY Amazon fails, then there is an issue between Amazon and the EE network .  Somewhere. 

[Jacob_]

Well that sounds like it's definitely software related, not anything with your smart hub.

If you can do windows key + R and type in cmd.exe and when it pops up do this:

ping www.amazon.co.uk -f -l 1472

^ if this doesn't work and you get a response like:
Reply from 192.168.1.1: Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
then set 1472 to 1464, 1452, 1440, 1432 

Until you actually get a ping response, then you add 28 (1464 being the payload + 28 being the IP+ ICMP headers) so it gives you 1492, that would be your MTU, which you can set on your host or on your router.

I would try and disable Norton for testing. Chrome and Edge are both based on the same engine (Chromium) so technically "the same browser".  Norton could be blocking certain domains that amazon website needs to function. i.e:

amazon.co.uk, www.amazon.co.uk , amazon.com, amazonaws.com, media-amazon.com, ssl-images-amazon.com, images-eu.ssl-images-amazon.com , m.media-amazon.com

You could also try an incognito session (ctrl + shift +n)  incase you have any addons installed such as adblock, ublock origin etc. Another option is to open web developer, so open a new tab, navigate to amazon.co.uk - press F12 - then reload the page, check the console to see if you're getting any issues like ":ERR_BLOCKED_BY_CLIENT" etc.. I have a suspicion it's Norton or an addon you have. 

I just noticed you said you have a patch panel and switch, what switch are you using? Edit: I see you said Netgear, is it a managed or unmanaged switch?

[Jacob_ · Accepted solution]

Just another response, Norton often will often treat "Public" and "Private" connections differently, so I would maybe change the Ethernet connection to Private to see if it makes a difference..

Start -> Settings -> Network and INternet -> Click your Ethernet adapater -> under network profile, select private network. It's an easy way of checking IF Norton is putting restrictions on your connection.

[kevsully]

This made a difference. No idea why it was set to PRIVATE but setting it to PUBLIC which is 'recommended'  (I'm on a home closed network), seems to have resolved it. Live and learn eh!.
Thanks Jacob.

Although its bizzarre that its only Amazon that was affected.

[Jacob_]

No worries, glad it sorted it.. Norton is a bit of a pest in my opinion when it comes to Antivirus etc, what's probably happened is when you've had the ethernet plugged in at some point it's recognised the network and defaulted the settings to that. Then when you may of connected the ethernet somewhere else it's defaulted to a different network profile.  You should check your Norton settings, Smart Firewall / Intrusion Prevention / Web Protection  something along those lines, chances are they haven't blocked Amazon, but most likely a resource Amazon was trying to call, either javascript from a CDN or possibly one the asset-cdn's from Amazon, which would just cause the website to fail if it's not allowing the client to load the required libraries.  See if there's any way to add exemptions for certain domains, Amazon relies heavily on cloudfront which is Amazon web services own low-latency CDN. So double check if there's any blocked domains etc in Norton.