Field note: the first two connection tests

Field note: the first two connection tests

Illustrative case, not a reported field measurement: At 9:00 a.m., a traveler using Zebra eSIM joined an airport Wi-Fi network and completed its sign-in page. The traveler then turned Wi-Fi off, reducing the number of active Wi-Fi connections from one to zero, and loaded a page over the travel data line. The note read: “Wi-Fi sign-in completed; cellular test completed with Wi-Fi off; home-line roaming checked.”

That record separates three observations that are easy to confuse: joining a Wi-Fi network, gaining internet access through its sign-in page, and verifying cellular data. A Wi-Fi icon alone does not establish that the airport portal has granted access. Likewise, a page that loads while both Wi-Fi and cellular are enabled does not by itself prove which path carried the traffic.

The aim during the first hour is not to guarantee a charge-free trip or the fastest available connection. It is to identify the intended data line, test each path under conditions that make the result interpretable, and record any failure before relying on the connection.

Before joining the airport network

Keep the travel eSIM installed and enabled, and identify the phone’s two lines by their labels. On a supported dual-SIM phone, select the travel eSIM as the cellular or mobile-data line. If the phone offers automatic cellular-data switching between lines, turn it off for this check. Menu names and available controls vary by device, carrier, and software version.

Check the home line’s roaming setting separately. Selecting the travel eSIM for data does not necessarily disable the home line or prevent charges for calls and texts. Turning off data roaming on the home line can reduce the risk of unintended roaming data use, but it is not a universal guarantee against every kind of charge. If the traveler must keep the home line active for verification messages or calls, check the carrier’s applicable roaming terms.

The travel eSIM may itself require data roaming to work under its plan. Confirm its instructions rather than applying the home-line setting indiscriminately. Also check whether installation or activation requires connectivity before disabling a working connection.

Airport Wi-Fi: join, sign in, then verify

Select the airport’s intended Wi-Fi network and wait for the sign-in page. Follow the displayed terms or access steps. If the portal does not appear, open a browser and try loading a page; some networks redirect the request to their sign-in screen.

For a clearer Wi-Fi-only test, temporarily turn off cellular data after noting the intended travel-data line. Then attempt to load a page over the airport network. Record the result as one of the following:

  • Connected and signed in: The portal was completed and a page loaded with cellular data off.
  • Joined, but not signed in: The phone joined the network, but the portal could not be completed.
  • Signed in, but access failed: The portal appeared to accept the sign-in, but the subsequent page did not load.
  • Not tested: The traveler could not safely or practically disable cellular data for the check.

Restore cellular data after the Wi-Fi test. If a portal asks for sensitive account or payment information, verify that the request is appropriate before submitting it. A public network name or a successful portal does not, on its own, establish that every connection over the network is secure.

Some phones have features that fall back to cellular when Wi-Fi is poor. Where available, disable those features for the test or keep cellular data off until the Wi-Fi-only observation is complete. Otherwise, a successful page load may conceal a Wi-Fi failure.

Cellular: test the travel line with Wi-Fi off

Turn Wi-Fi off, restore cellular data, and confirm again that the travel eSIM is selected as the data line. Wait for the phone to register on a mobile network, then load a page or use another modest data task.

This is the decisive separation check: with Wi-Fi off, a successful data task demonstrates cellular connectivity at that moment. It does not by itself prove that the correct SIM carried the traffic. That conclusion also depends on the line-selection setting and, where available, the device’s usage information or the carrier’s records.

Record the time, selected data line, roaming settings, and result. If cellular data fails, distinguish the symptoms where possible:

1. No mobile registration: The phone does not appear to connect to a mobile network. 2. Registration without usable data: A mobile connection appears, but the test page does not load. 3. Wrong data line selected: The home line, rather than the travel eSIM, is designated for mobile data. 4. Intermittent or slow service: The page eventually loads, but repeated attempts stall or fail.

Do not infer the cause from a single failed page. Coverage, plan activation, device settings, network congestion, and the destination website are all possible factors. Check the line and plan settings first, then repeat the same small test.

