4 ms·
This is why my old hosting company changed its auto disconnection code to work at 11am on a Monday morning, never at a weekend. That way it's the bill-payers t
by mattbee 4y ago
This is why my old hosting company changed its auto disconnection code to work at 11am on a Monday morning, never at a weekend.
That way it's the bill-payers that notice and get in touch, not the poor tech on the out-of-hours rota.
Also, it only firewalled the customer's public IPs from the Internet - it didn't stop servers. That way when the account is settled there was often nothing for the techs to do.
Also it was only ever done after the bank reconciliation was marked as complete, just in case...
We relied on goodwill and recommendation of engineers for our growth, so were keen not to make their lives harder for someone else's bureaucratic (or cynical) mistake.
- czbond 4y agoThe method you describe seems like the proper way to achieve this thorny issue.
- designium 4y agoWhich hosting company are you referring to?
- softawre 4y agoFrom his profile: > Cofounder and former MD of Bytemark, a British hosting company.
- kyriakos 4y agoThat's how hetzner handles late payments and only does this after 2 warning emails.
- Gibbon1 4y agoIn the normal BnB world anyone with a account gets a phone call before they get cut off.
- bingo-bongo 4y agoThat may be true for billing, but Hetzner killed all access to my dedicated server on a weekday afternoon and when I reached out to them within 30 min, the response was “it was done by the networking department, I can’t do anything about it, but they’ll look into it tomorrow..” .. :| wtf?! not okay Hetzner! (My “mistake” was a interface mis-configuration, nothing abusive or otherwise problematic)