[116557] in North American Network Operators' Group
Re: DOS in progress ?
daemon@ATHENA.MIT.EDU (Marshall Eubanks)
Thu Aug 6 20:21:39 2009
From: Marshall Eubanks <tme@americafree.tv>
To: Christoph Blecker <cblecker@peer1.com>
In-Reply-To: <4A7B4B34.9030808@peer1.com>
Date: Thu, 6 Aug 2009 20:20:21 -0400
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Aug 6, 2009, at 5:29 PM, Christoph Blecker wrote:
> It looks like there is something more widespread today. I've noticed a
> couple other sites having issues. LiveJournal has confirmed they are
> under attack as well:
> http://community.livejournal.com/lj_maintenance/125027.html
>
This is interesting.
http://www.nytimes.com/2009/08/07/technology/internet/07twitter.html
Most computer security analysts did not cite a specific source of the =20=
attack Thursday.
But Bill Woodcock, a research director of the Packet Clearing House, a =20=
nonprofit technical organization that tracks Internet traffic, said =20
Thursday=92s attack was an extension of the conflict between Russia and =20=
Georgia. It was not clear who initiated the attack, he said, but =20
likely =93one side put up propaganda, the other side figured this out =20=
and is attacking them.=94
Instead of using a botnet, or a network of thousands of malware-=20
infected personal computers to flood a site with traffic, Mr. Woodcock =20=
said this particular attack consisted of a wave of spam e-mail =20
messages, which began infiltrating Twitter and other sites at 10:25 =20
a.m. Eastern time. =93It=92s a vast increase in traffic that creates the =
=20
denial-of-service,=94 he said.
YouTube and LiveJournal were also affected, Mr. Woodcock said, =20
although =93Twitter was definitely hit the hardest.=94 YouTube said it =
had =20
not noticed any problems with its service.
-----------------
While I certainly trust PCH, I would be curious as to the evidence for =20=
this.
Regards
Marshall
> Cheers,
> -Christoph
>
> Jorge Amodio wrote:
>> FB flakyness could be related to timeout with Twitter APIs
>>
>> Just reported by the birdhouse:
>>
>> "As we recover, users will experience some longer load times and
>> slowness. This includes timeouts to API clients. We=92re working to =
get
>> back to 100% as quickly as we can."
>>
>
>
