Travel eSIM Local IP Breakout and Latency Directory

Travel eSIM local IP breakout is the single variable that separates a usable cellular line from one that feels broken on US soil: it determines whether your prepaid profile injects traffic onto the public internet near your hotel or trombones packets through a distant routing server first. As of June 22, 2026, this directory maps Airalo, Saily, Nomad, and Ubigi to measured exit IP geography, traceroute hints, and median ICMP from Network Scrutiny field audits—so you can pick a provider before you rely on Zoom, banking MFA, or cloud gaming on cellular data abroad or at home.

Stat: Hub-routed profiles in our May 2026 US audit averaged 94 ms higher RTT to US-East cloud probes than local-breakout Nomad sessions at the same street address (N=12 paired samples). Saily USA never showed a US exit IP in 6/6 tests. Source: Saily vs Nomad US breakout audit.

---

Original research: four-provider routing directory (June 2026)

We normalized Airalo, Saily, Nomad, and Ubigi into one comparable matrix on June 22, 2026, pulling measured rows from our May 15–22, 2026 US breakout audit, June 10–11, 2026 Paris spot check, and methodology flags where Network Scrutiny has not yet published a controlled US probe for a brand. Each row used the same protocol: unlocked iPhone 15 and Pixel 8, cellular-only, travel line as default mobile data, ipinfo.io/json for exit geography, 30 ICMP probes to 8.8.8.8, optional six-hop traceroute, breakout class LBO (local) vs IHBO (international hub).

Provider	SKU / market	Metro tested	Exit IP country	Routing-server hint (ASN / hop names)	Median RTT 8.8.8.8	Breakout	NS audit source
Nomad	10 GB / US	NYC	US	US-metro hostnames by hop 3; domestic ASN	26 ms	LBO	US audit 2026-05-16
Nomad	10 GB / US	Chicago	US	AT&T attach; US peering	31 ms	LBO	US audit 2026-05-18
Nomad	10 GB / US	San Francisco	US	T-Mobile 310-260; US egress	29 ms	LBO	US audit 2026-05-20
Saily	5 GB / US	NYC	NL	1Global hub; ams-class hop names	118 ms	IHBO	US audit 2026-05-16
Saily	5 GB / US	Chicago	NL	EU aggregator pattern	112 ms	IHBO	US audit 2026-05-18
Saily	5 GB / US	San Francisco	NL	EU hub pattern	109 ms	IHBO	US audit 2026-05-20
Airalo	3 GB / France	Paris (CDG area)	FR	Paris-metro hostnames hop 3; Bouygues-class ASN	31 ms	LBO	Traceroute audit 2026-06-10
Airalo	US country SKUs	—	Verify	Marketplace; per-SKU wholesale PGW	Verify	Unknown¹	Airalo vs Ubigi protocol
Ubigi	US / EU SKUs	—	Verify	Partner-specific per country	Verify	Unknown¹	Airalo vs Ubigi protocol

¹ Where I am less sure: Airalo and Ubigi US breakout can differ by underlying PLMN and wholesale rotation; we have not published a controlled US numeric row for either brand as of June 22, 2026. Run the directory protocol before you commit gigabytes.

Dataset (Schema.org): name Travel eSIM local IP breakout and latency directory — 4-provider routing matrix; datePublished 2026-06-22; license CC BY 4.0; URL https://networkscrutiny.com/guides/travel-esim-latency-local-ip-breakout-directory/#directory-matrix; inLanguage en-US.

{
  "@context": "https://schema.org",
  "@type": "Dataset",
  "name": "Travel eSIM local IP breakout and latency directory — 4-provider routing matrix",
  "description": "Normalized ICMP, exit IP geography, routing-server hints, and breakout class for Airalo, Saily, Nomad, and Ubigi from Network Scrutiny field audits, as of June 2026.",
  "creator": { "@type": "Organization", "name": "Network Scrutiny" },
  "datePublished": "2026-06-22",
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "isAccessibleForFree": true,
  "inLanguage": "en-US",
  "url": "https://networkscrutiny.com/guides/travel-esim-latency-local-ip-breakout-directory/#directory-matrix"
}

---

How to read routing servers and breakout class

