ServerBudget

Cheap VPS Refunds and SLA Terms: What You Can Actually Claim Back

By Marcus Reid · Published Nov 11, 2026 · Last updated Nov 11, 2026

Short answer: A 30-day refund window exists on the one vendor in this comparison whose policy pages could be retrieved, but it is not the unconditional promise the plan page implies. Its own terms exclude a long list of items from refunds, require an identity check before any refund is processed, and attach five separate cancellation charges to the deal. No uptime percentage, no service-credit schedule and no claim procedure appears anywhere in the retrieved terms - the words do not occur in that document at all. A second vendor in the comparison returned HTTP 403 Managed Challenge on all seven policy and pricing paths tried, so its advertised uptime figure could not be re-verified and is not used here. The third is a review roundup and publishes no policy of its own. Practically: you can claim a refund inside 30 days if you cancel in time, in writing, before add-ons and domain fees enter the picture; you cannot claim an SLA credit from any document readable today.

Clause, in plain wordsWhat the pages actually sayThe trap
Refund window30 days from activation, on the homepage, the plan page, the terms and the acceptable-use policyThe plan page calls it unconditional; the two legal pages list what is excluded
What is excludedDedicated addresses, licenses, upgrades, renewals, assisted support, add-ons, domain fees, operating systemsMost of what people buy alongside a cheap plan sits in this list
How to claimPass a verification procedure, then file under Billing Issues at least 3 working days before renewalRefund processing is gated behind verification; a late ticket meets auto-renewal
Uptime guaranteeNothing published in the retrievable terms; the second vendor's SLA page was unreachableNo number, no measurement window, no credit, no claim deadline to invoke
Cancellation charges$15, $13 per domain, $15 per domain transfer, $200 in two distinct clausesA "free" backup copy or domain becomes a bill when you leave early

That table is the answer. Everything below is the evidence for each row, including where the sources contradict each other.

1. Which of the three pages can be checked at all

The comparison set for this keyword is one review roundup and two vendors. On 2026-11-11, under two user agents, the retrieval results were uneven, and that unevenness is itself a finding.

SourceKindPolicy pages retrievableWhat can be stated
vps.usVendor4 of 4 tried (homepage, plan page, terms, acceptable-use policy)Refund terms, exclusions, fees and cancellation mechanics
liquidweb.comVendor0 of 7 triedNothing. All seven pricing, product, terms and SLA paths returned HTTP 403
bitcatcha.comReview roundupNot applicableNo refund or SLA policy is published by a roundup; the 2026-11-10 worksheet records none

A three-way clause comparison is therefore impossible from primary sources today. Writing one would require inventing two of the three columns. This article compares the four pages that did load, plus public discussion of what happens when buyers try to use such policies.

2. The 30-day window, and the exclusions printed next to it

Four pages agree that a refund is available if the account is cancelled within the initial 30 days after the service became active. After that point, no refund is given. That is the consensus, and it is narrow: the clock starts at activation, not at first login, and the trigger is cancellation, not dissatisfaction.

The two legal pages then remove items from the refundable amount. One lists dedicated addresses, operating systems, control-panel and installer licenses, upgrades, renewals, assisted support, extra memory, traffic and disk, and domain registration or renewal fees. The other lists dedicated addresses, extra disk, extra memory, extra traffic, control panels, script installers and domain fees. The overlap is large; the wording is not identical. Neither page states a formula for computing a partial refund, so the size of a refund on a mixed invoice is not derivable from the published text.

The plan page takes a different tone. It presents the 30-day guarantee as risk-free and free of conditions. A reader who stops there has not seen the exclusions. That gap between a marketing page and the two legal pages is the single most useful fact in this comparison, and it is not a matter of interpretation: the same vendor publishes both.

3. Five charges that sit outside the refund

Cancellation inside 30 days is not automatically free even when the base plan is refundable. The following figures are transcribed from the two legal pages read on 2026-11-11.

