Travel Connectivity
Travel eSIM Latency Benchmark: Local IP Breakout Test
Master latency benchmark for US travelers comparing Airalo, Ubigi, Saily, Nomad, and Jetpac: measured exit IP geography, median ICMP, routing class (local breakout vs hub), and field methodology so you can avoid high-ping tromboned paths before VoIP or banking.
- Updated
- 2026-07-03
- Reading time
- 16 min
TL;DR
Travel eSIM latency is dominated by where packets exit onto the internet—not by 5G bars. In Network Scrutiny's July 2026 master benchmark across five major brands, Nomad and Jetpac US SKUs delivered US exit IPs with ~26–35 ms median ICMP; Airalo and Ubigi US plans joined them with local breakout in our NYC spot checks; Saily USA still hairpinned through a European hub (~112 ms) in every session. Verify egress after every install.
- Local IP breakout (LBO) keeps median ICMP under ~50 ms in-region; international hub breakout (IHBO) adds 80–110 ms even when local 5G looks excellent.
- As of July 3, 2026, Nomad and Jetpac lead measured US latency; Airalo and Ubigi US SKUs achieved LBO in our July NYC checks but remain marketplace/partner-variable—re-test per SKU.
- Saily USA failed US IP breakout in 6/6 May 2026 sessions and 3/3 July 2026 re-checks; treat it as a privacy bundle, not a low-ping US egress product.
- The benchmark protocol is cellular-only: ipinfo.io JSON, 30 ICMP probes, optional six-hop traceroute, 60-second voice trial—same sequence for every provider.
Travel eSIM latency for US travelers comes down to one measurable question: does your prepaid profile inject traffic onto the public internet near you, or trombone packets through a distant packet gateway first? In Network Scrutiny's July 2026 master benchmark, Nomad and Jetpac US SKUs consistently delivered US exit IPs with ~26–35 ms median ICMP; Airalo and Ubigi US plans achieved local breakout in our NYC spot checks (~32–36 ms); Saily USA still routed through a European hub at ~112 ms despite full T-Mobile 5G bars. Checkout pages never disclose that split—you only see it after a cellular-only IP and ping audit.
Stat: Hub-routed Saily sessions averaged 86 ms higher RTT to
8.8.8.8than local-breakout Nomad/Jetpac sessions at the same street address (N=21 paired US samples, May–July 2026). Saily USA never showed a US exit IP in 9/9 tests. Source: Network Scrutiny field log; methodology below.
Original research: five-provider latency benchmark (July 2026)
We unified Airalo, Ubigi, Saily, Nomad, and Jetpac into one comparable matrix on July 3, 2026, normalizing rows from our May 15–22, 2026 three-metro US audit, June 10, 2026 Paris Airalo spot check, and July 1–2, 2026 NYC paired session that finally logged controlled US probes for Airalo and Ubigi. Hardware: unlocked iPhone 15 and Pixel 8. Posture: cellular-only, travel line as default mobile data. Each row records exit IP country via ipinfo.io/json, ASN, median of 30 ICMP probes to 8.8.8.8, median to a US-East cloud latency host where available, and breakout class LBO (local) vs IHBO (international hub).
| Provider | SKU / market | Metro | Exit IP | Median RTT 8.8.8.8 | US-East probe | Breakout | Audit date |
|---|---|---|---|---|---|---|---|
| Nomad | 10 GB / US | NYC | US | 26 ms | 24 ms | LBO | 2026-05-16 |
| Nomad | 10 GB / US | Chicago | US | 31 ms | 28 ms | LBO | 2026-05-18 |
| Nomad | 10 GB / US | San Francisco | US | 29 ms | 27 ms | LBO | 2026-05-20 |
| Jetpac | 5 GB / US | NYC | US | 33 ms | 30 ms | LBO | 2026-05-17 |
| Jetpac | 5 GB / US | Chicago | US | 47 ms¹ | 41 ms | LBO | 2026-05-19 |
| Jetpac | 5 GB / US | San Francisco | US | 35 ms | 32 ms | LBO | 2026-05-21 |
| Airalo | 5 GB / US | NYC | US | 32 ms | 29 ms | LBO | 2026-07-02 |
| Ubigi | 10 GB / US | NYC | US | 36 ms | 33 ms | LBO | 2026-07-02 |
| Saily | 5 GB / US | NYC | NL | 118 ms | 121 ms | IHBO | 2026-05-16 |
| Saily | 5 GB / US | Chicago | NL | 112 ms | 115 ms | IHBO | 2026-05-18 |
| Saily | 5 GB / US | San Francisco | NL | 109 ms | 114 ms | IHBO | 2026-05-20 |
| Saily | 5 GB / US | NYC (re-check) | NL | 115 ms | 118 ms | IHBO | 2026-07-01 |
| Airalo | 3 GB / France | Paris | FR | 31 ms | — | LBO | 2026-06-10 |
¹ Chicago Jetpac/AT&T attach showed 95th-percentile ICMP spikes to 68 ms—US exit IP, capacity jitter not trombone (May 19, 4:30 PM CDT).
Pricing checked July 1, 2026: Nomad 10 GB US ≈ $20; Jetpac 5 GB US ≈ $14 promo; Airalo US 5 GB ≈ $16; Ubigi US 10 GB ≈ $19; Saily 5 GB US ≈ $18—verify live checkout before purchase.
Dataset (Schema.org): name Travel eSIM latency benchmark — 5-provider local IP breakout matrix; datePublished 2026-07-03; license CC BY 4.0; inLanguage en-US.
{
"@context": "https://schema.org",
"@type": "Dataset",
"name": "Travel eSIM latency benchmark — 5-provider local IP breakout matrix",
"description": "Median ICMP, exit IP geography, and breakout class (LBO vs IHBO) for Airalo, Ubigi, Saily, Nomad, and Jetpac from Network Scrutiny field audits, as of July 2026.",
"creator": { "@type": "Organization", "name": "Network Scrutiny" },
"datePublished": "2026-07-03",
"license": "https://creativecommons.org/licenses/by/4.0/",
"isAccessibleForFree": true,
"inLanguage": "en-US",
"url": "https://networkscrutiny.com/guides/travel-esim-latency-benchmark-local-ip-breakout-test/#benchmark-matrix"
}
What local IP breakout means in this benchmark
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—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:
- Public IP country and ASN (
ipinfo.io/jsonon cellular only). - ICMP median (30 probes to
8.8.8.8and a regional target when available). - Traceroute hostnames on early hops—continental keywords (
ams,fra,sin) are hints, not proof. - 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. For the full technical primer, see travel eSIM latency: local breakout vs routing.
Field methodology (reproduce our numbers)
Declared inline: We compared five prepaid travel eSIM brands between May 15 and July 2, 2026 using the same protocol as our Saily/Nomad/Jetpac US audit and Airalo vs Ubigi paired test:
- Install profile; keep data roaming on.
- Force cellular-only; disable Wi‑Fi and system VPNs.
- Set the test profile as default mobile data.
- Capture PLMN, IP country/city/ASN (
curl -s https://ipinfo.io/jsonin Termux or Safari). - Run 30 ICMP probes to
8.8.8.8and a US-East cloud latency host; record median and 95th percentile. - Optional: traceroute first six hops—see travel eSIM traceroute audit.
- Application ground truth: 60-second WhatsApp voice on cellular; note mouth-to-ear delay.
Anecdotally, ICMP is deprioritized on some US bearers; if ping looks fine but voice stutters, trust step 7 over step 5.
Where I'm less sure: Airalo and Ubigi US breakout can differ by underlying PLMN and wholesale rotation quarterly. Our July NYC row is one controlled snapshot—not a perpetual SLA. Re-test after every profile install.
Provider results (five-brand snapshot)
Nomad — lowest measured US latency
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 destination1. Our May 2026 three-metro matrix supports that for the 10 GB / 30-day US SKU: US exit IPs and 26–31 ms medians on T-Mobile/AT&T attaches. Verdict: default pick when US IP fidelity and flexible GB tiers matter most.
Jetpac — local US breakout, short-trip pricing
Jetpac's Singapore HQ does not dictate US egress—US plans in our audit behaved like Transatel-class US breakout, not APAC trombone. Chicago AT&T showed higher jitter but remained LBO. Verdict: strong for short US visits and hotspot-heavy road trips; compare promo pricing against Nomad for longer stays.
Airalo — marketplace; US SKU passed July spot check
Airalo sells destination-specific bundles on varied host operators2. Our June 2026 Airalo France 3 GB sample in Paris showed FR exit and 31 ms median. The July 2, 2026 Airalo US 5 GB NYC sample showed US exit at 32 ms—but marketplace SKUs can diverge. Verdict: viable US latency when your specific SKU passes ipinfo; never assume from brand name alone.
Ubigi — unified brand, partner-specific routing
Ubigi markets one global identity3, but breakout follows per-country wholesale deals. Our July 2, 2026 Ubigi US 10 GB NYC session showed US exit at 36 ms—within noise of Airalo on the same corner. I have not tested every Ubigi corridor; forum reports still mix praise and distant-egress complaints abroad.
Saily — security bundle, EU hub default on USA SKU
Saily routes through 1Global infrastructure. Our 9/9 US sessions on the standard 5 GB United States listing showed Netherlands exit and 109–118 ms ICMP despite T-Mobile 5G—including July 1, 2026 re-checks after a Saily app update. Optional virtual location changes apparent geography like a VPN overlay. Verdict: wrong primary line for US-local breakout.
Worked examples
Marcus, product manager (JFK → Manhattan)
Marcus lands from Berlin for a two-week US sprint. He activates Saily 5 GB first. ipinfo.io shows Netherlands, ICMP median 121 ms. His bank's fraud SMS fires. He switches default data to Nomad 10 GB the same afternoon—US exit, 27 ms median, Google Meet standup on cellular in Hudson Yards is usable. Marcus keeps Nomad for US weeks and relegates Saily to EU trips where hub routing hurts less.
Priya, consultant (NYC → Paris)
Priya carries Airalo France 3 GB and Ubigi Europe 10 GB for a client week. In Paris CDG, Airalo shows FR exit, 31 ms ICMP—classic LBO. Ubigi on the same corner shows FR exit, 34 ms. Both beat her Mint Mobile roaming add-on on latency to EU SaaS nodes. She runs the paired protocol from our Airalo vs Ubigi guide before each trip because wholesale paths rotate.
Pros / cons by breakout goal (US travelers)
| Goal | Nomad | Jetpac | Airalo | Ubigi | Saily |
|---|---|---|---|---|---|
| US IP on US soil | ✅ Measured LBO | ✅ Measured LBO | ✅ July NYC LBO | ✅ July NYC LBO | ❌ IHBO 9/9 |
| Lowest measured US ICMP | ✅ ~26–31 ms | ✅ ~33–35 ms | ~32 ms (1 metro) | ~36 ms (1 metro) | ❌ ~109–118 ms |
| Predictability | High in audit | High in audit | Low—per SKU | Medium—verify | High (always hub US) |
| Security extras | Data-only | Lounge perks | Marketplace simplicity | Subscription model | Malware block + virtual location |
"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 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, 115 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 that Nomad does not include at the same tier4.
Rebuttal: The search intent behind travel esim latency 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. This benchmark 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/Jetpac/Airalo/Ubigi class)
│ │ └─ Foreign IP or ICMP > 80 ms → Switch; Saily USA failed 9/9
│ └─ US IP not required → Hub OK; watch voice RTT
│
├─ Abroad (EU, APAC, etc.)?
│ ├─ Run benchmark protocol; compare Airalo vs 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
Working checklist before you commit gigabytes
- Buy the United States SKU—not a global bundle—when US breakout is the goal.
- After install, confirm exit IP country before you leave airport Wi‑Fi.
- Compare Nomad vs Jetpac pricing for trip length (July 2026: Nomad 10 GB ≈ $20; Jetpac 5 GB ≈ $14 promo).
- If you choose Airalo or Ubigi, run the paired protocol—marketplace routing rotates.
- If Saily is installed, test with virtual location off first; document overhead if you turn it on.
- Cross-read best travel eSIMs for US travelers for plan economics and the breakout directory for per-provider deep dives.
Verdict
For travel eSIM latency while you are physically in the United States, Nomad is the defensible default as of July 3, 2026—US exit IPs and ~26–31 ms class medians across three metros. Jetpac ties within noise for short trips and hotspot use. Airalo and Ubigi US SKUs passed our July 2, 2026 NYC breakout test but demand per-SKU re-verification. Saily USA is the wrong primary data line for US-local breakout: treat it as a privacy wrapper with 1Global EU hub egress.
I would not trust any travel eSIM checkout screenshot that lacks an IP check—wholesale contracts rotate quarterly, and the matrix above is already perishable.
Disclaimer
Network Scrutiny is not affiliated with Airalo, Ubigi, Saily, Nomad, or Jetpac. 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, June 10–11, and July 1–2, 2026. ICMP and IP geolocation can mislead individually—use paired evidence.
Footnotes
-
Nomad eSIM blog on data roaming and regional home networks, accessed July 3, 2026. ↩
-
Airalo — How Airalo works, accessed July 3, 2026. ↩
-
Ubigi markets global travel data under a unified brand; technical routing remains partner-specific per destination. ↩
-
Saily Help — Virtual location feature documentation, accessed July 3, 2026. ↩
FAQ
Short answers; details are in the article above.
- In Network Scrutiny's July 2026 master benchmark, Nomad 10 GB US SKUs delivered the lowest median ICMP (~26–31 ms to 8.8.8.8) with US exit IPs across NYC, Chicago, and San Francisco. Jetpac US plans tied within noise on T-Mobile attaches (~33–35 ms). Airalo and Ubigi US SKUs showed local breakout in our July NYC spot checks (~32–36 ms) but can vary by underlying wholesale partner—verify after install.
- Saily routes consumer traffic through 1Global's European hub. In our audits, the USA SKU presented Netherlands exit geography and 109–118 ms median ICMP despite T-Mobile 5G bars. That is intentional hub routing for policy enforcement—not a radio defect.
- No. Airalo is a marketplace—each destination SKU rides a different host operator and wholesale deal. Our Airalo France sample broke out locally in Paris (31 ms), and our July 2026 Airalo US 5 GB sample showed US egress in NYC—but two travelers both on Airalo can see opposite outcomes. Run the benchmark protocol after every activation.
- Disable Wi-Fi and VPN, set the travel line as default cellular data, load ipinfo.io/json, run 30 ICMP probes to 8.8.8.8, note median RTT and exit country. If country mismatches your location and RTT exceeds ~80 ms in-region, assume hub routing. Full steps are in our traceroute and latency audit guide.
- Neither brand wins universally. In our July 2026 NYC paired test, Ubigi US 10 GB median ICMP was 36 ms versus Airalo US 5 GB at 32 ms—within measurement noise on the same corner. Abroad, both require per-country verification; see our Airalo vs Ubigi paired protocol for fair comparisons.