Sky broadband is successfully trace-routing to an inmotion server but BT is not
My friend and I share a common hobby where our club website is reached via an inmotion server (cottontownchorus.co.uk).
That website domain name is the same as it always has been but was recently moved to a new host, so the DNS records were all changed.
In my own case, I have Sky Broadband and I can access the website without a problem. My tracert gives me the following:
Tracing route to cottontownchorus.co.uk [220.127.116.11]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 6 ms 6 ms 6 ms 18.104.22.168
3 11 ms 10 ms 10 ms 02780e57.bb.sky.com [22.214.171.124]
4 11 ms 11 ms 11 ms 02780d57.bb.sky.com [126.96.36.199]
5 137 ms 135 ms 135 ms ae22.cr3-lax1.ip4.gtt.net [188.8.131.52]
6 135 ms 135 ms 135 ms edge1.lax2.inmotionhosting.com [184.108.40.206]
7 135 ms 135 ms 134 ms edge1.lax2.inmotionhosting.com [220.127.116.11]
8 135 ms 135 ms 135 ms csw1.lax2.inmotionhosting.com [18.104.22.168]
9 135 ms 135 ms 136 ms server1.harmonysite.com [22.214.171.124]
On the other hand, my friend has BT Broadband. Even having cleared browsing data, and done the usual round of reboots, he cannot reach the same website and gets this when he tries to tracert:
He can reach the website when he comes off wifi and goes onto 4G, so the issue looks to be localised to his BT router ??
I notice that the hops through InMotion are via different servers - don't know if this is relevant.
Any thoughts what we can try other than contacting BT to see if anything is blacklisted ?