vld
Joined 15 years ago
Joined 15 years ago
Give httping [0] a try for benchmarks.
This is the reply I got from their support, just a few days ago:
>In short, our DDoS protection works by filtering out DoS-like traffic and is applied via the Linode network, so all Linodes are automatically protected. If your server were to be on the receiving end of a larger attack that impacts the Linode's host, we would need to prevent your server from receiving traffic until the attack ends. If you're concerned that you might be the target of a large DoS attack, there are a number of third-party DDoS mitigation services that you can use alongside your Linode.
>We aren't able to provide specific numbers since effects can vary depending on the attack. If you wanted to be sure your Linode is protected, we would recommend utilizing a third-party DDoS protection service overtop of your Linode's included protection. You also have the option of waiting to apply third-party protection until a null route is found to be necessary.
When dealing with companies that are above a certain size, it takes days or weeks to get to someone that can fix issues, but if you're lucky and you have a friend that knows someone who works there he can expedite your ticket. This service would work like that, a friend that puts you in touch with people hired at big corps.
I'm aware this service would have a number of potential issues, such as how to get employees on the platform without annoying their employers, or how to prevent abuse/bribes, but if somebody find a way..
What options are there to prevent this? Would a registrar such as MarkMonitor provide at least some notice or protection?
Some live stats http://ip-api.com/docs/statistics