Weird. The site is very snappy for me, so I'm wondering what would account for this. I would normally think it was some kind of net congestion, but I can't imagine it would be so localized, and besides, we're sort of all scattered around North America so that doesn't make sense.
If any of you want to try something, do this:
1) Open up a command window by going to the Start button, clicking "Run", and typing 'cmd' (without the quotes.
2) Type the following command:
tracert discoverseattle.net
It should start to print out a bunch of stuff showing the 'hops' or path from wherever you are to this server, along with the time in milliseconds. If you see some that timeout or just show an asterisk (*), that indicates a problem. Here's what mine looks like when I do it:
[font style="font-family: Courier New;" size="2"]
Tracing route to discoverseattle.net [69.13.76.123] over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 15 ms 20 ms 10 ms GE-1-1-ur01.bellevue.wa.seattle.comcast.net [68.86.98.17]
4 11 ms * * 10g-9-3-ar01.burien.wa.seattle.comcast.net [68.86.96.66]
5 13 ms 14 ms 10 ms 12.118.106.5
6 12 ms 14 ms 13 ms gbr1-a30s1.st6wa.ip.att.net [12.127.6.142]
7 26 ms 11 ms 21 ms 12.127.6.61
8 13 ms 12 ms 11 ms 192.205.33.98
9 38 ms 38 ms 40 ms dcr1-so-1-0-0.Denver.savvis.net [204.70.193.62]
10 56 ms 54 ms 55 ms dcr1-so-0-0-0.dallas.savvis.net [204.70.192.94]
11 53 ms 64 ms 52 ms bcr1-so-0-0-0.Dallas.savvis.net [204.70.193.9]
12 53 ms 106 ms 54 ms 208.172.130.130
13 55 ms * 54 ms 208.172.130.130
14 * * * Request timed out.[/font]
[font style="font-family: Courier New;" size="2"] 15 * * * Request timed out.
[/font]I'm seeing a bunch of timeouts but they don't seem to be affecting me here, oddly enough. The pages load for me in a second or two at most. I'll touch base with the hosting company and see if they're having some kind of problem.
