Knowledge base
What happens when a renewal is not paid, what you must pay to get your services back, and when data is permanently deleted.
When a renewal payment fails we retry it and email you. Your sites keep working for seven days. If it is still unpaid after that, your hosting is suspended: your sites stop serving, but nothing is deleted.
Cloud servers and managed databases are paused straight away. We pay for those by the hour, so they have no grace period — they are stopped when the renewal fails and started again when it is paid.
Only Billing is open. You can see what is owed, pay it, add a payment method and top up your balance, but tools, backup downloads, site moves and the API are unavailable until the account is back in good standing. Everything opens again as soon as the payment goes through — you do not need to sign out or contact us.
Your services come back only when every missed billing period and the current one are paid. For example, if a monthly plan went unpaid 50 days ago, two periods are owed: the month you missed and the month you are in. Paying the first one does not restore the service on its own; the next renewal appears straight away, and your services resume when it is paid.
This is the same whichever way you pay — card, PayPal, crypto, bank transfer or account credit. Billing shows how many periods are owed.
Once nothing is owed you can pay for several months at once from Billing → Pay for several months at once: choose how many months, and we create one invoice for exactly that amount. It is useful if you pay by crypto or bank transfer.
If a subscription is cancelled, or stays unpaid, its sites, databases and backups are permanently deleted 60 days after the service ended. We email you 14 days and 3 days before, and never delete anything sooner than 14 days after the first warning. Paying what is owed before that date keeps everything.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →