Hostinger Support Review: The Question Isn't Speed, It's Scope

Most support reviews are one person’s anecdote about one ticket. Ours would have been too — so we went looking for what these companies commit to in writing instead, and found something more useful than a response time.

Two of these four providers publish exactly where their support stops. Two don’t publish anything.

What Hostinger commits to: nothing in writing

We read Hostinger’s Universal Terms of Service looking for a support obligation — a response time, an availability window, a scope definition. There isn’t one. The word “support” appears in the document only in the context of currency support, deprecated services and fraud prevention.

That’s not unusual and it isn’t an accusation. Budget hosts generally don’t write support SLAs into their terms, because doing so creates a liability priced into a $11.99 plan. But it does mean the 24/7 support on the marketing page is a description of intent, not a commitment you can hold them to.

What we could confirm is the shape of the front line. Hostinger’s own VPS page carries customer testimonials describing it plainly:

“the AI chat bot + human chat, if AI can’t resolve your question”

“Kodee and Mohammad from the support team were incredibly patient and thorough”

Kodee is Hostinger’s AI assistant, and it answers first. Those are testimonials the company chose to publish, so they’re the picture it wants you to have — an AI first touch with human escalation behind it. Reasonable for the price, and worth knowing before you open a chat expecting a person.

On phone support: we found no phone number on either Hostinger’s support page or its VPS page. Absence from those pages isn’t proof none exists, but it’s not being offered as a channel.

Cloudways publishes actual numbers

This is the contrast worth the article. Cloudways puts response times in print, tiered, with what each costs:

Read the free tier honestly: 12 hours for an initial response. That’s the number attached to the plan most people are on, and it’s a long way from what “24/7 support” implies. Cloudways also advertises a “90 seconds average response time” — an average is not a commitment, and the SLA table is the part that binds.

The 15-minute chat rule is the detail that catches people. On the free tier, a chat that isn’t resolved in fifteen minutes becomes a ticket — and the ticket clock is the 12-hour one. A hard problem doesn’t get more chat time; it gets moved to the slow queue.

And Cloudways publishes what it won’t touch at any tier:

“Changes to your website content/appearance” · “Changes to the functionality of plugins/themes/modules” · “Debugging custom code” · “Application level security issues”

That last one deserves attention. Application-level security is out of scope on a managed host — so a compromised WordPress install is your problem, not theirs, on a product bought largely for not having to think about servers.

Liquid Web publishes the boundary as a table

Liquid Web goes furthest, and its matrix is the clearest answer to the question most people are actually asking. All tiers get 24/7/365 availability. What separates them is what support will do.

Look at the Self-managed column. You get 24/7 support that will fix the hardware and the network — and will not troubleshoot your server, patch your OS, or configure your firewall. “24/7 support” is entirely true and answers almost none of the questions a VPS owner has.

That’s the boundary, stated in advance rather than discovered at 3am. When people say a host told them something was “outside our scope”, this table is the documented version of that conversation.

Where Liquid Web does engage, it names the ground: Linux and Windows administration, WordPress, WooCommerce and Magento, and WHM/cPanel, Plesk and InterWorx. Contact is chat or a support case — the FAQ names no phone channel.

The thing that actually predicts your experience

Not the hour you write in. Whether your question is inside the scope of the product you bought.

A billing question, a DNS record, a control-panel setting — inside scope everywhere, including the cheapest plan. These get answered.

“Why is my server load high”, “configure this firewall rule”, “my custom code throws a 500” — out of scope on unmanaged and self-managed tiers by published policy, and out of scope at Cloudways at every tier for the custom-code case. No amount of persistence changes a documented boundary.

So the question to ask before buying isn’t “is the support good”. It’s: the problems I’ll actually have — are they on the list? What sustained CPU load is contractually allowed is the same shape of question, and the answer lives in the same place: the product description, not the support page.

The honest pricing of the gap. Moving a server question from out-of-scope to in-scope costs real money — Cloudways’ Advanced tier is around $100/month against a $11 server, and Liquid Web’s managed tiers are a different price class from a budget VPS. For most people the cheaper answer is to learn the server, which is why basic hardening is worth an evening.

The providers

Hostinger — $11.99 renewal for 4GB, AI first touch with human escalation, no support commitment in its terms. Good value on the understanding that support is a service not a guarantee, and that root-level server questions on an unmanaged VPS are yours. Best fit if you’re comfortable operating the box.

Cloudways — from $11 for 2GB billed monthly, and the most transparent SLA of the four: 12 hours free, 6 or 2 hours paid, with the exclusions published. Managed hosting on top of DigitalOcean or AWS. Read the 15-minute chat rule and the out-of-scope list before buying — application-level security not being covered is the surprising one.

SiteGround — we could not read its support pages from either of our vantage points; it returned 403 to us in the US and geo-redirected in Europe. We have nothing verified to report, and we’re not going to characterise a company’s support from memory.

Liquid Web — the clearest published boundary in the category, with a tier matrix stating exactly which column stops troubleshooting your server. A different price class from everything above, and the honest answer if you need someone else responsible for the operating system.

How we checked this

Every figure here is from the provider’s own published page, read on 18 August 2026: Cloudways’ support page for the three SLA tiers, the 15- and 30-minute chat conversion rules and the out-of-scope list; Liquid Web’s support page for the tier matrix and the 24/7/365 statement; Hostinger’s Universal Terms of Service, VPS page and support page.

We did not open a single support ticket, and this article’s brief asked us to open five overnight. The plan was a billing question, a DNS problem, a root-level Linux question, a suspected outage and a cancellation, with response times logged in a table. We don’t hold accounts at these providers, and opening tickets under false pretences to time the replies — particularly a cancellation request for an account that doesn’t exist — is not something we’ll do to companies we then earn commission from. Publishing invented timings would be worse. So the article covers what’s verifiable instead, and we think the published scope is the more decisive evidence anyway: an anecdote about five tickets on one night wouldn’t generalise, and a published exclusion list does.

On Hostinger’s terms: we searched the document for a support obligation and found none. Absence from that document is not absence from the company’s practice — it means there’s no contractual commitment, not that support is bad.

On the AI first touch: the two quotes are customer testimonials published by Hostinger on its own VPS page, not our observation. They’re marketing selection, and we’ve used them only for the structural point that Kodee answers before a human does — which is what Hostinger itself is describing.

On phone support: we found no phone number on Hostinger’s support or VPS pages, and Liquid Web’s contact FAQ names chat and support cases only. Neither is proof no phone channel exists, and Cloudways’ Premium tier explicitly includes phone.

On SiteGround: two vantage points, both blocked. That’s a limitation of our access, not a finding about the company.

What we did not do: contact any provider’s support, hold an account anywhere, time a response, verify any advertised average, or test whether documented scope matches actual behaviour — which is the obvious gap and would need real accounts to close.

The host links above are affiliate links. The provider we’ve praised most for transparency is one of the most expensive, and the article’s conclusion for most readers is to learn the server rather than buy the support tier.

FAQ

Does Hostinger have good customer support?

Its terms contain no response-time or scope commitment, so there’s nothing to hold it to contractually. The front line is Kodee, its AI assistant, with human escalation behind it — which Hostinger’s own published testimonials describe directly.

Does Hostinger have phone support?

We found no phone number on its support page or VPS page. It’s not offered as a channel there, though absence from those pages isn’t conclusive.

What is Hostinger’s live chat response time?

Not published anywhere we could find, and not committed to in its terms. By contrast Cloudways publishes a 12-hour initial ticket response on its free tier and 3 hours for high priority.

Which host publishes a real support SLA?

Cloudways, with three tiers: 12 hours initial response free, 6 hours at roughly $100/month, 2 hours at roughly $500/month, and high-priority times of 3 hours, 30 minutes and 10 minutes respectively.

What won’t managed hosting support help with?

Cloudways publishes its exclusions at every tier: website content and appearance, plugin and theme functionality, debugging custom code, and application-level security issues.

Does 24/7 support mean they’ll fix my server?

Not necessarily. Liquid Web’s Self-managed tier includes 24/7/365 availability but excludes server-side troubleshooting, OS patching and firewall configuration. Availability and scope are separate things.

How do I judge support before buying?

List the problems you’ll realistically have, then check them against the provider’s published scope. Where no scope is published, assume anything above the control panel is yours.