Author Topic: DDoS'd, round two  (Read 1769 times)

All I see is a one pixel wide spike where the mouse cursor is. Something like that is usually a computation error. I know I see it frequently in steam downloads, where the download speed suddenly spikes to an unrealistic level

All I see is a one pixel wide spike where the mouse cursor is. Something like that is usually a computation error. I know I see it frequently in steam downloads, where the download speed suddenly spikes to an unrealistic level

Look at the inbound data numbers. I missed it too, don't worry.

i used to get ddos'd all the time in csgo by random brazilians 

I got ddosed once. And i know why. A competitive advantage in empiresmod.

who the forget is this stuffhead that keeps ddosing everything

who the forget is this stuffhead that keeps ddosing everything

this hacker known as 4 chan

this hacker known as 4 chan

omg anonymous is a big hacker too did you know

this hacker known as 4 chan

He may have been a system administrator.

All I see is a one pixel wide spike where the mouse cursor is. Something like that is usually a computation error. I know I see it frequently in steam downloads, where the download speed suddenly spikes to an unrealistic level
entire server went down, wasn't a computation error
It's so short because I was actively using my server when it began, and took it down immediately.

that sucks man.

next time try doing a null route.

EDIT: nevermind that, i'm pretty sure you could get screwed at any time. this is why i stopped renting my vps, people kept putting it down to stuff.
« Last Edit: August 30, 2015, 02:12:26 PM by blood.fm »

should have downloaded ZEDROWS DDOS PROTECTION™

should have downloaded ZEDROWS DDOS PROTECTION™
Does it protect your email, too?

Does it protect your email, too?
pay an extra 9.99 for AUTISM attack protection

From my little knowledge of computers, I'd assume he wouldn't be able to track a single IP - a DDOS uses many different computers (a botnet).



Sorry for you, OP. I can't see anyone doing anything to you.

Although the attack uses many computers, some ROUTERS dont give different IPs out for the different computers in your house. Some just use one. But for those who don't, either way, theres an easy solution to this problem.

Step One, find out the IP for ONE of the inbound packets.
Step Two, find out the ISP.
Step Three, contact the ISP, sending proof of the attack and logs, requesting they disable this person's ability to use the internet.
Step Three (IF ITS COMCAST), Realize you're screwed when you find out Comcast's costumer service rating.

I don't know if this would really help but its worth a shot.