How Users Forced Hostinger to Honor a Refund After a Billing “Glitch” That Charged Them Despite Auto-Renew Off

In early 2024, a significant number of Hostinger customers found themselves billed for web hosting services they had explicitly opted out of renewing. What began as isolated complaints quickly turned into a vocal movement across forums, social media platforms, and support channels, calling attention to an apparent billing “glitch” that caused accounts to renew automatically—despite the auto-renew setting being disabled. Users felt betrayed, and their collective pressure ultimately compelled the company to acknowledge the issue and issue refunds.

TLDR: A billing error at Hostinger led to customers being charged for services even after disabling auto-renew. After being met with silence and standard responses from support, affected users banded together across Reddit and X (formerly Twitter), forcing Hostinger to admit the mistake. Refunds were eventually issued, but the incident raised concerns over billing transparency and consumer rights. The situation serves as a wake-up call for scrutinizing tech billing practices.

The Billing “Glitch” That Sparked Outrage

The issue began quietly—with just a few users noticing unexplained charges on their payment methods around January 2024. Upon logging into their Hostinger accounts, they were surprised to find their services extended for another year even though they had disabled auto-renewal well before the expiration date. Most assumed it was a one-off incident but were stunned when Hostinger’s customer support told them the charges were “valid” and could not be refunded.

Reddit threads, particularly in subreddits like r/webhosting and r/techsupport, began to light up with similar complaints. Some users had screenshots or email confirmations showing that auto-renew was turned off, but they were still being charged. This gave rise to the growing belief that either a technical glitch occurred or Hostinger was willfully ignoring user settings.

Standard Support Scripts and Growing Frustration

Many customers took their cases to Hostinger’s chat and email support, only to receive generic responses. Reps insisted that auto-renewals were customer responsibility and often blamed the users for “not disabling auto-renew properly.” A few offered service credits instead of a refund, which only added to customer dissatisfaction.

Despite their frustration, users did not give up. Several began organizing collaborative efforts to document their cases, share how Hostinger was responding, and explore avenues for consumer protection. Some even contacted their banks or PayPal accounts to initiate chargebacks, with mixed success depending on the timeframe of the transaction.

Social Media as the Catalyst

Indeed, what shifted the narrative in users’ favor was how swiftly it spread on social media. Hashtags like #HostingerScam and #RefundHostinger began trending, particularly on X and TikTok. Influential tech YouTubers and bloggers picked up the story and started reaching out to Hostinger for comments, adding both pressure and visibility.

The power of numbers was evident. As more posts circulated and screenshots were shared en masse, Hostinger could no longer deny that something was flawed in their billing system. Notably, one viral thread containing screenshots of emails, payment confirmations, and dashboard settings gathered over 50,000 views and was retweeted by multiple tech journalists.

Hostinger’s Response and Admission

Finally, after weeks of silence and templated customer support replies, Hostinger issued a statement on their blog and official support Twitter account. They admitted that a “code-level exception” had caused some expired accounts to process renewals regardless of user settings. According to their post, a backend logic fault failed to check the auto-renew flag for a specific user subset during a routine billing system update.

“We deeply apologize to our users for this error. We are actively resolving all refund requests that were part of the erroneous renewal,” the statement read.

They provided a dedicated support form for affected users to request a refund and promised complete processing within 7-10 business days. The move was seen as too little, too late by many, but it did lead to the swift resolution of hundreds—if not thousands—of lingering refund cases.

Lessons Learned and the Future of Trust in Hosting Services

While Hostinger’s eventual transparency is commendable, the incident damaged the trust consumers had in their billing reliability. It also instigated a broader conversation about how digital service providers manage subscriptions, renewals, and user autonomy. Compared to industries like e-commerce, SaaS platforms often tread murky waters with user-friendly cancellation policies and inadequate notifications.

As a form of restitution, Hostinger claimed they would introduce two key changes:

  • Enhanced Audit Trails: Users will be able to view detailed logs of billing and setting changes, including timestamps and device/browser data.
  • Better Notification Emails: Upcoming renewals would be highlighted with clearer warnings and “final notice” messages requiring active validation within 48 hours.

Despite those promises, tech analysts and watchdogs continue to monitor the company’s billing practices, especially after the glitch tarnished its reputation for seamless automation and transparency.

FAQ: Billing Glitch and Refunds at Hostinger

  • Q: Why was I charged if I turned off auto-renew?
    A technical issue in Hostinger’s backend caused renewals to be processed even when auto-renew was disabled in some accounts. This was later acknowledged by the company.
  • Q: How can I get a refund if I was affected?
    Hostinger provided a dedicated refund request form for affected users. Those who haven’t received a refund should contact support with screenshots and transaction IDs.
  • Q: Can I file a chargeback instead?
    Yes, you can try to initiate a chargeback through your bank or payment provider. However, this may depend on your bank’s rules and how long ago the charge was made.
  • Q: Has Hostinger fixed the glitch?
    According to Hostinger, the bug that caused the glitch has been patched, and internal billing logs were updated to prevent similar issues in the future.
  • Q: How can I make sure auto-renew is off?
    Log into your Hostinger dashboard, go to the Billing section, and double-check both subscription status and payment methods. You can also delete cards and remove saved payment info if needed.

This situation serves as a cautionary tale for all online service users. It underscores the importance of checking billing settings and keeping documentation. And for tech companies, it’s a reminder that user trust depends not just on interfaces and speeds—but on accountability when things go wrong.