Back in 2014 they wanted a $10k/yr minimum.

This happened to us (Weebly) years ago when we had godaddy as our registrar. I highly suggest you transfer your domain to someone competent like Safenames or MarkMonitor.

SSL requires additional CPU resources, and is often coupled with hardware acceleration. All of this equates to higher hosting costs.

We (Weebly) had 18Gbps of UDP/123 (NTP) traffic sent our way on New Years eve -- definitely one of the larger attacks we've seen recently.

This sound like what brought down the GnuPG main site. Sounds like an Anonymous(TM)-type thing.

9 of the 13 root servers were taken down via a DDoS back in 2002.

http://c.root-servers.org/october21.txt

Although the report states "2.4. There are no known reports of end-user visible error conditions during, and as a result of, this attack.", it's not entirely accurate. I personally experienced issues with name resolution shortly after the attack started, and had no idea what the cause was until afterward. If I recall correctly, my name resolution was handled by Qwest, as they were the T1 transit provider I was using at the time.

UDP flood on port 80? With a bit of cooperation from your upstream, this should be one of the easier attacks to mitigate.

Anyone recall the ability to see where your friends last logged in from at their school? ex: "Chris last logged in from Simmons Hall".

I found it pretty interesting they had these names, given the rDNS didn't resolve to anything descriptive.

When did it do that? I was in pretty early, but dont remember that one....woulda been nice!

It ended in September 2006. It was cool because you could see the other person's IP, which was useful because you could then use your Google analytics to see which hot girls were clicking the links from your facebook profile to your home page.

I totally forgot about this, but remember seeing my friends "in the library" or dorm room.

More specifically, it broke down at metadata operations.

We currently have the ability to upload your own theme and customize existing themes, in development. Shoot me an email, chris (at) weebly.com, and I'll give you access. Otherwise, this feature should be live early next week =)

I agree. Simply disabling an account that was used at more than one ATM within a certain timeframe, based on geographic area, would have limited the damage. Similar to how cell phone cloning is detectable.