Welcome to WebmasterWorld Guest from 220.127.116.11
Forum Moderators: rogerd
The problem with twitter having a DoS attack is that everyone and all the automated junk trying to get onto twitter causes the next DDoS attack just trying to use the system while it's already overloaded.
My guess is that this meltdown will take more than a few minutes to mellow out once people start getting twitter pages because everyone will then immediately post something causing yet another DDoS.
At least TV stations can broadcast a test pattern ;)
You may have had trouble accessing Facebook earlier today because of network issues related to an apparent distributed denial-of-service attack. We have restored full access for most people. We’ll keep monitoring the situation to make sure you have the reliable experience you expect from us.
Did you hear that Google, Twitter and Facebook are teaming up to locate the source of the DDoS? Yup, a real live man/woman hunt. Someone is going to pay! Maybe.
Update (4:14p): Site latency has continued to improve, however some web requests continue to fail. This means that some people may be unable to post or follow from the website.
Twitter, Facebook attack targeted one user [news.cnet.com]
A Georgian blogger with accounts on Twitter, Facebook, LiveJournal and Google's Blogger and YouTube was targeted in a denial of service attack that led to the site-wide outage at Twitter and problems at the other sites on Thursday, according to a Facebook executive.
The blogger, who uses the account name "Cyxymu," (the name of a town in the Republic of Georgia) had accounts on all of the different sites that were attacked at the same time, Max Kelly, chief security officer at Facebook, told CNET News.
"It was a simultaneous attack across a number of properties targeting him to keep his voice from being heard," Kelly said.
Once what was happening was public, the use of spam was going to mean that the identity of the target (or at least the pseudonym he uses on his blog, which is what Facebook revealed) was going to be easy to work out anyway.
I'm really unimpressed by Twitter's failure to anticipate a DOS Attack and its failure to put in place a system to prevent it from being taken out. I mean, come on, it's 2009!
Have you ever tried to stop a DOS?
I have, some are simple, some aren't so simple.
When you have the raw amount of customers connecting that Twitter has it can be a challenge to initially sort out the problem connections from the actual users, especially when a botnet is being deployed that can actually use valid twitter member machines to attack the service itself.
After I read what the news claimed happened, I'm surprised they didn't just firewall off a few eastern European countries to slow down their ability to assault the system.
Heck, I finally permanently blocked a few Asian countries due to high volumes of spam, hack attacks and repeated high speed scrapers because eventually the business prospects don't outweigh the danger those areas pose to the server.