What happens if a renewal isn't paid
The dates from a server's renewal invoice to its deletion: reminders, suspension 3 days after the due date, and deletion of the server 21 days after.
Each server is paid a month or a year at a time. Its renewal invoice covers the next period, with the plan and each add-on on its own line. It's due on the day the paid period ends, which the server's page in the panel shows as paid until. If the invoice isn't paid, this is what happens, counted from that due date. The dates are the same for a yearly server.
| When | What happens |
|---|---|
| 7 days before | The renewal invoice is issued, and we email it to you, with its lines, the credit it used and the minute it's due. Any account credit pays it first. Nothing is charged to a card unless you turned on automatic payments. |
| 3 days before | A reminder email. With automatic payments on and a card that will work, there's no reminder: the card is charged on the due date. |
| On the due date | An email saying it's due today, at what time. The server keeps running. With automatic payments, the email about the charge (a receipt, or what to do if it didn't go through) comes instead. |
| 3 days after | The server is suspended: we stop it, and email you to say so. |
| 18 days after | A final warning email, with the date and time (UTC) the server will be deleted. |
| 21 days after | The server and its disk are deleted, and its IP addresses are released. |
The emails go to the address on your account (on a team, also to billing members who turned billing emails on, and to the account's billing contact address once it's confirmed). Every one of them links to the invoice and gives the exact due, suspension and deletion times, to the minute, in UTC. If several of your servers reach the same step at the same time (servers ordered together renew together), the invoice, reminder, due-today, suspension and final warning emails come as one email covering all of them, with each server's invoice and times listed on its own. A yearly server also gets a heads-up 30 days before its renewal; a monthly one doesn't, but every renewal invoice and receipt says when the next invoice comes and how to cancel before it. Servers that were already overdue on 7 November 2026, when we moved deletion from 14 to 21 days, follow the 21-day dates too: none is deleted sooner than its emails said.
The renewal is for the same price as the server's last period: a server keeps the price it was ordered at (Terms of Service).
Paying
Unless you turned on automatic payments with a card, nothing is taken from a card or a wallet unless you pay. With automatic payments on, your saved card is charged on the due date, and if that charge fails we try again a day and two days later, before the suspension date, and email you; the dates below still apply if it can't be charged. Open the invoice from the email, or from Billing in the panel, and choose pay with card, pay with Bitcoin or pay with USDT (TRC-20). A card payment for a renewal isn't held for checking, so it pays the invoice as soon as Stripe accepts it. Payment methods walks through each checkout. Any account credit has already been taken off the invoice, so you only pay what's left.
The billing overview lists every server's next renewal and whether it is an estimate, invoiced or paid, so you can see one coming:

To stop this ever happening, keep enough credit on the account: add funds and every renewal is paid by itself the moment its invoice is issued.
Check it worked
The invoice shows paid, and the server's paid until date on its Settings tab moves on by a month (or a year). The receipt email says the new paid-until date. If the server is suspended, it starts again as soon as the payment confirms, and the receipt says so. Nothing on the disk is touched while it's suspended; you just can't start it or take snapshots until the invoice is paid.
A Bitcoin payment can take a while to confirm; a card payment for a renewal is charged straight away. While a payment for the full amount is waiting for confirmation, we hold back the suspension or the deletion, for up to 72 hours. It's a safety margin for slow confirmations, not extra time, so pay well before day 21.
After the deletion
A deleted server can't be brought back, by you or by us. Its snapshots go with it, because they're stored on the same disk. If you think a deletion was a mistake, reply to the email that told you about it. If a payment arrives after that, it becomes account credit, which pays any other invoice you have open, then your next ones.
If a suspended server's data is all you need, or you need a little more time to pay, reply to the suspension email: we'll work something out with you.
If you'd rather not have the server any more, there's no need to let it lapse. Cancel it instead. Then nobody chases the renewal, and the server is deleted when its paid period ends.
A renewal issued late, or an outage on our side
If we issue a renewal invoice late, for example after an outage on our side, it's due no sooner than 3 days after we issue it. Every date in the table counts from that later due date, so a late invoice never shortens your time to pay. The reminder comes at least a day after the invoice, never with it.
If our side was down when one of these emails was due, the dates can move later, never earlier:
- An email that's due goes out when we're back, a day after the last one at the earliest. You only get the newest one, not a pile of old ones.
- If the server is past its suspension date by then, it's suspended straight away, and we email you to say so.
- A server is never deleted until at least 2 days after its final warning email. If we're back after day 18, the final warning goes out first, and the deletion date it gives is the real one.