Travel eSIM Latency Audit: Saily vs Nomad vs Jetpac

A travel eSIM latency test on US soil comes down to one question: where do your packets actually join the public internet? In Network Scrutiny's May–July 2026 field audit of Saily, Nomad, and Jetpac United States SKUs, Nomad and Jetpac consistently delivered US exit IPs with ~26–35 ms median ICMP to 8.8.8.8, while Saily's USA plan still hairpinned through 1Global's European hub at ~109–118 ms despite full T-Mobile 5G bars. That gap is the difference between usable Zoom on cellular and a banking app that flags your login.

Stat: In our audit, hub-routed Saily sessions averaged 94 ms higher RTT to ec2.us-east-1.amazonaws.com ping targets than Nomad/Jetpac local-breakout sessions at the same street address (N=18 paired samples, May 2026). Saily USA never showed a US exit IP in 9/9 sessions through July 2, 2026. Source: Network Scrutiny field log; methodology below.

This audit feeds our consolidated Travel eSIM Latency & Local IP Breakout Directory and the broader latency benchmark that added Airalo and Ubigi in July 2026.

---

Original research: US breakout latency matrix (May–July 2026)

We executed this audit between May 15 and July 2, 2026 on unlocked iPhone 15 and Pixel 8 hardware, cellular data only (Wi‑Fi and VPN off), at outdoor spots within ~500 m of carrier macro sites in Manhattan (NYC), The Loop (Chicago), and SoMa (San Francisco). Each provider used its publicly sold United States travel SKU: Saily 5 GB / 30 days (pricing checked on Saily's site July 8, 2026), Nomad 10 GB / 30 days (July 8, 2026), Jetpac 5 GB / 15 days (July 8, 2026). We recorded serving PLMN where iOS/Android exposed it, exit IP country/city via ipinfo.io, ASN, median of 30 ICMP probes to 8.8.8.8, median to an AWS us-east-1 latency endpoint, and optional six-hop traceroute where OS policy allowed.

Provider / SKU	Metro	Serving PLMN (observed)	Exit IP country	Median RTT 8.8.8.8	Median RTT US-East probe	Breakout class¹	Source
Saily 5 GB US	NYC	T-Mobile 310-260	NL (Amsterdam area)	118 ms	121 ms	IHBO / hub	NS audit 2026-05-16
Saily 5 GB US	Chicago	T-Mobile 310-260	NL	112 ms	115 ms	IHBO / hub	NS audit 2026-05-18
Saily 5 GB US	San Francisco	T-Mobile 310-260	NL	109 ms	114 ms	IHBO / hub	NS audit 2026-05-20
Saily 5 GB US	NYC (re-check)	T-Mobile 310-260	NL	112 ms	115 ms	IHBO / hub	NS audit 2026-07-02
Nomad 10 GB US	NYC	T-Mobile 310-260	US	26 ms	24 ms	LBO (local)	NS audit 2026-05-16
Nomad 10 GB US	Chicago	AT&T 310-410	US	31 ms	28 ms	LBO (local)	NS audit 2026-05-18
Nomad 10 GB US	San Francisco	T-Mobile 310-260	US	29 ms	27 ms	LBO (local)	NS audit 2026-05-20
Jetpac 5 GB US	NYC	T-Mobile 310-260	US	33 ms	30 ms	LBO (local)	NS audit 2026-05-17
Jetpac 5 GB US	Chicago	AT&T 310-410	US	47 ms²	41 ms	LBO (local)	NS audit 2026-05-19
Jetpac 5 GB US	San Francisco	T-Mobile 310-260	US	35 ms	32 ms	LBO (local)	NS audit 2026-05-21

¹ LBO = local breakout (traffic enters the internet in the US). IHBO = international hub breakout (traffic leaves via a distant aggregator hub). Labels follow GSMA-adjacent community taxonomy¹.

² Chicago Jetpac/AT&T session showed 95th-percentile ICMP spikes to 68 ms—still US exit IP, but worse jitter than Nomad on the same corner (May 19, 4:30 PM CDT, stadium-adjacent crowd).

Dataset (Schema.org): name US travel eSIM breakout latency matrix — Saily vs Nomad vs Jetpac; datePublished 2026-07-09; license CC BY 4.0; URL fragment #breakout-matrix; inLanguage en-US.

{
  "@context": "https://schema.org",
  "@type": "Dataset",
  "name": "US travel eSIM breakout latency matrix — Saily vs Nomad vs Jetpac",
  "description": "Measured exit IP geography, median ICMP, and breakout class for Saily, Nomad, and Jetpac United States travel eSIM SKUs across NYC, Chicago, and San Francisco, May 15–July 2, 2026.",
  "creator": { "@type": "Organization", "name": "Network Scrutiny" },
  "datePublished": "2026-07-09",
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "isAccessibleForFree": true,
  "inLanguage": "en-US",
  "url": "https://networkscrutiny.com/guides/travel-esim-latency-audit-saily-nomad-jetpac-us-breakout/#breakout-matrix"
}

---

What local IP breakout means on US soil

Local IP breakout (visited-country breakout) means your handset may attach to T-Mobile or AT&T in Chicago, but the decisive question is where the mobile core injects you into the public internet. If that point is in Amsterdam or Singapore, every US website sees a foreign IP and your packets pay for an extra round trip—even though your radio link is domestic.

Retail travel eSIM brands rarely publish breakout diagrams; routing is negotiated between wholesale aggregators (for example 1Global, Transatel) and host operators¹. Saily's consumer stack is tied to 1Global (Nord Security's travel eSIM), which multiple independent reviewers document as Netherlands-anchored hub routing². Nomad's consumer blog argues for regional home networks aligned with the destination to keep hops short³. Jetpac (Singapore HQ) sells US plans on Transatel-class US infrastructure; HQ location ≠ egress location, which is why we measured Jetpac separately instead of assuming Asian trombone.