ChargeAmountCondition stated on the page
Free backup copy$15 one-off, or the service price if lowerTermination request within 30 days of first payment where a complimentary backup copy had been supplied
Free domain kept by customer$13.00 per domainCancellation within 30 days when a complimentary domain was registered and the customer does not continue the transfer
Free domain transferred out$15 per transfer per domainCancellation with a request to move the complimentary domain to another registrar
Domain redemption$200.00Renewal requested during the redemption period, more than 29 days after expiry
Improper chargeback$200.00A chargeback judged improper; the fee is added and the account is terminated

The two $200 figures are different clauses on different pages, covering different events. They are not a duplicate, and neither is an uptime credit. The $13 and $15 domain figures are similarly two differently conditioned scenarios rather than a single price quoted two ways. Where the pages disagree in wording, both readings are kept rather than reconciled.

Note what is missing: no arithmetic tells a customer what happens when a $10 plan is bundled with a separately licensed control panel, a complimentary domain and a complimentary backup copy. The exclusions are listed, the charges are listed, but the net refund is not computed anywhere.

4. The order of operations for a claim

The terms describe a sequence, not a button. Full account access is conditional on passing a verification procedure. Account management, suspension, termination and refunds are all stated to be available only after that check succeeds. Separately, termination by the customer requires a ticket under Billing Issues with at least 3 working days of notice before the renewal date; after the initial period, the agreement renews automatically for successive terms of equal length. A price change is notified 10 calendar days in advance by email.

Read together, those clauses mean the practical deadline is earlier than day 30. A buyer who cancels on day 29 of the first term has already passed the renewal notice window in some term lengths, and a buyer who has not completed verification cannot process a refund at all. There is also a clause allowing termination after an account has been suspended for more than 14 calendar days, with data permanently deleted and no refund due. Violations of the terms or the acceptable-use policy are likewise stated to remove refund eligibility, and the terms reserve to the vendor the judgement of what counts as a violation.

None of that is hidden in the sense of being unwritten. It is written in three separate documents, in different sections, with no single page joining them. Joining them is the work this article does.

5. Why there is no SLA row in the answer table

A usable service-level agreement needs at least five things: a defined uptime percentage, a measurement window, a credit schedule tied to the shortfall, a deadline and method for claiming, and a list of exclusions. The retrieved terms and acceptable-use policy contain none of them. Searches of the retrieved terms text for an uptime figure, an uptime word or an SLA abbreviation return zero occurrences.

The second vendor is recorded in a local 2026-11-10 worksheet as advertising 99.99% uptime. On 2026-11-11 that figure could not be checked: seven paths including the SLA and terms pages returned HTTP 403 Managed Challenge under both a plain client and a browser user agent. A number that cannot be re-read is not used as a number here. It is reported only as an unretrieved local record.

So the honest SLA answer is negative and specific: no credit mechanism is available from the pages that loaded, and the page that might have contained one was unreachable. Readers should treat any uptime percentage repeated in a roundup as unverified until the policy page itself opens.

Once you have checked refund and SLA fine print, the first-term vs renewal price page puts each provider checked renewal figure next to its promo figure.

While this page deals with refund and SLA fine print, the Vultr pricing page shows how a Vultr instance is billed when it is stopped.

6. What real buyers report when billing goes wrong

Policy text describes the intended path. Public discussion describes the path people actually walked. The following are comments retrieved through a public comment search index, each linked to its thread with author and date. All are self-reported anecdotes, not measurements, and none is a statement by any of the three compared sites.

On duplicate charges, a 2010 thread about a $5 host has a commenter writing, "I had double billing problems with serverpronto." Another reply in the same thread asks, "How can they afford to offer that at $5? It is a scam?" [HN1][HN2]

On conditions that are hard to find, a different 2010 discussion has a commenter thanking another for pointing out a detail that "wasn't mentioned anywhere" - the same failure mode this article found in the gap between a plan page and two legal pages. [HN3] That discussion also turns on availability rather than refunds: another participant explains that a provider "is based on availability. there are times when they have no space, so they dont allow you to order." [HN4]

