Vultr refunded me for "too much" uptime

I must share a strange Incident with my Vultr Virtual Server. In January my Invoice showed a Credit of 4.87 US-Dollars with Description "SLA Uptime Exceeded."

This puzzled me greatly. I opened a Ticket and asked for Clarification. The Support Agent (name was "Jordan") stated that my Server had achieved 99.997 Percent Uptime in December, which triggered their "Inverted Service level agreement Clause." I asked for the Contract Text.

Jordan provided the relevant Section. It states that if Uptime EXCEEDS 99.99 Percent, the Customer receives a Credit proportional to the "excess Availability." This is apparently a Loyalty program Feature from an older Promotional Period.

I have now received three such Credits. The Clause seems to still be active for grandfathered Accounts. I do not know if this is intentional or a BillingError.

Please to a

Pro tip: this is almost certainly a legacy clause that survived a billing system migration. I've seen this with Oracle free tier quirks where old promotional language gets grandfathered into new accounts.

Here's how to verify:

• Check your original signup date and promo code used
• Compare your current plan name against their public plan list
• Look for "loyalty rewards" or "uptime bonus" in archived ToS versions

Heads up: if you report it, they will likely remove the clause silently and not back-credit you for honesty. If you stay quiet, it could persist for months or years, or they could claw it back later.

The real question is whether the math even benefits you long-term. 4.87 on a cheap VPS suggests the credit formula is trivial, not proportional to actual plan cost.

• 4.87 credit
• Unknown clawback risk
• Moral weight of knowing

I would check if the credit auto-applies or needs manual invoice review. If it is automated, it is probably buried deep enough that nobody at Vultr knows it exists. If a human approves each one, your clock is ticking.

My auction server with 24TB raw had a similar thing with a datacenter that forgot to bill cross-connect fees for 14 months. They eventually noticed and demanded full back payment. We negotiated to 3 months.

Credits are nice. Silence is safer. Documentation is essential.

This is a fascinating inversion of the usual SLA story. Most providers write SLAs as one-way valves: they pay you for downtime, never the reverse. Vultr either had a very optimistic marketing team in 2019, or someone inverted a comparison operator in their billing code. I would not call it exploitation to accept credits that their own system generates automatically. You did not manipulate anything. You simply exist with stable uptime, which is the expected state of a server. I would set aside the credit amounts in case of clawback. Treat it as a pleasant surprise, not budgeted income.

Okay so heres the thing I did this exact thing with InterServer in 2024 they had a weird bandwidth thing where if you used under ten percent of your allocation they gave you a rollover credit I never told them I just let it ride for eight months then one day poof gone no explanation no email just the credits vanished from my account I hadnt even spent them they were just theoretical numbers on a screen anyway my point is these weird billing artifacts are like finding money on the street yes its yours if you pick it up but the person who dropped it might come back and the question is do you want to be standing there holding it when they do or do you want to have already spent it on coffee and not care I spent mine on a new nvme drive no regrets but also no illusions that I wasnt living on borrowed time with that whole situation

Thanks for raising this, Hans-Dieter — it's a genuinely unusual case.

A few quick checks I'd recommend:

• Does the credit appear on your invoice as a line item with a specific code?
• Is there any mention in your original service agreement or welcome email?
• Has Vultr's billing team ever reached out proactively about it?

From a customer-success perspective, grandfathered clauses do sometimes persist in billing systems long after marketing retires the campaign. If you'd like, I can check whether Contabo has ever encountered similar legacy behavior (we have not, but I am curious).

In the meantime, I'd suggest downloading all invoices with the credit applied, in case of future account review.

— Jane @ Contabo

Why pay for Vultr's billing mysteries when you can self-host it and know exactly where every penny goes

Seriously though this is why I run my own invoice system with docker compose and a reverse proxy in front of grocy or actualbudget. You own the data, you own the logic, no inverted clauses no surprise credits no clawback risk

I get it, not everyone wants to be their own sysadmin. But this thread is literally about a provider's opaque billing artifact that even their support barely understands. That is the core problem with any hosted service: you are renting mystery meat infrastructure with mystery meat accounting

If you do stick with Vultr, at minimum export your billing history monthly. I have a simple cron job that hits their API and dumps to csv. Same principle as backups: trust but verify, and preferably dont trust

https://www.vultr.com/pricing/

Following this thread closely. I have three Vultr instances in Singapore and never seen anything like this.

I have now received the January Invoice with another Credit, this time 5.12 US-Dollars. Same Description "SLA Uptime Exceeded." I have archived all Invoices and ToS Versions from my Signup in 2021. The Clause is real and still active. I will not report it further.

This is wild. I've peered with Vultr in New Jersey and Frankfurt for years. Their network is solid but their billing system has always been a black box. If this is automated and tied to actual uptime metrics from their monitoring, it could be running on a cron job that nobody owns anymore.

Question: does the credit scale with your plan cost, or is it a flat calculation? If it's proportional to your monthly spend, a 5 dollar VM gets pennies while a bare metal box could be getting real money.