---

Traceroute hints: what we saw beyond ping

ICMP alone cannot prove routing, but traceroute hop hostnames are directional when paired with exit IP geography. On Saily USA sessions, hop 3–4 often resolved to Amsterdam-class aggregator names before traffic reached US-facing CDN edges—a pattern consistent with IHBO even when the serving PLMN was domestic T-Mobile. On Nomad and Jetpac US sessions, hop 3 typically showed US-metro peering (Chicago, Ashburn, or Bay Area hostnames) matching the ipinfo.io country field.

Where I am less sure: iOS and Android increasingly block or sanitize ICMP traceroute on cellular bearers; we treat hop names as corroboration, not proof. When traceroute is unavailable, the paired IP country + median RTT test still separates LBO from IHBO in practice. Full six-hop protocol: travel eSIM traceroute latency audit.

---

Provider architecture (what we expected vs what we measured)

Saily — security bundle, EU hub default

Saily markets malware blocking, optional virtual location, and Nord-adjacent privacy⁴. Architecturally, 1Global hub routing is a feature for consistent policy enforcement—not a bug—but it conflicts with US-local breakout goals. Our nine US sessions matched third-party Vietnam→Romania anecdotes in spirit: you are on US radio, EU internet.

Where I am less sure: whether every Saily US SKU always maps to the same 1Global egress POP; we only bought the standard 5 GB / 30-day listing in May 2026 and re-checked it in NYC on July 2, 2026. A wholesale change could localize tomorrow—re-test, do not trust this table forever.

Nomad — regional home network narrative holds in our sample

Nomad's explainer acknowledges that many travel eSIMs route through a home network before the internet, then claims Nomad keeps that home in the same region as the destination to limit latency³. Our US exit IPs and sub-40 ms regional probes support that story for the 10 GB SKU—at least on T-Mobile/AT&T attaches in three cities.

Jetpac — US performance when the SKU is US, not "Singapore routing"

Jetpac's brand is Singapore-based, but US plans in our audit behaved like US breakout profiles (Transatel-style US core), not APAC trombone. That matches city speed reports in trade reviews for US road trips, and differs from Jetpac's infamous Vietnam→US trombone anecdotes abroad⁵. Lesson: evaluate the SKU country, not the company's headquarters.

---

Field methodology (reproduce our numbers)

Declared inline: We compared three prepaid United States travel eSIMs on May 15–July 2, 2026 using the same protocol as our travel eSIM latency primer and Airalo vs Ubigi latency protocol:

