# Hostinger review: plans, latency from China and test IPs

Last price check: 2026-11-17

Hostinger was founded in 2004 and offers 9 data centres. This site lists 1 of its plans (1 Main server, 0 Relay); routes: Standard route. Refund: 30 days. All listed plans are currently in stock.

Black Friday sale on: 1 plans take part, the first ending 2026-12-14; they carry the “Limited-time” tag in the table below. Every vendor’s sale: [Black Friday and Singles Day VPS deals 2026](https://vps.appsail.dev/en/guide/black-friday-vps-2026/).

## All plans

Sorted by monthly price, lowest first, including out-of-stock plans. Figures in the table are checked by hand. Test IPs and latency on the three carriers for each data centre are in the [test IP table](https://vps.appsail.dev/en/hostinger/#test-ip-section) below.

| Monthly price | Vendor | Route | Test IP | Buy | Use | Specs | Bandwidth | Traffic | Price and discounts | Refund | Claude | Available countries and regions |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| $8.79$24.49 -64% | [Hostinger](https://vps.appsail.dev/en/hostinger/) | Standard route | [72.61.127.234](https://www.itdog.cn/ping/72.61.127.234)[9 more data centres in the table below](https://vps.appsail.dev/en/hostinger/#test-ip-section) | [KVM 2](https://vps.appsail.dev/go/hostinger/KVM%202) Limited time Black Friday until 12/14 | Main server (8G) | 2 vCPU / 8G / 100GB NVMe | 1Gbps | 8TB | $8.79/mo, 24 months prepaid (Black Friday sale, 64% off the list price of $24.49/mo)Renewal $14.99/mo | 30 days | Supported | United States, United Kingdom, France, Germany, Lithuania, India, Indonesia, Malaysia, Brazil |

## Test IPs and latency on the three carriers

Each test IP is pinged 4 times by up to 12 public measurement probes on each of mainland China's Telecom, Unicom and Mobile, and the results are averaged. Each run measures the vendor measured longest ago, and the day's runs are averaged. This table was measured on 2026-11-10. Loss of 20% or more is marked in orange: such a latency is only the average of the packets that came back, and the connection will lag in real use. “no reply” means that carrier's probes could not reach the IP. Click an IP to open a multi-node ping across China on itdog and test it yourself.

The “Evening peak” line under each time is a second measurement taken around 9 pm Beijing time; compare it with the early-morning figure above to see how much slower the evening is.

“Outbound route” is a traceroute to the test IP from one probe on each of the three carriers, showing which network the path from China to the data centre crosses: whether Telecom enters CN2, whether Unicom uses 9929 or 4837, whether Mobile uses CMIN2 or CMI. The return path (data centre back to China) cannot be seen from China, and a vendor's CN2 GIA or CMIN2 label usually refers to the return path, so the two may differ. Hover over a route to see the test date.

Fastest data centre per carrier: Telecom KVM 2 (Jakarta) 155 ms; Unicom KVM 2 (Jakarta) 146 ms; Mobile KVM 2 158 ms.

| Test IP | Plan (data centre) | Telecom | Unicom | Mobile | Outbound route | Test date |
| --- | --- | --- | --- | --- | --- | --- |
| [72.61.127.234](https://www.itdog.cn/ping/72.61.127.234) | KVM 2 | 255 msEvening peak 280 ms | 353 msloss 2%Evening peak 475 ms | 158 msEvening peak 233 ms | Telecom 163Unicom 4837Mobile CMI | 2026-11-10 |
| [45.132.241.142](https://www.itdog.cn/ping/45.132.241.142) | KVM 2 (Phoenix) | 178 msEvening peak 229 ms, loss 21% | 210 msEvening peak 254 ms | 240 msEvening peak 251 ms, loss 23% | Telecom 163Unicom 4837Mobile CMI | 2026-11-10 |
| [147.79.78.203](https://www.itdog.cn/ping/147.79.78.203) | KVM 2 (Boston) | 227 msEvening peak 237 ms | 253 msEvening peak 355 ms | 265 msEvening peak 285 ms | Telecom 163Unicom 4837Mobile CMI | 2026-11-10 |
| [72.62.234.24](https://www.itdog.cn/ping/72.62.234.24) | KVM 2 (Paris) | 255 msloss 2%Evening peak 261 ms | 276 msEvening peak 296 ms | 246 msEvening peak 306 ms | Telecom 163Mobile CMI | 2026-11-10 |
| [76.13.14.153](https://www.itdog.cn/ping/76.13.14.153) | KVM 2 (Frankfurt) | 191 msEvening peak 215 ms | 269 msloss 5%Evening peak 274 ms | 244 msEvening peak 327 ms | Telecom 163Unicom 4837Mobile CMI | 2026-11-10 |
| [91.108.122.207](https://www.itdog.cn/ping/91.108.122.207) | KVM 2 (Vilnius) | 240 msloss 2%Evening peak 252 ms | 307 msEvening peak 432 ms | 314 msEvening peak 314 ms | Telecom 163Mobile CMI | 2026-11-10 |
| [72.62.210.159](https://www.itdog.cn/ping/72.62.210.159) | KVM 2 (Manchester) | 268 msEvening peak 270 ms | 276 msEvening peak 280 ms | 227 msEvening peak 252 ms | Telecom 163Unicom 4837Mobile CMI | 2026-11-10 |
| [147.93.111.193](https://www.itdog.cn/ping/147.93.111.193) | KVM 2 (Mumbai) | 269 msEvening peak 406 ms, loss 29% | 312 msloss 5%Evening peak 481 ms, loss 42% | 346 msEvening peak 367 ms | Telecom 163Unicom 4837Mobile CMI | 2026-11-10 |
| [76.13.22.207](https://www.itdog.cn/ping/76.13.22.207) | KVM 2 (Jakarta) | 155 msEvening peak 193 ms | 146 msEvening peak 253 ms | 166 msEvening peak 121 ms | Telecom 163Unicom 4837Mobile CMI | 2026-11-10 |
| [191.101.78.164](https://www.itdog.cn/ping/191.101.78.164) | KVM 2 (São Paulo) | 338 msloss 2%Evening peak 345 ms | 354 msEvening peak 390 ms | 357 msEvening peak 387 ms | Telecom 163Unicom 4837Mobile CMI | 2026-11-10 |

Probe cities: Telecom: Dongguan, Yancheng, Xi'an, Meikeng, Guangzhou, Chongqing; Unicom: Nanning, Wuhu, Wuhan, Changsha, Xi'an, Jingzhou; Mobile: Nanning, Beijing, Taishan, Guangzhou, Kunming, Wuxi. Probes change from day to day; figures are for reference only.

## Latency from outside China

Each test IP is pinged 3 times by two Globalping probes in each of 9 cities outside mainland China, and the results are averaged; several runs on one day are averaged too. The closer the data centre is to the user, the lower the latency: for an agent or a website, look at the column nearest to you or your users. Loss of 20% or more is marked in orange.

| Test IP | Plan (data centre) | Frankfurt | São Paulo | Taipei | Hong Kong | New York | Los Angeles | London | Sydney | Tokyo | Test date |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 72.61.127.234 | KVM 2 | 157 ms | 357 ms | 58 ms | 40 ms | 252 ms | 243 ms | 172 ms | 98 ms | 73 ms | 2026-11-10 |
| 45.132.241.142 | KVM 2 (Phoenix) | 159 ms | 159 msloss 50% | 154 ms | 157 ms | 73 ms | 12 ms | 132 ms | 171 ms | 126 ms | 2026-11-10 |
| 147.79.78.203 | KVM 2 (Boston) | 84 ms | 123 ms | 190 ms | 213 ms | 8 ms | 70 ms | 75 ms | 218 ms | 177 ms | 2026-11-10 |
| 72.62.234.24 | KVM 2 (Paris) | 11 ms | 188 ms | 239 ms | 166 ms | 80 ms | 144 ms | 10 ms | 242 ms | 239 ms | 2026-11-10 |
| 76.13.14.153 | KVM 2 (Frankfurt) | 3 ms | 196 ms | 266 msloss 50% | 242 ms | 88 ms | 147 ms | 18 ms | 304 ms | 245 ms | 2026-11-10 |
| 91.108.122.207 | KVM 2 (Vilnius) | 22 ms | 215 ms | 255 ms | 203 ms | 126 ms | 175 ms | 41 ms | 288 ms | 264 ms | 2026-11-10 |
| 72.62.210.159 | KVM 2 (Manchester) | 23 ms | 201 ms | 231 ms | 195 ms | 46 ms | 140 ms | 7 ms | 250 ms | 227 ms | 2026-11-10 |
| 147.93.111.193 | KVM 2 (Mumbai) | 121 ms | 264 ms | 215 ms | 97 ms | 219 ms | 232 ms | 147 ms | 147 ms | 124 ms | 2026-11-10 |
| 76.13.22.207 | KVM 2 (Jakarta) | 217 ms | 349 ms | 68 ms | 48 ms | 235 ms | 183 ms | 182 ms | 106 ms | 84 ms | 2026-11-10 |
| 191.101.78.164 | KVM 2 (São Paulo) | 194 ms | 2 ms | 297 ms | 351 ms | 110 ms | 170 ms | 192 ms | 339 ms | 268 ms | 2026-11-10 |

## Company background

- Founded: 2004
- Operating entity: Hostinger International Ltd (Larnaca, Cyprus; the contracting party for users in most countries; the UK, Indonesia and some others have separate entities)
- Headquarters: Vilnius, Lithuania (founded in Kaunas in 2004)
- Ownership: Private company, not listed; the private equity firm ConHostinger has held about 30% since 2021, and the founders and team hold the rest

Founded in Kaunas in 2004 as Hosting Media and renamed Hostinger in 2011. The website says it has more than 4 million customers (another page says 5 million or more), over 1000 employees and data centres in 12 locations. In 2024 it shut down its free hosting service 000webhost. Wikipedia puts its 2025 revenue at about €275 million.

Reputation: Trustpilot 4.6 (over 70,000 reviews). Often praised for an easy control panel, fair prices and friendly human support; common complaints are being held up by the AI support bot first, sudden account suspensions, and disputes over refunds and renewal bills.

Checked on 2026-10-20. Sources: [1](https://www.hostinger.com/about) · [2](https://www.hostinger.com/legal/universal-terms-of-service-agreement) · [3](https://en.wikipedia.org/wiki/Hostinger) · [4](https://www.trustpilot.com/review/hostinger.com)

## Related guides

- [Black Friday VPS deals 2026](https://vps.appsail.dev/en/guide/black-friday-vps-2026/)
- [Best VPS for Claude Code](https://vps.appsail.dev/en/guide/claude-code-vps/)
- [VPS for self-hosted AI agents](https://vps.appsail.dev/en/guide/ai-agent/)
- [Hetzner alternatives](https://vps.appsail.dev/en/guide/hetzner-alternative/)
- [VPS for Australia and New Zealand](https://vps.appsail.dev/en/guide/australia-vps/)

## Other vendors

[RackNerd](https://vps.appsail.dev/en/racknerd/)[BandwagonHost](https://vps.appsail.dev/en/bandwagonhost/)[DigitalOcean](https://vps.appsail.dev/en/digitalocean/)[Lcayun](https://vps.appsail.dev/en/lcayun/)[TmhHost](https://vps.appsail.dev/en/tmhhost/)[DMIT](https://vps.appsail.dev/en/dmit/)[LisaHost](https://vps.appsail.dev/en/lisahost/)[V.PS](https://vps.appsail.dev/en/vpshosting/)[HostKvm](https://vps.appsail.dev/en/hostkvm/)[Jtti](https://vps.appsail.dev/en/jtti/)[HNCloud](https://vps.appsail.dev/en/hncloud/)

### Where the test IPs and latency figures come from

A test IP is a machine the vendor publishes for this data centre and this route. Before buying you can ping it to see how fast your own network reaches it. Clicking an IP opens a multi-node ping across China on itdog, which you can break down by province and carrier.

- **Where the IPs come from**: The vendor's website or Looking Glass page, or the vendor's reply to a support ticket; a few come from third-party reviews. When an IP published by the vendor no longer answers, we replace it with the reachable address with the lowest latency in the same subnet.
- **Who measures the latency**: Probes in mainland China from two public measurement networks. One vendor is measured each day at 5 a.m. Beijing time, in turn, so each vendor comes round about every ten days. Each run uses up to 12 probes on each of Telecom, Unicom and Mobile (6 per network; when a network has fewer that day, we use what it has), and each probe pings 4 times.
- **How to read it**: “Telecom 18 · Unicom 22 · Mobile 37 ms” is the latency on each of the three carriers; hover to see the probe cities and loss rate. When a carrier shows 20% loss or more, it is spelt out, e.g. “Telecom 99 (loss 55%)”. That latency figure is only the average of the packets that came back, and in real use the connection will lag; the “My network” filter and sorting do not count it as reachable. We have cross-checked such loss over TCP ports: the handshake time grows several-fold, so it is the path from that carrier to the data centre that drops packets, not the server rate-limiting ping. Sorting by the column uses the fastest of the three carriers.
- **Colours**: The limit depends on the data centre's region: 45 ms for Hong Kong, 80 ms for the rest of Asia, 170 ms outside Asia. Within the limit is green, over it red. The shade compares a figure with the other data centres in the same region: the faster half of the greens is deep green, the slower half of the reds deep red, and so is anything losing packets or unreachable. The line under the figures is the test IP.
- **No reply and unreachable**: “no reply” on one carrier means that probe could not reach the IP. “Test IP unreachable” means probes both inside and outside China could not reach it, usually because the IP has been retired; it does not mean the route or the server is unavailable. IPs that block ping are tested on TCP port 80/443 instead.
- **How accurate is it**: For reference only. Each run uses at most 12 probes per carrier, pinging 4 times each; the probes change every run, most sit in data centres rather than on home broadband, and bandwidth and the evening peak are not measured.

### What the route names mean

The route is which carrier's network, and which of its networks, carries traffic between mainland China and the data centre. The closer to China and the better the route, the smoother SSH and web pages feel, and the steadier things are at the evening peak.

Each tag colour stands for one carrier: red for Telecom, blue for Unicom, green for Mobile. The solid colour is that carrier's premium route, the pale one its standard tier, and a grey outline is an ordinary route with no optimisation.

- **CN2 GIA**: China Telecom's premium network (AS4809), with CN2 both ways. Low latency, stable at the evening peak, the most expensive. The first choice for Telecom users.
- **CN2 GT**: The standard version of Telecom CN2: the international leg uses CN2, the domestic leg uses the ordinary 163 backbone. Cheaper than GIA, a little less stable at the evening peak.
- **CN2**: The vendor only says CN2, without stating GIA or GT; it is safer to expect GT-level performance.
- **9929**: China Unicom's premium network (AS9929, also called Unicom A network or CUII). Works best for Unicom users.
- **4837**: China Unicom's standard backbone (AS4837). Cheap, plentiful bandwidth; may be congested at the evening peak.
- **CMIN2**: China Mobile's premium network (AS58807). Works best for Mobile users.
- **CMI**: China Mobile International's standard outbound route (AS58453): better than a standard route for Mobile users, worse than CMIN2.
- **All 3 carriers optimised**: The vendor states that return traffic for all of Telecom, Unicom and Mobile goes over optimised routes, so it will not be too bad whichever broadband you use.
- **Standard route**: A regular international route, not optimised for mainland China; it can slow down noticeably at the evening peak. As a Main server it may lag from China; if it does, add a Relay in front of it.

This site labels routes as each vendor states them; the “Outbound route” column on vendor pages is our own traceroute from China, which cannot see the return path. Real-world results depend on your own carrier; you can test with the test IP before buying.

Guides: [VPS for self-hosted AI agents](https://vps.appsail.dev/en/guide/ai-agent/) · [Hetzner alternatives](https://vps.appsail.dev/en/guide/hetzner-alternative/) · [Serving users in mainland China: Hong Kong and Japan](https://vps.appsail.dev/en/guide/hk-japan-vps-china/) · [VPS for Australia and New Zealand](https://vps.appsail.dev/en/guide/australia-vps/) · [Best VPS for Claude Code](https://vps.appsail.dev/en/guide/claude-code-vps/) · [Black Friday VPS deals 2026](https://vps.appsail.dev/en/guide/black-friday-vps-2026/) · [Stock changes (RSS)](https://vps.appsail.dev/feed.xml)

About the data: prices, data centres and bandwidth are as stated on each vendor's website. Each row is one plan: “Main server (8G)” is the cheapest 8G RAM plan we have verified for that vendor and route, for running Claude Code; “Relay (China-optimised route)” is the cheapest plan of any RAM size for that vendor and route, used as a proxy or relay. All prices are converted to a US dollar monthly price (¥6.68 = $1, mid-rate on 2026-11-17); where a yearly price exists we divide it by 12, and the monthly price is shown under “Price and discounts”. Route labels follow the vendor's own product names or descriptions; this site only traces the outbound route from China (the “Outbound route” column on vendor pages). The green tag “Native / Residential / Dual-ISP” after the route marks the IP type (of interest for cross-border e-commerce and overseas social media work), also as the vendor's product name or description states it; this site does not verify each IP. “CN2” means the vendor only says CN2, without stating GIA or GT; “All 3 carriers optimised” means the vendor states that return traffic for Telecom, Unicom and Mobile goes over optimised routes. The “Telecom xx · Unicom xx · Mobile xx ms” under the test IP is the average latency of pings from up to 12 public measurement probes on each of mainland China's three carriers; one vendor is measured each day at 5 a.m. Beijing time, in turn, so each vendor comes round about every ten days. The probes differ every run, so the figures are for reference only; hover to see the probe cities and loss rate. When one network shows 20% loss or more it is marked “Telecom 99 (loss 55%)”; such a route will lag in real use, and filters and sorting do not count it as reachable. IPs that block ping are tested on a TCP port instead. “no reply” on one network means that probe could not reach the IP; “Test IP unreachable” means probes both inside and outside China could not reach it, usually because the test IP has been retired; it does not mean the route or the server is unavailable. Hong Kong data centres are not in Anthropic's supported regions; other data centres are judged by the official list of supported countries, which does not mean every IP has been tested to work.

Some buy links carry an affiliate commission; commissions do not affect the ranking or the data in the table. Where a vendor has a public coupon code, it is shown in the “Price and discounts” column; enter it yourself at checkout.
