I’m not sure what happened here. It may have been a bug on our end.
The RAM limit does exist but hitting it is really, really rare. But in the last 24 hours, the limit has been triggered more times than all the times before that. So something was definitely changed on the platform and I assume that this was not intentional.
So for now, I suggest just waiting for the reactivation and see what happens after. It’s very likely that this won’t happen again, even if you don’t change anything on your site.
It would be extortion. I completely agree. Which is why we don’t do that. We don’t want users or customers that hate us.
We’re not in the business of holding your site hostage and extorting you for money. If you buy hosting from us, the only reason should be that you actually like our services and because the package is a good fit for you.
Some security products have the annoying tendency to assume that if one subdomain is bad, then all subdomains must be bad. And instead of informing the owner of the domain so they can fix it, they just block the entire domain without telling anyone.
Because even if we have a 99.9% effective abuse filter, we host hundreds of thousands of websites, so a few bad sites will evade our detection and security companies will see them before we do.
If you know your site is safe, then please report your site to Cisco as a false positive, because that’s what this is. These security companies tend to be more receptive to reports from their users/customers that a domain owner.