RackNerd denied my refund, then I filed a chargeback

146 days, wow this thread still very wewevant I think

Sofialund, you mention the cultural thing with vos I think that is intewesting point maybe the fowmality of ticket system hide the human connection some host wespond better to chat or phone, not just ticket queue

Srelet, the blameless postmowtem is nice in theory but how many budget host actually do this I cuwious if anyone has seen RackNerd ow simiwaw publish outage notes vowuntawily that would be nice signal of matuwity

I still think quinn's approach is gold standawd pwepawed, honest, pwoportionate the thwee P's

But this thread stuck with me.

I keep thinking about that line. I had basically the same thing with Vultr last year — routing issues, shrugged off, no RCA shared, status page at https://status.vultr.com never even acknowledged it. I didn't chargeback, just migrated out and ate the cost. Sometimes I wonder if that was the wrong move, letting them off without signal. Has anyone actually seen a budget host change their transparency practices after a documented chargeback? Or do they just blacklist the card and move on?

202 days, guess this thread died but the problem didn't.

That's the part that still bugs me. RackNerd had the traceroute data, they knew the migration timeline, and they still went with the boilerplate. I've seen the same pattern with two other budget hosts. It's not the network degradation that triggers the chargeback, it's the stonewall.

Has anyone here actually gotten a proactive refund offer from a host after a routing change? Without escalating at all?

¡ah, this thread has been quiet for long time! I come back to add something I learned since then.

This is true in theory, but I want to say: the transparency needs to be *offered*, not hunted. The customer should not need to open three tickets to learn "we migrated datacenters and routing changed." That information belongs in status page or at least first reply.

I still think quinn did everything right. Documented, prorated, patient. But the host made them work too hard for basic information. That is the real failure.

¡the small hosts can learn from this without needing big SRE team! Just tell the customer what happened, when, and why. Saves everyone time and money.

Has anyone else here had better luck with proactive communication from budget providers? Or is this still rare in 2026?