Can anyone else see Hostgator sites? For example...

[#1]

For the last 2-3 hours, for many people in the UK Hostgator hosted sites appear down, through various ISPs.
For example, http://forums.hostgator.com http://www.hostgator.com, most of my sites etc, and lots of people tweeting about it: http://search.twitter.com/search?q=hostgator and yet http://downforeveryoneorjustme.com/http://forums.hostgator.com for example, shows it as up.
Here's my tracert
Tracing route to www.hostgator.com [67.215.66.132]
over a maximum of 30 hops:
  1    1 ms    <1 ms    <1 ms  192.168.1.1
  2    34 ms    33 ms    33 ms  lo0.plusnet.thn-ag1.plus.net [195.166.128.101]
  3    37 ms    34 ms    32 ms  vl703.thn-gw1.plus.net [84.92.4.241]
  4    33 ms    32 ms    33 ms  ae0-102.ptn-gw01.plus.net [212.159.1.53]
  5    34 ms    34 ms    32 ms  vl31.ptn-gw02.plus.net [195.166.129.2]
  6    33 ms    34 ms    36 ms  195.66.226.185
  7  126 ms  106 ms  108 ms  te9-3.ccr02.jfk02.atlas.cogentco.com [154.54.5.122]
  8  106 ms  106 ms  106 ms  te4-2.ccr02.jfk05.atlas.cogentco.com [130.117.0.54]
  9  113 ms  113 ms  112 ms  te2-1.mpd01.jfk05.atlas.cogentco.com [154.54.3.106]
10  106 ms  106 ms  106 ms  vl3504.na22.b001105-25.jfk05.atlas.cogentco.com [38.20.36.114]
11  109 ms  110 ms  107 ms  opendns.demarc.cogentco.com [38.104.74.42]
12  110 ms  111 ms  110 ms  hit-servfail.opendns.com [67.215.66.132]

[#2]

Its up for me here, but I have my firewall configured to block ICMP, so I can't run you tracert terribly easily.

[#3]

Fine for me here too.

[#4]

OK for me and here is a tracert which may show a problem in planet.com

Quote

Tracing route to hostgator.com [74.54.219.185] over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  192.168.0.1   2    44 ms    50 ms    41 ms  lo0.plusnet.thn-ag1.plus.net [********]   3    42 ms    54 ms    45 ms  vl703.thn-gw2.plus.net [84.92.4.242]   4    43 ms    42 ms    43 ms  ldn-b4-link.telia.net [213.248.84.197]   5    42 ms    41 ms    42 ms  ldn-bb1-link.telia.net [80.91.249.77]   6    43 ms    44 ms    41 ms  ldn-b3-link.telia.net [80.91.251.237]   7    44 ms    42 ms    40 ms  abovenet-ic-126798-ldn-b3.c.telia.net [213.248.101.106]   8    42 ms    40 ms    46 ms  so-0-0-0.mpr1.lhr2.uk.above.net [64.125.27.225]   9   123 ms   129 ms   119 ms  so-1-1-0.mpr1.dca2.us.above.net [64.125.31.186] 10   160 ms   161 ms   152 ms  ge-2-0-0.mpr3.iah1.us.above.net [64.125.25.114] 11   148 ms   148 ms   152 ms  xe-0-1-0.er1.iah1.us.above.net [64.125.28.5] 12   153 ms   153 ms   154 ms  209.66.99.94.available.above.net [209.66.99.94] 13   152 ms   148 ms   151 ms  et5-4.ibr04.dllstx3.theplanet.com [70.87.253.53] 14   150 ms   149 ms   150 ms  te9-2.dsr01.dllstx3.theplanet.com [70.87.253.14] 15     *        *        *     Request timed out. 16   426 ms   233 ms   211 ms  te1-1.car05.dllstx6.theplanet.com [70.87.254.170] 17   153 ms   149 ms   148 ms  crunchy.hostgator.com [74.54.219.185] Trace complete.

[#5]

Hmmm, this is all very odd. Thanks for the info - I might try another DNS server perhaps, but it does appear to be lots of other people on other ISPs too

[#6]

I use OpenDNS for mine, and I suspect Adie and OJ might not use PNs DNS either.

[#7]

I am using PN DNS and the site worked for me

[#8]

I am using the Plusnet automatic ones
212.159.6.10
212.159.6.9

[#9]

Quote from: James_G

I use OpenDNS for mine, and I suspect Adie and OJ might not use PNs DNS either.

I used OpenDNS to..

[#10]

Ah well, half right in my suspicions. (If I were in a pedantic mood I might be tempted to declare that my previous logical statement was 100% correct.  )

[#11]

Ah, so it's not OpenDNS either. I'll stick with them because...ah, wait - it's just come back!
Hurrah! OK for me here now. Thanks for your help.

[#12]

Quote from: racquel

Tracing route to www.hostgator.com [67.215.66.132] over a maximum of 30 hops:   1     1 ms    <1 ms    <1 ms  192.168.1.1   2    34 ms    33 ms    33 ms  lo0.plusnet.thn-ag1.plus.net [195.166.128.101]   3    37 ms    34 ms    32 ms  vl703.thn-gw1.plus.net [84.92.4.241]   4    33 ms    32 ms    33 ms  ae0-102.ptn-gw01.plus.net [212.159.1.53]   5    34 ms    34 ms    32 ms  vl31.ptn-gw02.plus.net [195.166.129.2]   6    33 ms    34 ms    36 ms  195.66.226.185   7   126 ms   106 ms   108 ms  te9-3.ccr02.jfk02.atlas.cogentco.com [154.54.5.122]   8   106 ms   106 ms   106 ms  te4-2.ccr02.jfk05.atlas.cogentco.com [130.117.0.54]   9   113 ms   113 ms   112 ms  te2-1.mpd01.jfk05.atlas.cogentco.com [154.54.3.106] 10   106 ms   106 ms   106 ms  vl3504.na22.b001105-25.jfk05.atlas.cogentco.com [38.20.36.114] 11   109 ms   110 ms   107 ms  opendns.demarc.cogentco.com [38.104.74.42] 12   110 ms   111 ms   110 ms  hit-servfail.opendns.com [67.215.66.132]

This shows what the problem was and shows one of the main problems with OpenDNS.
For some reason OpenDNS couldn't resolve www.hostgator.com (possibly because of domain registration problems). Most DNS servers will normally give an error message at this point, however the OpenDNS DNS servers are configured instead to substitute the IP address of one of their own servers (ie hit-servfail.opendns.com [67.215.66.132]). As a result your traceroute shows a route to a OpenDNS system, and not to hostgator. This can obscure what the real problem is.
Mike

[#13]

Yeah, I thought as much. Although it wasn't an OpenDNS problem. I used to have so many problems with Plusnet DNS not resolving this or that, or being slow (both to respond and update), and things have been a lot quicker since switching to OpenDNS. Do you think it's safe to try plusnet DNS again? It's been 3 months now, have they updated the servers?

[#14]

TBH I don't know as I'm also using OpenDNS, mainly because I find their logging and site filtering handy enough to put up with the occasional problem
Mike