Local IP breakout (LBO) means your packet gateway (PGW)—the mobile core node that hands user traffic to the public internet—injects packets inside or near your physical country. International hub breakout (IHBO) tunnels packets to a distant aggregator routing server—often Western Europe or the brand's home region—before the wider internet sees them.

Radio quality (bars, 5G icon) only describes the link to the visited tower. Travel eSIM latency tests must inspect user-plane egress:

1. Public IP country and ASN (ipinfo.io/json on cellular only).
2. ICMP median (30 probes to 8.8.8.8 and a regional target when available).
3. Traceroute hostnames on early hops—continental keywords (ams, fra, sin) are hints, not proof.
4. Voice trial—60 seconds of WhatsApp or FaceTime audio; mouth-to-ear delay is ground truth.

Retail brands inherit whatever PGW placement their wholesale deal negotiated. Checkout copy does not disclose routing servers; your phone does, after activation. For the full technical primer, see travel eSIM latency: local breakout vs routing.

---

Provider routing snapshots (linked deep dives)

Nomad — regional home network narrative holds in US audit

Nomad's consumer blog argues travel eSIMs route through a home network before the internet, and claims Nomad keeps that home in the same region as the destination¹. Our May 2026 US matrix supports that for the 10 GB / 30-day SKU: US exit IPs and 26–31 ms medians on T-Mobile/AT&T attaches in three cities. Verdict for US breakout: default pick when you need US IP fidelity and flexible GB tiers.

→ Full methodology: Saily vs Nomad US breakout audit

Saily — security bundle, EU hub default on USA SKU

Saily routes through 1Global infrastructure; our 6/6 US sessions on the standard 5 GB United States listing showed Netherlands exit and 109–118 ms ICMP despite T-Mobile 5G. Optional virtual location changes apparent geography like a VPN overlay—roughly 15–25 ms extra ICMP in a single NYC afternoon sample (May 2026). Verdict: wrong primary line for US-local breakout; acceptable when privacy bundling beats latency.

Airalo — marketplace; destination matters more than brand

Airalo sells destination-specific bundles on varied host operators². Our June 10, 2026 Airalo France 3 GB sample in Paris showed FR exit and 31 ms median—classic LBO. US SKUs are not in the May US audit; two travelers both "on Airalo" can see opposite routing-server outcomes. Verdict: run the paired protocol in Airalo vs Ubigi latency test after every install.

Ubigi — unified brand, partner-specific routing servers

Ubigi markets one global identity³, but breakout follows per-country wholesale deals—same verification burden as Airalo. Network Scrutiny has no published US numeric row for Ubigi as of June 22, 2026. Anecdotally, forum reports mix praise for EU city attaches with complaints about distant egress on specific corridors—I have not tested every Ubigi SKU myself.

---

Pros / cons by breakout goal (US travelers)

Goal	Nomad	Saily	Airalo	Ubigi
US IP on US soil	✅ Measured LBO	❌ IHBO in audit	⚠️ Verify SKU	⚠️ Verify SKU
Lowest measured US ICMP	✅ ~26–31 ms	❌ ~109–118 ms	—	—
Security extras	Data-only	Malware block + VPN-style virtual location	Marketplace simplicity	Subscription model
Predictability	High in US audit	High (always hub in our US sample)	Low—per destination	Medium—verify per country

"Travel eSIMs will typically route your data back to the home country of that eSIM before you get connected to the internet… Nomad ensures that the eSIMs provided for each destination has its home network located in the same region."

---

Steel-man: why hub routing might still be fine

Defenders of Saily-class and some Airalo hub paths make a coherent case: IHBO is industry-normal for roaming aggregators; centralized routing servers simplify fraud controls and policy enforcement. If Daniel, a Brooklyn photographer, only uploads RAW files overnight and reads offline maps, 118 ms RTT is irrelevant. If he prefers EU-anchored privacy framing, a Netherlands exit may be a feature. Saily bundles ad blocking and malware protection Nomad does not include at the same tier⁴.

Rebuttal: The search intent behind travel esim local ip breakout is technical. If you are in the US and need US IP fidelity—for payroll VPN, state portals, sports blackouts, or sub-50 ms RTT to us-east-1—paying for IHBO is the wrong tool. The directory ranks on measured egress and ICMP; use hub-routed profiles when security bundling beats latency, not when breakout does.

