MalcolmNathaniel
Posts: 1394
Joined: 9/20/2010 Status: offline
|
OK, here's why I know it's not your browser (the short version*) Your browser sends a request to the OS for a DNS lookup. The operating system is in charge of sending a request to the DNS server to translate "www.collarchat.com" into 72.13.91.174. Your browser then sends a message to the OS for a connection to 72.13.91.174:80 with a standard HTTP CONNECT. The server responds with a string of text in HTML (which may or may not include JAVA, FLASH or what have you) or it responds with an error code or it doesn't respond at all. Because I used a separate server (www.downforeveryoneorjustme.com) which uses, presumably, different DNS servers, and a different line it is suggests that, assuming a backbone isn't down, that it is the server or the connection to the server that is down. Because I can reach "down for everyone" I know that my connection is alive and kicking. I also know that my browser hasn't had a brain fart. Since I usually have between 10 and 20 pages open at a time I just go somewhere else for 15-20 minutes. This can be caused by a lot of things. My top two guesses are: the server is reaching it's limits as to the database technology employed or someone is spamming the server hard at times and clogging the connection. My next two guesses are memory or drive fragmentation. Bear in mind that I have no idea what OS/DB/Webserver is being used here, nor do I know what hardware it is running on. These are just guesses as to why it goes down. *This isn't the proper venue (or forum, if you will) for an in depth discussion on the technicalities.
|