What Happens When You Stop Paying for Hosting

From the team behind aidrop.it — one workspace to build, host, and keep changing your code.

A card expires, a renewal fails, or the project is simply over. What happens next is the one part of a hosting agreement almost nobody reads before they need it, and it decides whether "we stopped paying" means the site is down or the data is gone.

Every host runs three clocks: when it stops serving, when it deletes, and what comes back when you pay. They are different numbers, they apply to different things, and most pricing pages state none of them.

Find the three numbers before you rely on a host. If they are not written down, ask — and write the answer down yourself, with the date, using the worksheet at the end of this article.

Four things, and they do not go together

A project on a host is four separate things: the code, the running application, the data in managed services, and the operational knowledge — domain records, secrets, settings. Non-payment reaches them at different speeds. Code is yours and in git. The application stops first. Data is deleted last, on a clock. The knowledge is where hosts differ most, and where nobody looks.

That is the same split as asking whether you could actually leave: code leaves easily, data slowly, and the operational knowledge usually not at all. Non-payment is the involuntary version of leaving, on the host's schedule rather than yours.

Stopped should mean stopped, not removed

The right first response to a failed payment is a warning with a date, then a stop that removes nothing. A failed renewal is usually a card, not a decision, and a host that deletes on the day of the bounce has turned a billing error into an outage nobody had a chance to prevent.

A stop should look like this: the application scaled to zero, the address kept, the database untouched — stopped is not deleted, and the difference is what is still there afterwards. It should not look like a deleted service, a released domain, or a silence you discover from a customer. The warning is the part to check — a host that cannot state the lead time has not decided it.

What payment brings back

The subtle question is what a payment restores. "Everything" sounds generous and is wrong: it also starts the environments you had stopped on purpose, so a payment becomes an unrequested deployment. The right answer is exactly what non-payment stopped, and nothing else. Ask, because the answer reveals whether the host records what it did or merely flips a flag.

Ask about the clock too: paying inside the window should cancel the stop, and paying after it should cancel the deletion. Where payment restores service but the deletion date stands, you can pay and still lose the data.

The deletion clock is the one to write down

The data clock is the only irreversible one. A stop is undone by a payment; an erase is undone by nothing, and if the host keeps no backups, the export you took during the window is the only copy in existence. Four things to ask: how many days, whether there is a warning before, whether the export still works while stopped, and whether an abuse suspension runs on a shorter clock.

A managed database is the thing the clock deletes, because it is the only place durable state can live when an application container has nowhere to write. That is also why the export matters more than the grace period: the grace period buys time, the export buys the data.

The worksheet, to fill in once per host

Answer it from the terms or the documentation, link the source, and keep it with the project. Most of these have no answer on a pricing page, which is what the worksheet is for.

# Non-payment terms — <host>, checked <date> by <name>

## Stop
- [ ] Warning before anything stops?      lead time: ____   sent to: ____
- [ ] What stops?                          apps only / apps + databases / everything
- [ ] Is the address kept while stopped?   yes / no
- [ ] Can I export data while stopped?     yes / no / needs a ticket

## Delete
- [ ] Days from stop to deletion:          ____
- [ ] Warning before deletion?             yes, on day __ / no
- [ ] What is deleted?                     databases / files / code / DNS records / secrets
- [ ] Backups I could ask for?             yes / no  → if no, my export is the only copy

## Return
- [ ] Payment restores:                    exactly what was stopped / everything / nothing automatic
- [ ] Payment cancels the deletion clock?  yes / no
- [ ] Abuse suspension on its own clock?   yes: ____ / no

Source: <link to the terms or the page that states this>

An unanswered line is a finding. It means the host has not said, and "has not said" is the answer to plan around.

FAQ

What happens if I don't pay my hosting bill? It depends on the host, which is the problem. The good pattern is a warning with a date, a stop that removes nothing, and a separate, longer clock before any data is deleted. The bad pattern is deletion on the day of the failed payment.

Does a host delete my data if I stop paying? Eventually, usually. The questions are how many days after the stop, whether you are warned first, and whether an export works during the window. A host that keeps no backups will say deletion is final, and it means it.

Will paying again restart my site? It should restart exactly what non-payment stopped — not every environment you own, some of which you may have stopped deliberately. Ask whether a late payment also cancels the deletion clock, because those are two separate outcomes.

Can I get my data back after hosting is suspended? While it is suspended and inside the deletion window, an export should work and is the thing to do first. After deletion, only if the host keeps backups, and many do not.

What is the timeline on aidrop.it? A warning to every admin three days before applications stop; the stop removes nothing and the address stays. Paying restores exactly what was stopped. Databases, caches and queues are kept for sixty days after hosting lapses, with a warning on day fifty, then deleted — there are no backups, so the on-demand export is the copy. Code and project knowledge are never deleted by billing. An abuse suspension is a separate clock: thirty days, and paying does not lift it.

Cover: https://commons.wikimedia.org/wiki/File:Expired_Parking_Meter.jpg by MarkBuckawicki, CC0, via Wikimedia Commons. Cropped to 16:9 within the original frame. Alt text: A parking meter showing a red EXPIRED flag, with a parked car behind it.