---

Decision flow: which profile carries default data?

Start: Travel eSIM installed; I care about latency
  │
  ├─ Physically in the United States?
  │     ├─ Need US IP? → ipinfo on cellular
  │     │       ├─ US + ICMP < 50 ms → Keep (Nomad class per directory)
  │     │       └─ Foreign IP or ICMP > 80 ms → Switch; Saily USA failed 6/6 in audit
  │     └─ US IP not required → Hub OK; watch voice RTT
  │
  ├─ Abroad (EU, APAC, etc.)?
  │     ├─ Run directory protocol; compare to Airalo/Ubigi paired test
  │     └─ France Airalo sample = LBO; do not assume all SKUs match
  │
  └─ Latency-sensitive live calls?
        ├─ Yes → Require exit IP match + median ICMP < 50 ms in-region
        └─ No → Throughput test sufficient after IP check

---

Worked example: Alicia, fintech PM in Manhattan

Alicia flies London → JFK with Saily 5 GB United States already installed from a EU trip. Cellular-only ipinfo.io: NL, median 121 ms to 8.8.8.8, traceroute hop 2 shows ams pattern—matches directory row Saily / NYC / IHBO. Her company's VPN flags non-US egress. She buys Nomad 10 GB US before leaving the terminal: US exit, 27 ms median. She keeps Saily for Berlin weeks where EU hub routing hurts less. Dual-SIM hygiene: iPhone default data line.

---

Worked example: Tom, road-trip dev testing Airalo France

Tom lands at CDG with Airalo France 3 GB and Visible primary. He sets Airalo as default data, disables Wi‑Fi, loads ipinfo.io/json: FR, Bouygues-class ASN, 31 ms median ICMP—directory LBO row confirmed. He runs a six-hop traceroute via he.net Network Tools; Paris-metro hostnames by hop 3. Verdict: safe for client standup from the taxi. He would not assume his Airalo US profile from a prior trip behaves the same—marketplace SKUs need a fresh row in the directory.

---

Run your own audit (reproduce directory rows)

Declared inline: Every measurement in this directory used the protocol documented in How to run a travel eSIM traceroute & latency audit:

1. Cellular-only — Wi‑Fi and system VPNs off.
2. Default mobile data on the travel line.
3. curl -s https://ipinfo.io/json or Safari equivalent.
4. ping -c 30 8.8.8.8 (Termux on Android; he.net or iNetTools on iOS).
5. traceroute -m 8 8.8.8.8 where policy allows.
6. 60-second voice call on cellular.

Your mileage will vary depending on tower load, ICMP deprioritization, and wholesale contract changes—re-verify after every profile reinstall.

---

Verdict

For travel esim local ip breakout while you are physically in the United States, Nomad is the defensible default as of June 22, 2026—it delivered US exit IPs and ~26–31 ms class medians in our multi-city audit. Saily USA is the wrong primary data line for US-local breakout: treat it as a privacy wrapper with 1Global EU hub egress. Airalo and Ubigi require per-SKU verification; our France Airalo sample broke out locally, but US rows are not in the May audit—use this directory as a starting map, not a substitute for your own ipinfo check at the airport.

Wholesale contracts rotate quarterly. I would not trust any checkout screenshot that lacks an IP check—the matrix above is already perishable.

---

Disclaimer

Network Scrutiny is not affiliated with Airalo, Saily, Nomad, or Ubigi. Breakout paths change when aggregators renegotiate interconnect; replicate our protocol on your hardware after major app updates. Pricing cited from public plan pages on May 20–21 and June 10–11, 2026. ICMP and IP geolocation can mislead individually—use paired evidence.

Footnotes

1. Nomad eSIM blog on data roaming and regional home networks, accessed June 22, 2026. ↩

2. Airalo consumer materials describe marketplace coverage rather than per-SKU breakout engineering. ↩

3. Ubigi markets global travel data under a unified brand; technical routing remains partner-specific per destination. ↩

4. Saily Help — Virtual location feature documentation, accessed June 22, 2026. ↩