Trouble connecting to website on GoDaddy

[#1]

This is a weird one.  As of yesterday I stopped being able to connect to my GoDaddy website: www.simlogical.com via my Plusnet FTTC connection.  I can still connect fine via my phone's mobile data.

I don't think it's anything wrong with my browser setup as it is the same trying it from other devices in out home using the same connection.  I don't think it's anything wrong with the router setup as it's not been changed or restarted since long before this problem started.

I have asked some friends to test, and at least one person, using Verizon in the USA also has the same trouble connected.  Using the IsItUp type of services, two say it's up and one says it's down.

Godaddy themselves say they can't see any problem with the site, and I can actually connect ok to someone else's site hosted at Godaddy.  

What on earth can I try next?

[#2]

The site loads OK using FTTC for me. What do you get if you try a tracert to the site?

[#3]

C:\Users\Inge>tracert simlogical.com

Tracing route to simlogical.com [68.178.254.124]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.1.254
2 15 ms 15 ms 14 ms lo0-central10.ptn-ag03.plus.net [195.166.128.192]
3 41 ms 15 ms 59 ms link-b-central10.ptn-gw02.plus.net [212.159.2.138]
4 15 ms 14 ms 14 ms xe-5-3-0.ptw-cr02.plus.net [212.159.0.110]
5 16 ms 17 ms 16 ms 195.99.126.182
6 16 ms 16 ms 18 ms 166-49-211-228.eu.bt.net [166.49.211.228]
7 82 ms 82 ms 82 ms ixp1-xe-0-0-0-0.us-nyc.eu.bt.net [166.49.208.27]
8 82 ms 82 ms 82 ms nyc2-brdr-01.inet.qwest.net [63.146.27.193]
9 * * * Request timed out.
10 140 ms 139 ms 139 ms 63-232-81-254.dia.static.qwest.net [63.232.81.254]
11 * * * Request timed out.
12 140 ms 139 ms 140 ms ip-184-168-1-138.ip.secureserver.net [184.168.1.138]
13 139 ms 140 ms 140 ms ip-184-168-1-137.ip.secureserver.net [184.168.1.137]
14 140 ms 139 ms 140 ms ip-184-168-1-134.ip.secureserver.net [184.168.1.134]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

[#4]

That's odd, mine ends up transitting the same routers but gets a response from the destination at hop 17.

C:\>tracert simlogical.com

Tracing route to simlogical.com [68.178.254.124]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dsldevice.lan [192.168.1.254]
  2    22 ms    21 ms    38 ms  lo0-central10.pcl-ag04.plus.net [195.166.128.185]
  3    22 ms    22 ms    22 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.174]
  4    25 ms    22 ms    22 ms  xe-0-2-0.pcl-cr02.plus.net [212.159.0.206]
  5    24 ms    25 ms    23 ms  195.99.126.98
  6    24 ms    24 ms    23 ms  core3-te0-9-0-27.faraday.ukcore.bt.net [109.159.249.179]
  7    24 ms    25 ms    25 ms  213.137.183.38
  8   110 ms   106 ms   106 ms  166-49-208-183.eu.bt.net [166.49.208.183]
  9   102 ms   101 ms   102 ms  166-49-169-110.eu.bt.net [166.49.169.110]
 10     *        *        *     Request timed out.
 11   156 ms   160 ms   156 ms  63-232-81-254.dia.static.qwest.net [63.232.81.254]
 12     *        *        *     Request timed out.
 13   157 ms   156 ms   158 ms  ip-184-168-1-138.ip.secureserver.net [184.168.1.138]
 14   157 ms   157 ms   156 ms  ip-184-168-1-137.ip.secureserver.net [184.168.1.137]
 15   158 ms   157 ms   161 ms  ip-184-168-1-134.ip.secureserver.net [184.168.1.134]
 16     *        *        *     Request timed out.
 17   159 ms   158 ms   158 ms  p3slh027.shr.phx3.secureserver.net [68.178.254.124]

Trace complete.

You could try disconnecting from Plusnet and reconnecting to see if you get a different gateway (presently ptn-ag03) and different results.

[#5]

And, this morning suddenly, I can connect!  Two days mysteriously broken, day three just as mysteriously fixed