> This looks like the author chose a very bad hosting plan. For example, Hetzner simply lowers your connection speed if you get above the limit, and you only pa

> This looks like the author chose a very bad hosting plan. For example, Hetzner simply lowers your connection speed if you get above the limit, and you only pay for additional traffic (and speed) if you really want to. Most other providers handle the situation in a similar way. As mentioned elsewhere in the text, the core problem was that everything was hosted on the main domain (and IP). Hetzner at least only allows throttling per IP, which would have crippled the whole server. With everything tied together like that, there's little wiggle room. Takeaway here, use distinct (sub-)domains for every project/product/whatever to prepare for cases like this. > This seems to be very short period for closing down a service. Of course, there were no paying customers, so they got more than they paid for. Especially as setting up your own Telize instance seems to take about 15 minutes including OS installation. > However, some trouble could have been avoided by a longer closing period. In particular, it is much easier to get rid of annoying after-period users if you are able to deny their requests with a simple "You had 3 months to prepare for the shutdown!" Users dense enough to make their products break on a 404 are rarely troubled by reason. Or deadlines. I doubt they'd have been deterred by a six months period – embedded code like that is a one-off affair and nobody checks on it until it breaks.