As of about 2:30am EST (if not earlier) the site is acting bogged down, or overworked.
I can sympathize.
NOTE: I am not complaining, just reporting. I hope it isn't anything serious.
As far as I can see paizo.com uses DNS loadbalancing, right now only one of the two IPs has an open http port.
$ host paizo.com
paizo.com has address 188.8.131.52
paizo.com has address 184.108.40.206
paizo.com mail is handled by 0 mail.paizo.com.
$ telnet 220.127.116.11 80
Connected to 18.104.22.168.
Escape character is '^]'.
$ telnet 22.214.171.124 80
telnet: Unable to connect to remote host: Connection timed out
I edited my hosts file for the time being.
|Jeremy Mac Donald|
|Gary Teter Senior Software Developer|
Yeah, one of our servers was very unhappy when I got into the office this morning. A loving kick to the head seems to have brought it around.
Gary, have you considered something more redundant than DNS round-robin loadbalancing yet? I have extensive experience with high-availability loadbalancing setups. If you like and in case you're running Linux on your servers I could compile some relatively easy to implement setups that don't require any additional hardware.