1. Install profile; keep data roaming on (required for travel eSIM attach per Nomad's documentation³).
2. Force cellular-only; disable Wi‑Fi and system VPNs.
3. Set the test profile as default mobile data (iOS: Settings → Cellular → Cellular Data).
4. Capture PLMN, IP country/city/ASN (curl -s https://ipinfo.io/json in Termux or Safari).
5. Run 30 ICMP probes to 8.8.8.8 and a US-East cloud latency host; record median and 95th percentile.
6. Optional: traceroute first six hops where OS policy allows—look for transatlantic hostnames (directional hint only).
7. 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.

Worked example: Marcus, product manager in NYC (JFK → Manhattan)

Marcus lands from Berlin for a two-week US sprint. He activates Saily 5 GB first (already installed from a EU trip). ipinfo.io shows Netherlands, ICMP median 121 ms to 8.8.8.8. His bank's fraud SMS fires. He switches default data to Nomad 10 GB the same afternoon—US exit, 27 ms median, voice standup on Google Meet is usable on cellular in Hudson Yards. Marcus keeps Nomad for US weeks and relegates Saily to EU trips where hub routing is less harmful.

Worked example: Elena, Austin remote worker on I-35

Elena road-trips Chicago → Minneapolis with Jetpac 5 GB on a Pixel 8. T-Mobile attach in Madison, WI shows US IP, 38 ms ICMP. Downtown Chicago AT&T attach on the same SKU jumps to 47 ms median with brief spikes to 68 ms during rush hour—still local breakout, but capacity-limited jitter, not trombone. She would not switch providers for that alone; she would switch if IP country flipped to SG or NL (it did not through July 2026).

---

Pros / cons (US breakout lens)

Saily (USA SKU)	Nomad (USA SKU)	Jetpac (USA SKU)
Pros: Built-in security extras; virtual location for appearance control; polished Nord-adjacent UX	Pros: US exit IP in our audit; flexible GB tiers; straightforward app	Pros: US exit IP; strong short-trip pricing; hotspot-friendly; SmartDelay lounge perk on some packs
Cons: EU hub routing in 9/9 tests; higher RTT to US SaaS; banking/geo friction	Cons: Data-only; no published breakout SLA; AT&T vs T-Mobile variance by city	Cons: Jitter on some AT&T attaches; brand less known; voice/SMS not native PSTN

"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."

"The country on the eSIM package tells you where you have coverage—not where your traffic exits. The only way to know is to check your public IP after activation."

---

Steel-man: why Saily might still be the right buy

Saily's defenders have a coherent case: hub routing is industry-normal for roaming-class products; Saily bundles ad blocking, malware protection, and optional virtual location that Nomad and Jetpac do not include at the same tier. If Elena mostly reads email and offline maps, 118 ms RTT is irrelevant. If Marcus needs EU-like privacy policy and distrusts US surveillance framing, a Netherlands exit may be a feature, not a defect. Saily's own help center positions virtual location as deliberate control over apparent geography⁴—an honest workaround when US IP is not the goal.

Rebuttal: The search intent behind a travel eSIM latency test is technical, not ideological. If you are in the US and need US IP fidelity—for banking, state government portals, sports blackouts, or sub-50 ms RTT to us-east-1—paying Saily's premium to trombone through Amsterdam is the wrong tool. Nomad or Jetpac won our May–July 2026 audit on the metric this page promises; use Saily when security bundling beats latency, not when breakout does.

---

Decision flow (which profile should carry default data?)

Start: I am physically in the US with a travel eSIM installed
  │
  ├─ Need US IP for apps/banking/streaming rights?
  │     ├─ Yes → Run ipinfo on cellular
  │     │         ├─ Country = US → Keep profile (Nomad/Jetpac class)
  │     │         └─ Country ≠ US → Switch provider or SKU; do not trust storefront name
  │     └─ No → Hub routing OK → Saily class acceptable; watch RTT for live calls
  │
  └─ Latency-sensitive live calls on cellular?
        ├─ Yes → Require US exit + median ICMP < 50 ms to 8.8.8.8
        └─ No → Throughput-only tests sufficient

---

Working checklist before you commit gigabytes

1. Buy the United States SKU—not a global bundle—when US breakout is the goal.
2. After install, confirm exit IP country before you leave airport Wi‑Fi.
3. Compare Nomad vs Jetpac pricing for your trip length on each site (July 8, 2026 checks: Nomad 10 GB ≈ $20 list; Jetpac 5 GB short trips often under $15 promo—verify live checkout).
4. If Saily is already installed, test with virtual location off first; document overhead if you turn it on.
5. Cross-read best travel eSIMs for US travelers for plan economics and travel eSIM unlimited throttling for FUP traps.
6. For dual-SIM hygiene, see iPhone dual-SIM default data line.

---

Verdict

For a travel eSIM latency test while you are actually in the United States, Nomad and Jetpac are the defensible defaults as of July 9, 2026—both delivered US exit IPs and ~25–35 ms class medians to public DNS in our audit. Jetpac wins short US visits and hotspot-heavy road trips; Nomad wins if you want larger buckets without Jetpac's lounge-centric upsells. Saily is the wrong primary data line for US-local breakout: treat it as a privacy and security wrapper that intentionally centralizes egress in 1Global's EU hub, and only keep it when that tradeoff helps you more than it hurts.

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 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 July 8, 2026. ICMP and IP geolocation can mislead individually—use paired evidence.

Footnotes

1. Julian Hart, "eSIM Routing Explained," DEV Community (2026)—hub vs local breakout taxonomy and ipinfo.io verification pattern. ↩ ↩²

2. Independent field reviews (e.g., eSIMS.io Saily Vietnam test; Defy Life Saily 2026 review) document 1Global / Netherlands egress; our US audit corroborates the same pattern on the USA SKU. ↩

3. Nomad eSIM blog on data roaming and regional home networks, accessed July 8, 2026. ↩ ↩² ↩³

4. Saily Help — Virtual location feature documentation, accessed July 8, 2026. ↩ ↩²

5. eSIMS.io Jetpac Vietnam review documents US trombone from Southeast Asia—the inverse failure mode of our US-local Jetpac results. ↩