UPDATE: The attack may have been caused by a DNS redirect. We're investigating: http://bit.ly/4Il4iY
11:57 PM - 17 Dec 2009
0 replies
80 retweets
12 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.