"GearHost experienced an entire network outage earlier today. This was due to a large DDOS attack against a hosted web site. We are currently working on repairing the problem but we are still under this attack so network connectivity will be intermittent."
From what the owner of gearhost is saying it is... the person who "got the scammer" was very irresponsible. Just think of of the businesses on Gearhost that lost money today. Then again, getting a scammer back, on a personal level, would have been cool. The sender may have also broken some laws using the postal service (unless sent otherwise) to get "even."
If you have not read the story... it is funny though.
what would have been real funny, is if the escrow would have went through... and the scammer turned out to be legit...
I never said the owner said that (not my intention anyway)... that was my openion. The story was not only on slashdot but on every other forum on the net. go to google and type: P-P-P-Powerbook.com. I said he was irresponsible because it cost gearhost to be down for almost 4 + hours, per gearhost site. The guy who got scammed slammed gearhost with an attack... or at least that is what gearhost is claiming.
I do business on the net and I would have been darn mad if someone caused me to lose 4+ hours of sales just to "get even" or show someone a lesson.
Actually, it was due to p-p-p-powerbook.com I understand getting back at someone but there is good in letting things go. A personal vendetta has cost a lot of businesses sales, money etc etc. I personally took a big hit as the downtime came right after I had just come back from advertising at a trade show that cost me 3K... not good. I am just an innocent business owner that got caught in the crossfire :-(
Correct ... as hekwu stated this was due to the p-p-p-powerbook.com site. The attack was against this and this site only but due to the severity of this attack it brought us down, almost our DC that we're in and is now pushing Level3's border routers over 30% normal usage. There are quickly looking for it's root otherwise UUNET will have to block it.