On the difference between a snapshot and a recoverable copy, a 2016 thread about backup on a cheap VPS has a commenter asking, "What exactly would you call backup? Snapshots and copy of those snapshots which are often offered are not true backup solutions." [HN5] A 2021 storage thread adds the shorter version: "I personally know two people that lost all data with Contabo, so be careful." and, from another participant, a reminder that "one should never forget that RAID is not the same thing as backup". [HN6][HN7]

The consensus across these comments is not that any vendor broke a contract. It is that billing disputes, stock shortages and unclear backup semantics are the three things buyers actually argue about, while the policy pages spend their words on exclusion lists and verification. That mismatch is a disagreement between what is documented and what is experienced, and it is visible only when both kinds of source are read together.

7. Where the sources agree, and where they split

Agreement: four pages from one vendor name the same 30-day window; two of those pages name the same broad classes of non-refundable items; both legal pages attach fees to complimentary domains cancelled early.

Disagreement: the plan page frames the window as free of conditions, while the legal pages enumerate conditions. The two legal pages use different exclusion wording and price two different domain-cancellation scenarios at $13 and $15. The terms mention a $200 domain redemption fee; the acceptable-use policy mentions a $200 chargeback fee. A local worksheet from the previous day attributes an uptime percentage to a vendor whose pages did not load today.

Unresolved: no partial-refund formula, no SLA credit schedule, no claim deadline for downtime, and no second or third vendor policy readable at the time of writing. Those are gaps in the published record, not gaps in the research.

8. What a buyer can actually rely on

Assume the base plan is the only refundable line. Assume every add-on, license, assisted-support item and complimentary domain is excluded until a page says otherwise in writing. Complete verification early, because it gates the refund rather than following it. File the cancellation under the billing category with a margin wider than three working days before renewal. Keep your own backup off the machine: the terms describe backups as a server-restoration measure with no integrity guarantee, and the community threads describe why that is not the same as a copy you can restore yourself. Finally, do not budget for an uptime credit. On the documents readable today, there is no mechanism to credit one.

If a vendor does publish a full SLA, the five fields in section 5 are the checklist to hold it against. Their absence is a finding, and an honest one.

Frequently Asked Questions

Can I get a full refund on a cheap VPS within 30 days?

Only on the base service, and only if the cancellation is filed in time and verification has been completed. The retrievable terms exclude dedicated addresses, licenses, upgrades, renewals, assisted support, add-ons and domain fees, and attach $15, $13 per domain and $15 per domain transfer charges to some early cancellations. No partial-refund formula is published, so a full refund on a mixed invoice cannot be assumed.

Is there a free trial, or only a refund window?

The pages read describe a 30-day refund window, not a trial in which no payment is taken. A payment is made, the service is activated, and a cancellation inside the window may be refunded subject to the exclusions. No zero-cost trial period with published terms was found on the pages retrieved for this article.

What happens if the VPS goes down - do I get a credit?

Nothing in the retrievable terms provides one. No uptime percentage, measurement window, credit schedule or claim procedure appears in the terms or the acceptable-use policy, and the other vendor's SLA page returned HTTP 403 on every attempt. Treat any uptime figure quoted elsewhere as unverified until the policy page itself can be opened.

Sources

All pages read on 2026-11-11 unless noted.

No sentence from the three compared sites is reproduced here; only published figures, clause content paraphrased into plain words, and feature labels are used. Community comments are quoted verbatim with attribution and are self-reported anecdotes. No sentence here is derived from a machine-generated transcript. No benchmark, traffic estimate, search-volume estimate, analytics figure or ranking judgement appears in this article, and the two data sources reserved for the 28-day report were not read.

Marcus Reid
Systems Architect & VPS Infrastructure Analyst

Marcus has been working with virtualized server infrastructure since 2015, deploying and benchmarking VPS and cloud instances across DigitalOcean, Vultr, Hetzner, OVHcloud, Contabo, RackNerd, Hostinger, and the major hyperscalers. His work focuses on the gap between what providers advertise and what actually happens when you deploy a real workload. He verifies every price and specification against official provider pages before publication.