Your quota dies on day four. Again. So you go hunting for a bug host Telkomsel 2026 working list, find a post in some Facebook group, copy a hostname, paste it into HTTP Injector, and… connection failed. Zero bytes transferred. Story of your life.
I’ve been on that treadmill for years. And the honest truth is that 90% of the lists floating around are recycled hostnames from 2023 that stopped working a long time ago. So instead of handing you another dead list, let me show you what actually still works — and how to test any host yourself in under two minutes.
What a “Bug Host” Actually Is
A bug host is a hostname or IP that the carrier’s billing system treats as free traffic. Usually it’s a domain tied to a whitelisted service — the operator’s own portal, a gaming package, a partner content site — where traffic isn’t counted against your quota.
When you point your SSH or V2Ray payload at one of those hostnames and set the right Host header plus SNI, the billing layer sees “this guy is browsing the free portal” while your tunnel quietly carries everything else. That mismatch is the whole trick. Nothing magic about it.
Quick reality check: this sits squarely in the grey zone of your carrier’s terms of service. It’s educational content, not an endorsement. Use it knowing the risk — accounts do get throttled, and hosts get patched fast.
Why These Lists Rotate Every Few Weeks
Because carriers patch them. Constantly.
Once a host gets popular enough — and popular means it spreads across a thousand Telegram channels in three days — the network team notices the traffic anomaly and either kills the zero-rating, adds header inspection, or blackholes the hostname entirely. That’s why any list claiming “2026 working list, verified, no dead hosts” is either very new or very dishonest.
The reliable approach isn’t memorizing hostnames. It’s learning how to find and verify them yourself. That skill doesn’t expire.
The Host Categories That Still Hold Up
After testing more than a hundred candidates over the past few months, the survivors almost always fall into three buckets.
1. Operator-owned portals
- Domains under the carrier’s own free-access subdomains — usually the self-care and package-info pages
- They’re whitelisted by design, so billing rarely touches them
- Look for hosts that respond on port
80and8080without redirecting
2. Gaming and package-partner hosts
- Game top-up portals and package-activation endpoints bundled with unlimited-game plans
- Often allow
443with a clean TLS handshake, which pairs nicely with SNI-based setups - These tend to have the longest lifespan because breaking them breaks a paid product
3. CDN-fronted hosts
Some operators whitelist CDN ranges for their own asset delivery. If you can front your tunnel through a hostname inside that range, you get a stable route — but this one’s fragile because the CDN config changes without warning. Fun when it works, painful when it dies mid-session.
How to Test a Host in 90 Seconds
Don’t trust screenshots. Test it.
- Ping isn’t enough — ICMP can reply while HTTP is blocked. Skip it.
- Check the HTTP response with
curl -sk -o /dev/null -w "%{http_code}" --max-time 5 http://yourhost:80 - A
200or302means the host is alive and reachable. A timeout or000means dead. - Then open the host in your browser on mobile data — not Wi-Fi. If the page loads while your quota is at zero, the zero-rating is live.
- Finally, plug it into your client and watch the byte counter. If it climbs past 1 MB, you’re in.
That last step is the only test that matters. Everything before it is just filtering out the obvious junk.
Setting It Up in HTTP Injector and v2rayNG
HTTP Injector (SSH + payload)
Paste the host into the Host field, set port to 80 or 8080, then add these lines to your payload:
Host: yourhost.com
X-Online-Host: yourhost.com
User-Agent: Mozilla/5.0
Keep the SSH connection itself on port 443 or 22. The bug host only handles the fake HTTP layer — the tunnel is separate.
v2rayNG / NekoBox (WebSocket + TLS)
Set the address to your server, the port to 443, and enable TLS with SNI set to the bug host. Path stays at /ws or whatever your server uses. In my experience, Xray-core with ws transport survives carrier DPI longer than raw SSH, especially on the newer filtering rules.
One thing people get wrong: WireGuard can’t do this. It’s UDP with no HTTP header, so there’s nothing to spoof. If a tutorial tells you to use a bug host with WireGuard, close the tab.
Tips and Tricks From Someone Who’s Banged His Head on This
- Rotate hosts weekly. Keep three working ones saved. One will die the day you need it most.
- Test on mobile data with the quota actually at zero. A host that “works” while you still have quota proves nothing.
- Port
8080and8880are consistently less filtered than443for plain HTTP payloads. - Cheap VPS beats free SSH accounts every time — free servers die in days, and you’ll blame the host when the problem is the server.
- If you’re doing anything beyond browsing, grab a proper VPN premium instead. The cat-and-mouse game costs more in time than the subscription costs in money.
- Keep your config backups in cloud storage, not in a chat with yourself. You’ll thank yourself later.
FAQ
Is there a permanently working Telkomsel bug host?
No. Anything “permanent” is either patched within weeks or was never real. Treat every host as temporary and you’ll be far less frustrated.
Why do hosts work on one phone but not another?
APN settings, IPv6 vs IPv4 routing, and client version all matter. Set your APN protocol to IPv4 only and retest — this alone fixes a surprising number of failures.
Which client is best in 2026?
NekoBox for flexibility, v2rayNG for stability, HTTP Injector if you’re on SSH with custom payloads. Honestly, the client matters less than whether your host is actually alive.
Does this still work on 5G?
Sporadically. The 5G core uses stricter billing inspection in most areas I’ve tested, so LTE hosts often fail on 5G. Lock your network to LTE and see if the host comes back.
My Pick
Skip the dead lists and build your own three-host rotation. That’s the only setup that’s ever stayed reliable for me. And if you want a server that doesn’t die every 48 hours, grab a free account at claudessh.com and start testing from a stable base — it’s the closest thing to a shortcut this hobby has.
Now go test a host. Two minutes, one curl command, real answer.
You can also create the same type of account on RouterSSH SSH SSL — it covers 196 countries with unlimited bandwidth.
