Japan coverage at a glance
| Attribute | 922 S5 in Japan |
|---|---|
| Pool | Part of the 350M+ residential network |
| Cities | Tokyo, Osaka, Yokohama, Nagoya, Fukuoka and more |
| Carriers | NTT, KDDI, SoftBank, So-net |
| Protocols | SOCKS5 / HTTP / HTTPS |
| Billing | Per IP — balance never expires |
| Checkout | Crypto, no KYC |
Why operators pick JP per-IP
Per-IP billing wins in Japan work where one identity maps to one account. You buy an JP address, assign it to a profile, and it stays yours — no bandwidth meter running in the background while the profile idles.
- Antidetect profiles — one Japan IP per browser profile, held for weeks.
- Marketplace accounts — JP sellers and buyers kept on separate lines.
- Drop and release monitoring — Tokyo and Osaka exits for regional launches.
- Localized QA — verify what a Japan shopper sees before a campaign ships.
Setting up an JP endpoint
Generate credentials in the dashboard, set country to JP (and a city if the job needs one), then paste the endpoint into your browser profile or script. SOCKS5 and HTTP(S) share the same login, so switching protocol never means re-buying an IP. Use code OPEN30 on the first order.
Frequently asked questions
How much is one Japan IP?
922 S5 sells JP addresses per IP starting at $0.07/IP, and volume tiers lower the unit price. Bought IPs stay on your balance indefinitely.
Can I keep the same Japan IP for a profile?
Yes. That is the point of per-IP billing — assign one JP address to one antidetect profile and reuse it as long as the profile lives.
Which Japan cities are available?
Tokyo, Osaka, Yokohama, Nagoya, Fukuoka and additional metros. City selection is part of the credential, so several JP cities can run at once.
Do you require KYC for Japan proxies?
No. Registration is email-only and checkout is crypto — USDT, BTC, LTC and others. Access activates once the payment confirms on-chain.