After installing a travel eSIM, many people open an IP-lookup site and panic:
“I am in Tokyo—why does it say Hong Kong or Singapore?”
That is not always a misconfiguration. Travel eSIMs often separate “which towers you use” from “where traffic exits to the public internet.” Product labels like native IP, roaming, and exit / egress IP describe exactly that.
This guide explains the three terms in plain language and why the IP country can differ from where you stand.
(Also: Data-only vs native numbers, and native vs roaming rules in the refund policy.)
Bottom line first: lookups usually show the exit IP
Once the eSIM is online, traffic traverses the carrier network and leaves through a public egress point. Websites, fraud checks, and region filters typically geolocate that exit IP (egress IP)—not your passport stamp and not simply “the tower city name.”
- Your location: where you are
- Radio network: which carrier/tower you registered on
- Exit IP: which country/node the public internet sees
These three can disagree—especially on roaming eSIMs.
What each term means
| Term | Plain meaning | What you may see on a product page |
|---|---|---|
| Native IP / local native IP | Local-carrier native path; egress closer to the destination | “Japan native IP”, “Korea IP native”, etc. |
| Roaming (non-native) | You use the destination network, but routing/egress may use another region’s node | “Singapore IP roaming”, “Hong Kong IP roaming”, “roaming route” |
| Exit / egress IP | The public IP location visible to websites | “Egress: Singapore IP”, “often Hong Kong egress” |
On this site, “native” and “which country the exit IP shows” are separate. Only plans marked native use local breakout. A country IP label, or a roaming-route label, is not native.
A destination-country IP is not native
An IP lookup that says Japan or the USA only means the exit is in that country. A native eSIM means traffic breaks out on the destination carrier’s network. The exit country can match while the route is still roaming.
That is why only native plans on this site say “local tower network” and “traffic does not route via China.” A roaming plan is not described that way, even when the exit is a Japan IP or a USA IP.
- Native Japan: for example AU (KDDI) and IIJ/Docomo. These are the plans that mention local towers and no China routing.
- Japan IP, but roaming: SoftBank only. The exit is labeled a Japan IP. It is not a native Japan eSIM.
- Singapore or Hong Kong IP roaming: for example some SoftBank/KDDI dual-network plans. You can be in Japan while the lookup shows Singapore or Hong Kong.
- Native USA: the AT&T +1 number SIM.
- USA IP, but wholesale roaming: Verizon, AT&T, and T-Mobile USA-IP plans. These are not native number SIMs.
Why can you be in country A while the IP looks like country B?
You (in Japan) → local tower → roaming/backbone routing → egress node (e.g. Singapore or Hong Kong) → sites see that node’s IP
So “in Japan, IP shows Singapore/Hong Kong” is often expected on plans labeled Singapore-IP roaming, Hong Kong-IP roaming, or Singapore/Hong Kong egress—not proof the eSIM connected to the wrong country.
If the plan promises Japan native IP but lookups stay unrelated for a long time, then check you are on the travel eSIM, VPN/private DNS is off, and you are not still on another SIM.
Typical traits of native IP
- Egress closer to the destination; some local apps/services feel smoother
- Latency often better (tower load still matters)
- Native ≠ phone number—native is about path/IP; calling needs separate product wording
- Refunds: native plans are usually stricter after QR/install codes are delivered—see the refund policy
Typical traits of roaming + labeled egress
- You use local radio in the destination; egress may be Hong Kong, Singapore, Malaysia, etc. (per plan)
- Some China / Greater Bay plans note Singapore egress and LINE/IG/FB without VPN—that is about the egress node, not denying you are on the ground locally
- Roaming routes usually need data roaming on
- Refunds more often follow install/activate status, unlike many native plans
What to read on the product page
- Look for native vs roaming and exit/egress labels—not only the country name
- If you need a local-looking IP, prioritize native IP
- If you care about specific apps on restricted networks, read egress notes and any “supported / not guaranteed” lines (e.g. ChatGPT/TikTok)
- One destination can have multiple carrier options with different IP types—confirm the option you select
Myths
“Wrong IP country means a broken eSIM.”
Not necessarily—match it to the product’s egress/roaming text first.
“Native IP means I can call.”
No—native is path/IP; numbers/calling are separate.
“Hong Kong IP roaming means it only works in Hong Kong.”
No—it usually describes egress/routing; coverage is the plan’s coverage list.
“Every Japan eSIM has a Japan IP.”
No—options may be Japan native IP or Singapore/Hong Kong IP roaming, etc.
“A Japan IP or USA IP means it is native.”
No. That only means the exit is in that country. SoftBank-only can be a Japan-IP roaming route. A US wholesale plan can be a USA IP and still not be a native number SIM. This site mentions local towers and “does not route via China” only on native plans.
Bottom line
The IP sites see mainly comes from the exit / egress node. Native IP keeps egress closer to the destination; roaming plans may use local towers while exiting via Hong Kong or Singapore—so a Singapore/Hong Kong IP while you are in Japan is often normal.
Separate “where I go” from “how egress should look” when choosing a plan. Connectivity issues are a different checklist (troubleshooting) from IP-country mismatch.
