RackNerd denied my refund, then I filed a chargeback

So I had a VPS with RackNerd for three months. Uptime was fine, but the network to my region degraded after they migrated datacenters. I opened a ticket, asked nicely, got a boilerplate "network conditions outside our control" response.

I asked for a prorated refund. Denied. Pointed to their ToS section 14.3. IMO that's pretty standard for budget hosts, but YMMV.

Here's what actually worked: I filed a chargeback through my payment processor, not for the full amount, but for the final month only. I documented everything. Timeline, traceroutes, ticket responses. Took maybe 20 minutes.

The processor sided with me. RackNerd didn't even contest it, which surprised me. Money back in 8 days.

Now I'm seeing debate about whether this hurts small hosts. Take it with a grain of salt, but I think there's a difference between a fraudulent chargeback and one with documentation. I was a customer in good standing for 90 days. The service genuinely degraded.

What do others think? Has anyone else gone this route?

Oh quinn, this very interesting case study

1. You write very clear ticket with timeline and traceroute
2. You ask prorated refund, not full amount
3. You have 90 day good standing very much
4. You document everything for processor very much

I think this not hurt small host if customer honest and prepared many host actually learn from this and improve network routing very much

But some customer abuse chargeback, that make it hard for everyone

From an SRE perspective, this is exactly why we run blameless postmortems. The host had a network degradation event. They didn't communicate root cause to the customer. Transparency would have prevented the escalation entirely.

I've been on both sides of this. At my previous gig, we treated chargebacks as signals in our error budget. If a customer felt forced into that path, we failed somewhere upstream. We published our outage notes voluntarily. Transparency, transparency, transparency.

That said, RackNerd's silence here is telling. No contest usually means they knew they couldn't defend it, or the amount was below their litigation threshold. Either way, they absorbed the cost rather than engage. That's a business decision, not a moral failing by OP.

Actually, "error budget" is not a financial metric; you mean you tracked customer satisfaction incidents against your reliability target. These are distinct concepts.

"Chawgeback" is not a word; the term is chargeback. Your l/r confusion is consistent, but this one is particularly distracting.

To the actual topic: OP's documentation discipline is admirable; most users lack this. The host's non-response suggests operational immaturity. I have no strong ethical objection.

Hej, I have experience with chargeback on Contabo. Into config of my monitoring I have all logs, hej. On server I keep ticket archive, no problem.

No, I think small host need fair chance. Malý server provider sometimes have bad month. But if they not answer ticket with real info, then customer have right to escalate. I go to payment processor only after host ignore me for two week.

Actually I win two of three case. Third one I lose because no past documentation. Lesson: keep everything on server, hej.

¡the approach of quinn is the correct one! The documentation extensive, the amount prorated only. I have seen the chargebacks fraudulent and those hurt to all. The host small deserves the opportunity to fix, but if they not fix, then the processor is there for reason!

¡I use vos with my provider in argentina and always they answer me! Maybe the cultural thing helps, no? The transparency is good but the action of customer documented is better!

¡the server red of network is not problem of customer! The refund prorated is fair, the chargeback last resource. ¡good job quinn!

I don't think we're in disagreement here. Documentation and transparency aren't competitors.

My point is that if RackNerd had published a quick status note about the routing change, quinnbizz might not have needed the paper trail at all. The chargeback becomes a last resort instead of the only resort.

That said, seven days later — did anyone from RackNerd ever show up in this thread? Their silence here is itself a data point.

32 days late to this, but

I had a similar run-in with Contabo last year. Network degradation, boilerplate response, same loop. The difference was I escalated through their community Discord first. A senior engineer DMed me within an hour, we hopped on a screen share, and he traced the routing issue to a peering change they'd made that wasn't in their status page yet.

Got my prorated credit without ever touching the chargeback button. The host fixed the peering two days later.

Not every host has that backchannel, obviously. But RackNerd's silence here is the real failure mode Quinn documented.

Has anyone actually gotten RackNerd to budge on 14.3 without going the chargeback route?

This sounds nice in theory but I've never seen a budget host volunteer root cause for a routing issue. They don't have the staff for it. You get the template and the case closes.

44 days quiet so maybe this is dead, but I'm curious if quinnbizz ever heard back from RackNerd after the chargeback landed. Some providers blacklist over that even when the amount is small and the claim is documented well.

Hey, sorry for the late follow-up — 81 days, yikes. Just wanted to close the loop since a few folks asked how it shook out.

The chargeback went through for that final month. RackNerd suspended my account immediately, which was fair — I expected that. What I didn't expect was their sales team emailing me two weeks later offering credit if I'd "reconsider the dispute." Too late, obviously.

This stuck with me. I checked their status page recently and they actually started posting routing maintenance windows. Might be coincidence, might not. Either way I ended up on GreenCloudVPS for my replacement VPS and the routing's been solid.

To anyone finding this later: document everything before you pay, not after. Makes all the difference.

Quinn