Single website times out on my connection only
Odd one this... As of yesterday, my design business website http://www.swashandfold.com (which obviously I need to access) is inaccessible via my home connection. However the site is up (http://www.isup.me/http://www.swashandfold.com/), working fine for other people, and accessible over mobile data connection. Just not for me via any machine connected to my Plusnet fibre. 
I get "timed-out" errors (or the platform equivalent) whether I try Chrome, Firefox, my Win 10 machine, my OSX machine, FTP clients or pinging the server.
I've tried the following:
... and I'm kind of out of ideas now. Its very strange. In actual fact, I don't think its a DNS issue since ping resolves it ok. But its the actual server (109.123.71.220) which isn't playing ball over Plusnet.
I'm not ruling out UK2 of course - there could be something going on their side. But trying to rule out all options.
Any thoughts?
I get "timed-out" errors (or the platform equivalent) whether I try Chrome, Firefox, my Win 10 machine, my OSX machine, FTP clients or pinging the server.
I've tried the following:
- Google DNS and OpenDNS (on my machine)
- Google DNS and OpenDNS telnetted and changed on my router (Technicolor TG582n)
- Checked any Firewall settings locally, on my account settings, and on my web host (UK2)
- Checked for any IP blocking on my web host
... and I'm kind of out of ideas now. Its very strange. In actual fact, I don't think its a DNS issue since ping resolves it ok. But its the actual server (109.123.71.220) which isn't playing ball over Plusnet.
I'm not ruling out UK2 of course - there could be something going on their side. But trying to rule out all options.
Any thoughts?
Based on what you've posted this is a bit left-field but have you always been using Google DNS and is all of the site hosted remotely from your LAN? I ask because some routers like mine use DNS to provide(*) NAT loopback facilities. In that situation if you change to Google DNS it will prevent you accessing anything that you host yourself.
( https://en.wikipedia.org/wiki/Network_address_translation#NAT_loopback )
(*)'Fake' may be a better term for it
( https://en.wikipedia.org/wiki/Network_address_translation#NAT_loopback )
(*)'Fake' may be a better term for it
Have you checked to see if your IP has been blacklisted by your host's server, it can happen 
Quote from: Den1 Have you checked to see if your IP has been blacklisted by your host's server, it can happen
Thanks for input all... yep, as Den1 suspected (and I'd been leaning towards myself), it seems to have been down to a particularly thorough session of multi-device, multi-browser responsive CSS development.
It seems UK2 considers synchronised browsing using Adobe Edge Inspect as the equivalent of a Wordpress attack, so decided to block my Public IP. Cheers UK2!
Anyway, thanks again for suggestions!