What happens if a server invoice is overdue? The stop, cancel and deletion timeline
If a server invoice is not paid by its due date, the service is first suspended, then canceled and finally enters the deletion process on a set timeline. This guide explains what happens on which day under our current automation settings, how to bring a suspended server back and how to protect your data.
When is the renewal invoice created?
The renewal invoice for your VDS and VPS services is created 7 days before the due date and appears in your client area. Reminder emails are sent as the due date approaches. You can pay the invoice by card (via iyzico), bank transfer (EFT) or with your account balance. Prices do not include 20% VAT.
We recommend not leaving the payment until the due date. An unexpected problem such as a declined card or a delayed bank transfer can easily push a last-minute payment past the due date. Paying on the day the invoice is issued, or within a few days, leaves you time to sort things out.
The timeline after the due date
Under our current automation settings, the following steps apply to an unpaid server invoice. Days are counted from the invoice due date.
| When | What happens? | Effect on your server | What should you do? |
|---|---|---|---|
| 7 days before the due date | The renewal invoice is created; reminder emails are sent before the due date. | The server runs normally. | Pay the invoice before the due date. |
| Due date | The last day to pay the invoice. | The server keeps running. | Complete the payment today at the latest. |
| Day 2 after the due date | The service is suspended and the server is shut down. | The virtual machine is off; websites, email and applications are unreachable. | Pay the invoice; the service is reactivated. |
| Day 7 after the due date | The service is canceled. | The server is off and the service has ended. | Contact our support team without delay. |
| Day 14 after the due date | The server is placed in the deletion queue; deletion is carried out with our team's approval. | Data from a deleted server is not guaranteed to be recoverable. | Have your data off the server well before this date. |
Because the automation runs during business hours (09:00–18:00), the time at which these steps happen can shift within the day. You cannot know in advance at what time on day 2 the suspension will take place, so do not leave the payment until the last moment.
This timeline describes our current automation settings for information purposes, and those settings may be updated over time. Our service relationship is governed by the Distance Sales and Service Agreement and the Cancellation and Refund Policy; refer to these documents for the contractual basis of these periods.
What happens to a suspended server?
Suspension means your server is shut down. Because the virtual machine is not running, everything you host on it becomes unreachable at the same time:
- Websites and APIs stop responding; visitors see a timeout or a connection error.
- A mail service running on the server cannot receive mail. Sending servers retry for a while; if the outage lasts too long, the messages bounce back to the sender.
- Scheduled tasks (cron), backup scripts, queue workers and monitoring agents do not run; any backups the server takes itself are skipped for that period.
- SSH, RDP and remote database connections cannot be established.
Suspension alone does not delete data; the server is only shut down. As time passes, however, the service is canceled and the server enters the deletion queue. Even a short outage can cost you visitors and orders, and search engines may also view sites that stay unresponsive for long periods unfavorably.
Bringing a suspended server back
If you pay while the service is suspended, the service is reactivated. Follow these steps:
- Sign in to your client area and open the unpaid invoice.
- Pay the invoice by card (via iyzico), bank transfer (EFT) or with your account balance.
- When the service is reactivated, the server is powered on automatically. Check its status on the service page after a few minutes; if it still shows as off, turn it on with Start Server.
- After the server is up, use the commands below to confirm that your services started properly.
- If the problem persists, open a support ticket and include the service and invoice details. Never share passwords, card details or one-time codes.
Since the server has been off for a while, a few checks after it boots are a good idea. Failed services, time synchronization and boot errors are the first places to look:
# Services that failed to start
systemctl --failed
# Status of the web and database services (replace with your own services)
systemctl status nginx mariadb --no-pager
# Clock and time synchronization
timedatectl
# Error-level log entries from the current boot
journalctl -b -p err --no-pager | tail -n 30After an unexpected shutdown, a database server may run recovery steps when it starts, so the service can take a little longer to become ready. For the effects of the different shutdown types, see the power actions guide.
A late payment does not move the due date
A late payment does not shift the next due date to the day you paid. For example, if a service is due on the 22nd and you pay the invoice on the 24th, the next due date is still the 22nd. The days the server was off still count toward the period you paid for, so paying on time avoids both the outage and the lost days.
Tips to avoid disruptions
- Consider annual billing. With annual billing, 12 months of service cost the same as 10 months, and you pay only one renewal invoice a year. Annual purchases also come with a 30-day money-back guarantee from activation. For a comparison, see the monthly and annual pricing guide.
- Use your account balance. If you keep a balance on your account, you can pay quickly from it when the invoice is issued. Do not assume the balance settles the invoice on its own; check the invoice status in the panel.
- Keep invoice emails out of spam. Add emails from Hostimor to your safe senders list and check your spam folder regularly. Your invoices also appear in your client area, independently of email.
- Keep your contact details up to date. Make sure the email address and phone number in the client area are current. Using a shared address such as accounting@ instead of one employee's personal address keeps notifications from getting lost when staff change.
- Add due dates to your calendar. If you have several servers, keep their due dates in your team's shared calendar and name the person responsible for payment.
If you want to leave the service
If you no longer need the server, end the service in a planned way instead of leaving the invoice unpaid and waiting for the timeline to run its course. That way your data is not deleted outside your control.
- Move your data off the server: web files, database dumps, configuration files, scheduled tasks, SSL certificates and application keys.
- Check that the archive opens and that the database dump is complete.
- Point your domain's DNS records and email settings to your new server and wait for the change to propagate. See the DNS propagation and TTL page for timings.
- Submit your cancellation request from the client area.
Run the commands below on your own computer or on your new server to pull the data from the old server. The examples assume you connect as root; on Windows servers, transfer files over a Remote Desktop connection or with your own backup tool. For a regular backup routine that is independent of the server, see our guide to off-site backups with restic.
# Run on your own computer or on your new server
mkdir -p ~/server-archive
# Web files and system configuration
rsync -avz root@203.0.113.10:/var/www/ ~/server-archive/www/
rsync -avz root@203.0.113.10:/etc/ ~/server-archive/etc/
# Consistent dump of all databases (use mysqldump if you run MySQL)
ssh root@203.0.113.10 "mariadb-dump --single-transaction --routines --triggers --all-databases | gzip" > ~/server-archive/databases.sql.gz
# Scheduled tasks of the root user
ssh root@203.0.113.10 "crontab -l" > ~/server-archive/root-crontab.txt
# Verify the archive
gzip -t ~/server-archive/databases.sql.gz && ls -lh ~/server-archiveFor annual purchases, you can request a refund within 30 days of activation; the details are in the Cancellation and Refund Policy.
Data from a deleted server is not guaranteed to be recoverable. Snapshots live in the same place as the server and are removed together with it, so always keep your backups off the server. For details, see the Backup and Data Retention Policy.
Frequently asked questions
Is the data on a suspended server deleted?
Suspension shuts the server down; it does not delete data. Under our current automation settings, however, the service is canceled on day 7 after the due date and the server is placed in the deletion queue on day 14. The safest way to protect your data is to pay the invoice on time and keep an up-to-date backup off the server.
I have paid. When will my server come back on?
After a payment made during suspension, the service is reactivated and the server is powered on automatically. If the server still shows as off on the service page after a few minutes, turn it on with Start Server. If the problem persists, open a support ticket with the invoice and service details.
Can a canceled service be restored?
For a service canceled on day 7 after the due date, contact our support team without delay to find out what can be done. You can reach us through a support ticket, by email at destek@hostimor.com or via live chat on our website. Data from a server that has been placed in the deletion queue or deleted is not guaranteed to be recoverable.
Related articles
Thanks for your feedback!