Can anyone get to webreseller.net ?
I heard about yipes maintance, but didn't get an email in regard to if webreseller would be effected.

www.webreseller.net

DOS Attack that we are working on..

Yah, its been on and off for the last 20 minutes with the heavy packetloss.

EDIT: Jeez those guys are fast, guess the above post explain it.

http://www.webhostingtalk.com/showthread.php?s=&threadid=92270

as you see i having probs too

site is down for me.
but box is pingable

xtroot:~# ping webreseller.net
PING webreseller.net (66.54.216.242) from 140.99.28.26 : 56(84) bytes of data.
64 bytes from webreseller.net (66.54.216.242): icmp_seq=0 ttl=242 time=76.671 msec
64 bytes from webreseller.net (66.54.216.242): icmp_seq=1 ttl=242 time=79.938 msec
64 bytes from webreseller.net (66.54.216.242): icmp_seq=2 ttl=242 time=79.916 msec
64 bytes from webreseller.net (66.54.216.242): icmp_seq=4 ttl=242 time=79.923 msec
64 bytes from webreseller.net (66.54.216.242): icmp_seq=6 ttl=242 time=79.316 msec
64 bytes from webreseller.net (66.54.216.242): icmp_seq=8 ttl=242 time=79.840 msec
64 bytes from webreseller.net (66.54.216.242): icmp_seq=9 ttl=242 time=79.921 msec
64 bytes from webreseller.net (66.54.216.242): icmp_seq=10 ttl=242 time=79.922 msec
64 bytes from webreseller.net (66.54.216.242): icmp_seq=12 ttl=242 time=79.923 msec
64 bytes from webreseller.net (66.54.216.242): icmp_seq=13 ttl=242 time=79.918 msec
64 bytes from webreseller.net (66.54.216.242): icmp_seq=14 ttl=242 time=79.835 msec
64 bytes from webreseller.net (66.54.216.242): icmp_seq=18 ttl=242 time=79.932 msec
64 bytes from webreseller.net (66.54.216.242): icmp_seq=21 ttl=242 time=79.907 msec
64 bytes from webreseller.net (66.54.216.242): icmp_seq=22 ttl=242 time=79.942 msec

--- webreseller.net ping statistics ---
25 packets transmitted, 14 packets received, 44% packet loss
round-trip min/avg/max/mdev = 76.671/79.636/79.942/0.836 ms

Matter has been resolved... It was an attack..

Bastards!!! The sad part is someone just doesn't have anything better to do. Why not put their ability to good use instead of this crap. Happy Holidays!!!

I must say I am pleased and impressed with the response times to these attacks.

When we are attacked, that means everyone is getting attacked indirectly. Sorry for the problems....

Kudos to Webreseller for resolving the issue so quickly that I didn't even notice the problem :)

Originally posted by twrs
Kudos to Webreseller for resolving the issue so quickly that I didn't even notice the problem :)

No kudos from me. I have a server down for about 4 hours now and webreseller is not keeping us updated. I have no idea what's going on with the server other than a hardware issue. They aren't answering their phones, emails, or pagers. Very disturbing.

They're down again at 2 O'Clock Eastern Time on Saturday November 30th.

heavy packetloss here :(
___________

4 bytes from 66.227.26.1: icmp_seq=6 ttl=242 time=6.488 ms
64 bytes from 66.227.26.1: icmp_seq=10 ttl=242 time=6.526 ms
64 bytes from 66.227.26.1: icmp_seq=16 ttl=242 time=5.981 ms
64 bytes from 66.227.26.1: icmp_seq=20 ttl=242 time=7.178 ms
64 bytes from 66.227.26.1: icmp_seq=26 ttl=242 time=6.044 ms
64 bytes from 66.227.26.1: icmp_seq=30 ttl=242 time=6.739 ms
64 bytes from 66.227.26.1: icmp_seq=34 ttl=242 time=6.724 ms
64 bytes from 66.227.26.1: icmp_seq=36 ttl=242 time=6.534 ms
64 bytes from 66.227.26.1: icmp_seq=40 ttl=242 time=6.706 ms
64 bytes from 66.227.26.1: icmp_seq=46 ttl=242 time=6.332 ms
64 bytes from 66.227.26.1: icmp_seq=50 ttl=242 time=7.464 ms
64 bytes from 66.227.26.1: icmp_seq=56 ttl=242 time=6.365 ms
64 bytes from 66.227.26.1: icmp_seq=60 ttl=242 time=29.931 ms
64 bytes from 66.227.26.1: icmp_seq=66 ttl=242 time=5.981 ms
64 bytes from 66.227.26.1: icmp_seq=70 ttl=242 time=6.866 ms
64 bytes from 66.227.26.1: icmp_seq=76 ttl=242 time=6.399 ms
64 bytes from 66.227.26.1: icmp_seq=80 ttl=242 time=6.661 ms
64 bytes from 66.227.26.1: icmp_seq=86 ttl=242 time=5.882 ms
64 bytes from 66.227.26.1: icmp_seq=90 ttl=242 time=5.891 ms
64 bytes from 66.227.26.1: icmp_seq=96 ttl=242 time=6.472 ms
64 bytes from 66.227.26.1: icmp_seq=100 ttl=242 time=6.506 ms
64 bytes from 66.227.26.1: icmp_seq=106 ttl=242 time=5.943 ms

118 packets transmitted, 25 packets received, 78% packet loss
round-trip min/avg/max/stddev = 5.882/7.478/29.931/4.606 ms
bash-2.05a$

Looks like another attack... wonder who hates them so much :bawling:

matter has been resolved in less then 15 minutes, we are very close to finding out who..

Originally posted by webreseller
matter has been resolved in less then 15 minutes, we are very close to finding out who..

you found out who it was ? or still looking?

Just wondering what do you usually do in such case? Do you implement some kind of IP filtering or you just close the user's box right away without notifying him first?