What to measure—and what the numbers mean

A useful first-hour record contains both a functional result and, when appropriate, a performance result. Aggregated results from the FCC Speed Test app include speed, latency, and packet loss for both upload and download. A test can fail outright; a completed test can also reveal poor performance through high latency or packet loss, even if a page eventually loads. [1]

For a controlled comparison:

1. Cellular: Turn Wi-Fi off, verify the travel data line, and run the test. 2. Wi-Fi: Join and sign in to airport Wi-Fi, turn cellular data off, and repeat. 3. Log both outcomes: Include the time, location within the airport, connection type, and whether the test completed. 4. Restore the intended settings: Re-enable cellular data if needed and confirm the preferred data line.

A speed test consumes data, potentially a meaningful amount on a limited travel plan. Check the plan allowance before running repeated tests; a simple page-load check may be sufficient when the immediate question is whether a path works.

Ookla’s Q1 2025 analysis gives context for comparing the paths, not a prediction for an individual arrival. Among 48 major airports studied, 12 of the 41 with Wi-Fi data met the FCC’s 100 Mbps download and 20 Mbps upload benchmark; 21 of 48 met it on mobile, and only three met it on both. Those are median speed comparisons. They do not measure captive-portal success, eSIM setup success, or a first-hour failure rate. [2]

The miss: a successful page can still hide the wrong path

Consider a traveler who joins airport Wi-Fi, sees a page load, and assumes the Wi-Fi session is working. If cellular data remained enabled, the phone may have used cellular instead. If automatic data switching was also enabled, the traveler may need to check which line was used before attributing the traffic to the travel eSIM.

The reverse ambiguity matters too. A traveler may believe the eSIM is ready because a messaging app works, while the app is still using airport Wi-Fi. Turning Wi-Fi off for the cellular check removes that uncertainty about the connection type.

A failed Wi-Fi sign-in or an unexpected cellular-data charge is a practical sign that the intended separation did not hold. Neither identifies the cause by itself. Review the portal result, data-line selection, switching settings, home-line roaming setting, and the timing of the charge or usage. Contact the relevant carrier if the billing record remains unexplained.

Samsung documents separate views for mobile and Wi-Fi data usage. Those views can help establish which connection type consumed data, but their availability and detail depend on the device. A mobile-data total does not automatically identify the SIM or roaming tariff responsible for every byte. [3]

The underlying eSIM specifications address consumer profile architecture and remote SIM provisioning; they do not guarantee airport coverage, a successful Wi-Fi portal, or correct user-facing data selection. Those still need to be checked on the phone and against the applicable plan. [4]

What to record next time

Use a short log rather than relying on memory. For each connection, write down:

  • Time and place: Arrival time and where the test was performed.
  • Wi-Fi result: Network joined, portal completed or failed, and whether a page loaded with cellular data off.
  • Cellular result: Wi-Fi off, selected data line, mobile registration, and whether the page loaded.
  • Settings: Automatic data switching, home-line roaming, and travel-line roaming as observed.
  • Usage or charges: Relevant counter readings or carrier records, including their time window and whether they distinguish the two lines.
  • Performance, if tested: Upload or download speed, latency, packet loss, or a failed test. [1]

Treat a counter reading as supporting evidence, not instantaneous proof: a device or carrier may report usage on a different schedule or over a broader period than the test. Avoid resetting existing usage statistics unless their current value is no longer needed. Save only the information necessary for troubleshooting, and keep screenshots containing phone numbers or account details private.

The handoff at the end of the first hour is a known configuration: the preferred Wi-Fi state, the intended cellular-data line, an understood roaming setting, and a record of which independent tests succeeded or failed.

References

[1] https://fcc.github.io/vizmo/docs/ [2] https://www.ookla.com/research/reports/global-airport-internet-performance-q1-2025 [3] https://www.samsung.com/us/support/answer/ANS10002914/ [4] https://www.gsma.com/solutions-and-impact/technologies/esim/esim-specification/

Zebra AI