I’ve heard stories from other Twitter Folks about it being Denial of Service attack:
[ad#cricket-right-ez]
Now it is possible to have[intlink id=”3236″ type=”post”] Conficker to all botnets[/intlink] to try to go to the site but I am not certian it is the Conficker. It could be as simple as someone misconfigured a server and no one can get to it. People who want to check out what people on twitter are saying can search for it and see for yourself. I’ll update as needed when I find out more, but it will probably be a couple of hours before the site is back up, according to some reports. I’ll know more later today, so keep tune.
Update at 6:30pm EST
We speculate that the source of the problem may have been a large scale Denial of Service attack against UltraDNS, or an internal operations problem. When we were able to sucessfully query UltraDNS servers, responses were slow to come back, or largely timed out. The problem began to clear itself up around 10:00 am Eastern, when we saw DNS responses returning quickly again, and our favorite sites coming back online.
[Via DynamicNetwork Service Inc.]
It looks like this might of been the cause for Amazon, and some other sites including the Register. I’m not quite sure what happened but someone talks about it on Redidit:
Wed Apr 01 | 14:37:03 >: nslookup xxx.xxx.com ;; connection timed out; no servers could be reached
Edit: Just got off the phone with Register.com support. The technician admitted to me that they have had a “server failure” and the problem is affecting all of their customers.
Although this post suggest they had a server failure, I am not quite sure what happened but I am going to let you figure that out!! This is some really good information go on Twitter. So you can try to figure it out some more for yourself.
Oh a side not, I’ve gotten the right RSS feed working, if you want to subscribe to my site and get automatic updates with full text just subscribe to my feed.