3 ms·
For comparison, my experience with slicehost: I lost my credit card and got a new one, so the charges from slicehost were bouncing because they had my old numb
by johnswamps 16y ago
For comparison, my experience with slicehost:
I lost my credit card and got a new one, so the charges from slicehost were bouncing because they had my old number. They sent me several e-mails about it but I wasn't checking the e-mail account they were sending it to, so this went on for about 2-3 months past due. Eventually I logged onto the e-mail account and found out about it -- I hadn't even noticed anything was wrong because they kept my VM running. I just logged on, payed the $60 or whatever it was in back payments and that was it.
(I don't know whether this is their normal policy or not, so don't use this post as an excuse to try it.)
- kanwisher 16y agoI had a similar experience with slicehost. I canceled cc and thought they would delete but they didn't and I paid it back and they kept me as a customer for years afterwords.
- mr_luc 16y agoHeh, I stopped looking at this thread almost immediately after "getting over" the initial sting. But I have to say, I still feel that this kind of behavior would be a sane policy. No one´s saying you should hold onto data forever. But having a dedicated pool of dead storage that´s capable of storing the data for a few months of non-payment, or even longer -- that seems like a very good idea. The running VMs are so many, many times more expensive than a block of dead storage of equivalent size. Probably orders of magnitude more expensive. Then when you consider the business benefit to having the softer-and-fuzzier policy ... well, there´s always the "avoid 'high maintenance' customers" theory.