Tokyo Speed Test: NRT/HND, Shinjuku/Shibuya, and Subway Coverage

30 Oct 2025

This tokyo mobile speed test digs into what you’ll actually get on the ground at Narita (NRT), Haneda (HND), around Shinjuku and Shibuya, and riding the JR Yamanote and Tokyo Metro/Toei subway corridors. We ran repeat measurements across multiple days, hours, and networks, highlighting download/upload speeds, latency for calls, and how connections behave in stations, tunnels, and on the move. If you’re landing and need to work, place VoIP calls, or navigate without hiccups, this is the practical picture—plus an open CSV you can reuse. We also flag eKYC caveats unique to Japan, and quick set-up steps to avoid common roaming pitfalls. For multi-city itineraries, there are notes on how Tokyo compares with other regions we cover across Destinations. Teams and travel managers can also access more granular logs via the Partner Hub and scale with our For Business options.

How we tested

Devices: iPhone 15 Pro (iOS 18), Google Pixel 8 (Android 15).
Profiles: international travel eSIMs connecting to KDDI (au) and SoftBank, plus a domestic NTT Docomo data SIM for baseline.
Tools: Speedtest by Ookla, nPerf, and ICMP/UDP pings to Tokyo-region cloud endpoints; passive cell metrics.
Sample size: 210 spot tests, 3 days, peak and off-peak windows.
Location set: NRT T1/T2/T3 arrivals/departures; HND T3 and T1; Shinjuku Station concourses and platforms; Shibuya Scramble and station areas; JR Yamanote between Shinjuku–Shibuya–Harajuku; Metro Ginza, Hanzomon, Marunouchi; Toei Oedo segments.
Networks: 5G NSA/sub‑6 where available; 4G LTE fallback. No public Wi‑Fi tests included.

Notes: - Results reflect traveller conditions: crowding, handovers, and indoor attenuation. Absolute speeds will vary by device, plan, and cell load. Latency is the most stable indicator of “snappiness” for calls and apps.

Airport results: NRT and HND

Narita (NRT)

Arrivals halls (T1/T2): 5G NSA on KDDI and Docomo consistently strong. Typical downloads 180–320 Mbps, uploads 20–40 Mbps. Median latency to Tokyo endpoints 19–24 ms.
Immigration/baggage zones: throughput dips under load; we saw 70–150 Mbps down, 10–25 Mbps up. Latency remained steady (20–28 ms), which matters more for calls and messaging.
Landside SIM areas and rail concourses: solid mid-band 5G with 150–280 Mbps down; short-lived cell handovers near escalators may briefly stall background uploads.
Outdoor kerbs/taxi stands: 200–350 Mbps down when line-of-sight to gNodeB is clear; gusty wind and crowds don’t affect RF, but vehicles can create transient multipath.

Pro tip: - If your phone keeps flapping between 5G and LTE, lock to LTE for the eSIM during a call. Latency stays in the low 20s ms, and you avoid 5G handover blips.

Haneda (HND)

T3 Arrivals (international): fastest median in the study—220–360 Mbps down, 25–50 Mbps up across KDDI/Docomo/SoftBank, 17–22 ms latency.
Domestic T1 check-in halls: 140–260 Mbps down, 15–35 Mbps up. Peak morning departures add jitter but not a major latency spike.
Monorail/Keikyu connectors: 80–180 Mbps down while in motion; expect a few seconds of RSRP dips in tunnels with quick recovery on platforms.

Set-up checklist on landing: 1. Install your eSIM before take-off; download profile on airport Wi‑Fi only if needed. 2. Ensure data roaming is on, and APN is auto-provisioned by your eSIM provider. 3. Toggle Airplane Mode once to trigger registration; wait for 4G/5G icon. 4. Run a quick test near a window or open area to establish a baseline. 5. For VoIP, run a latency test; you want sub‑40 ms to Tokyo.

Shinjuku and Shibuya: streets, stations, and concourses

Shinjuku

East/West exits, street level: 120–260 Mbps down, 15–35 Mbps up. Latency 20–26 ms. Crowded evenings can throttle uploads more than downloads.
JR concourses and shopping arcades (basement): 40–120 Mbps down typical; uploads 8–20 Mbps. Occasional cell selection to LTE only; calls remained stable.
Platform edges (Chuo Rapid, Yamanote): 60–140 Mbps down; in-train ramp to 50–100 Mbps once doors close.

Shibuya

Scramble crossing and Hachiko exit: 150–400 Mbps down on mid-band 5G; 20–40 Mbps up. Latency 18–24 ms.
Shibuya Station basement corridors: 30–90 Mbps down; 8–18 Mbps up, likely due to heavy contention and deeper placement.
Miyashita Park and Cat Street: 120–240 Mbps down outdoors; uploads 15–30 Mbps.

Call quality and latency: - To Tokyo-region media servers: 15–30 ms (excellent for WhatsApp, FaceTime, Zoom audio). - To Singapore: 60–90 ms (good). - To US West: 120–170 ms (acceptable for voice, mild delay on video). - To US East/Europe: 180–260 ms (voice fine with slight overlap; video requires turn-taking). - We observed jitter 3–8 ms on 5G and 6–15 ms on LTE in busy concourses. Packet loss remained under 0.5% on all tests except brief handovers.

Pro tips: - If your video call stutters as you descend into a station, disable 5G temporarily to keep a stable LTE anchor. - Noise matters more than bandwidth; use headphones with a mic to ensure the other party hears you in Shinjuku rush hour.

Subway and JR corridors: coverage in motion

Tokyo’s rail network is extensively covered with in-station and in-tunnel repeaters. Expect the following patterns:

JR Yamanote (Shinjuku–Harajuku–Shibuya): 80–180 Mbps down in-train; 20–110 Mbps during curves or when shadowed by buildings. Latency holds 25–35 ms; handovers are quick.
Chuo Rapid (Shinjuku area): 70–150 Mbps down; uploads ~12–25 Mbps.
Metro Ginza/Marunouchi/Hanzomon platforms: 60–200 Mbps down, 10–30 Mbps up. In tunnels between stations: 25–80 Mbps down, occasional 2–5 second dips.
Toei Oedo (deeper level): platforms 50–140 Mbps down; tunnels occasionally drop to 10–40 Mbps with 5–10 second shelves under peak load.
Station mezzanines and ticket gates: biggest contention spikes; you may see high throughput but spiky jitter. Start large uploads on the platform, not at the gate.

Checklist: keep data stable in transit - Turn off Low Data Mode/Low Power Mode during maps or calls. - Don’t chase bars—band selection switching costs you stability; allow automatic selection unless a call is critical. - If a roaming profile prefers a weaker network, manually select the stronger local partner (KDDI/Docomo/SoftBank) and re-enable automatic later.

eKYC in Japan: what travellers need to know

Domestic mobile numbers (voice/SMS) from Japanese operators usually require eKYC (ID verification) and, for some plans, a local address. This is strict, even for eSIM.
Data-only international eSIMs used by visitors generally do not require Japanese eKYC. They connect to Japanese networks via roaming agreements.
SMS-based logins: if an app demands a local SMS number, a data-only eSIM won’t help. Use app-based OTP, email login, or a secondary number from your home SIM.
VoIP/SIP: inbound SIP over mobile data may be affected by CGNAT. Most consumer apps (WhatsApp, FaceTime, Teams, Zoom) work fine; enterprise SIP trunks may need TURN/ICE relays.

If you’re coordinating teams, our For Business options include pre-trip provisioning guidance and app whitelists that avoid SMS-only traps.

At-a-glance numbers

Airports (NRT/HND) median: 230 Mbps down / 30 Mbps up / 20–23 ms latency.
Shinjuku/Shibuya streets median: 180 Mbps down / 25 Mbps up / 21–27 ms latency.
Stations/platforms median: 90 Mbps down / 15 Mbps up / 24–32 ms latency.
In-train (JR/Metro/Toei) median: 70 Mbps down / 12 Mbps up / 27–38 ms latency.

These medians are traveller-grade: plenty for HD maps, rideshare, cloud docs, and stable VoIP. Latency, not peak Mbps, dictates call quality—and Tokyo’s is consistently low.

Run your own tokyo mobile speed test (5-minute setup)

Before leaving your hotel, update carrier settings and OS.
Pick one test app (e.g., Speedtest) to keep results comparable.
Test in three spots: outdoors, station platform, and in-carriage.
Log results with time and place. Note 5G/LTE and network name.
For calls, run a 3–5 minute WhatsApp audio test. Observe delay and overlap, not just Mbps.
Repeat at peak (08:00–09:30 or 18:00–20:00) and off-peak to compare.

Dataset and open CSV

We’re making a de-identified dataset available as an open CSV for researchers, planners, and power users. Columns include: timestamp, coarse location (grid), network (Docomo/KDDI/SoftBank), RAT (5G/LTE), download, upload, latency, jitter, packet loss, and motion state (stationary/in-train).

Request or access the CSV via the Partner Hub with a short note on your use case. Teams on For Business get ongoing updates per quarter.
We’ll also reference this study under Japan in Destinations, and cross-compare with other regions.

Who this helps

Business travellers who need predictable call quality and uploads from stations and rides.
Remote teams planning on-the-go video meets between terminals and city centre.
Photographers and creators uploading from platforms or cafés near Shinjuku/Shibuya.
Travellers on multi-leg trips comparing connectivity across regions.

Planning onward travel? See our eSIM round-ups for neighbouring trips: Esim North America, Esim Western Europe, and country picks like Esim United States, Esim France, Esim Italy, and Esim Spain.

Practical tips to stay connected

Prefer mid-band 5G when stationary; switch to LTE if you’re seeing frequent 5G-LTE flaps during movement.
Download offline maps for central Tokyo as a backup.
If your upload is throttled in a station concourse, step to a platform or outside for a 2–3x improvement.
Keep a power bank; 5G scanning drains batteries on dense cells.
Disable VPNs during initial registration; re-enable if needed after your first speed test.

FAQ

Which network was “best” overall? All three majors (NTT Docomo, KDDI au, SoftBank) performed well. KDDI/Docomo had the most consistent low latency in our tests. SoftBank delivered strong peaks outdoors. For travellers on roaming eSIMs, you can’t always choose—but manual selection can help in edge cases.
Is 5G necessary for good performance in Tokyo? Not strictly. LTE delivered 50–150 Mbps with sub‑40 ms latency in most locations—enough for work and VoIP. 5G helps with quick uploads and large downloads, and is more sensitive to handovers in motion.
Will my VoIP calls work in the subway? Yes, with caveats. On platforms and most tunnels you’ll get stable audio. Expect brief 2–10 second dips between some stations (especially deeper Toei segments). Use LTE for long calls while moving and start video only when stationary.
Do I need a Japanese SIM with eKYC? No, not for data-only international eSIMs. Local Japanese numbers typically require eKYC; use app-based verification instead. If your workflow relies on SMS to a local number, plan ahead with your home SIM or an approved service.
Can I tether/hotspot? Yes. We maintained 20–60 Mbps to a laptop on LTE and 80–200 Mbps on 5G in central areas. Some plans rate-limit hotspot traffic; check your eSIM’s terms.
How does Tokyo compare with other regions? Tokyo’s latency is best-in-class, which benefits calls and cloud apps. Peak throughput is on par with major EU cities. See regional guides via Destinations and compare with Esim Western Europe and Esim North America.

Next step: browse Japan and neighbouring regions on Destinations and request the open CSV via the Partner Hub.

Read more blogs

Andes Highlights (3 Weeks): Peru–Bolivia–Chile–Argentina Connectivity

Planning a south america itinerary 3 weeks through the high Andes? This route stitches together Peru’s Sacred Valley, Bolivia’s La Paz and Salar de Uyuni, Chile’s Atacama Desert, and northern Argentina’s quebradas or Mendoza wine country—often by long-distance bus and a couple of short flights. Connectivity is different at altitude: coverage is strong in cities but drops in high passes and salt flats; bus Wi‑Fi is patchy; border towns can be blackspots. The smart move is an eSIM with multi‑country coverage, backed by offline maps, offline translations, and a simple routine for crossing borders by bus without losing service. Below you’ll find a practical, connectivity-first itinerary; checklists to prep your phone, apps and documents; and on-the-ground tips for staying online where it matters: booking transport, hailing taxis, backing up photos, and navigating when the signal disappears.If you’re transiting via Europe or North America, you can also add a layover eSIM to stay connected door-to-door. Start with our country list on Destinations, then follow the steps, and you won’t waste time chasing SIM shops at 3,500 metres.The 3‑week Andes route at a glanceWeek 1: Peru (Cusco, Sacred Valley, Machu Picchu) - Fly into Cusco (or Lima then connect). - Base in Cusco; day trips to Pisac/Chinchero/Maras–Moray. - Train to Aguas Calientes; Machu Picchu visit; return to Cusco or continue to Puno/Lake Titicaca.Week 2: Bolivia and Chile (La Paz, Uyuni, San Pedro de Atacama) - Bus/collectivo via Copacabana to La Paz. - Fly or overnight bus to Uyuni. - 3‑day Uyuni–altiplano tour ending in San Pedro de Atacama (Chile).Week 3: Chile and Argentina (Atacama to Salta or Mendoza/Buenos Aires) - Choose: - North: San Pedro to Salta/Jujuy by bus; fly to Buenos Aires. - Or South: San Pedro–Calama flight to Santiago; bus or flight to Mendoza; onward to Buenos Aires.Connectivity notes (quick): - Cities: generally strong 4G/4G+; 5G in major hubs (Santiago, Buenos Aires). - Altitude/rural: expect long no‑signal stretches (Uyuni, altiplano passes, Paso Jama). - Bus Wi‑Fi: often advertised, rarely reliable. Plan to be offline onboard. - Border regions: networks switch; a multi‑country eSIM avoids sudden loss.eSIM vs local SIMs for a 4‑country tripFor a route with multiple borders and remote legs, eSIM wins on time and reliability.What a multi‑country eSIM gets you: - One plan across Peru, Bolivia, Chile, Argentina (check coverage per country on Destinations). - No passport/SIM registration queues at kiosks. - Keep your home number active on the physical SIM for calls/SMS codes. - Instant top‑ups if you burn data on photos or navigation.When a local SIM still helps: - Long stay in one country with heavy data use (e.g., a month in Buenos Aires). - Dead zones where a different local network performs better (rarely worth the hassle on a 3‑week pace).Practical approach: - Use an eSIM as your primary data line across all four countries. - If you find a specific local network far better in one region, add a cheap local SIM and keep the eSIM as backup.Device readiness checklist (before you fly)1) Check eSIM compatibility and SIM‑lock status on your phone.2) Buy and install your eSIM while on home Wi‑Fi. Keep a PDF/printed copy of the QR code.3) Label lines clearly (e.g., “eSIM Andes Data”, “Home SIM”).4) Turn on data roaming for the eSIM; leave roaming off for your home SIM to avoid charges.5) Set up dual‑SIM rules: data on eSIM; calls/SMS default to home SIM if needed.6) Download offline: Google Maps/Organic Maps for all target regions; language packs (Spanish at minimum); bus/air tickets; hotel confirmations.7) Cloud backups: set to upload on Wi‑Fi only; pre‑create shared albums for travel companions.8) Test tethering/hotspot with your laptop/tablet.If you’re transiting popular hubs, consider a short layover eSIM: - USA connections: add an Esim United States or a broader Esim North America.- Europe connections: Madrid/Barcelona? Use an Esim Spain. Paris or Rome? See Esim France and Esim Italy. Multi‑country layovers? Try Esim Western Europe.City‑by‑city connectivity notesCusco & the Sacred Valley (Peru)Coverage: Good in Cusco city; variable in high villages (Maras/Moray) and along Inca Trail approaches.Tips: Download Sacred Valley maps offline; pin viewpoints and ruins. most taxis use WhatsApp—save your accommodation’s number.Machu Picchu/Aguas Calientes: Patchy to none at the citadel. Upload your photos later; don’t rely on live ticket retrieval.Lake Titicaca: Puno and CopacabanaPuno: Reasonable 4G; bus terminals crowded—screenshot QR tickets.Crossing to Copacabana: Expect a signal drop around the border; have directions saved offline.La Paz (Bolivia)Good urban 4G; the cable car network has decent signal but tunnels do not.Yungas/“Death Road” tours: Mountain valleys cause dead zones—share your emergency contacts with the operator, carry a charged power bank, and don’t plan remote calls.Uyuni and the Altiplano (Bolivia to Chile)Uyuni town: OK 4G; ATMs finicky—use Wi‑Fi for banking apps.Salt flats/lagunas: Assume offline for most of the 3‑day tour. Guides often carry satellite phones; agree a pickup time/place in San Pedro and preload your map route.San Pedro de Atacama (Chile)Town: Solid 4G; accommodations often have Wi‑Fi but speeds vary.Geysers, Valle de la Luna: Offline navigation essential; sunrise trips start before mobile networks wake up in some areas.Salta/Jujuy or Mendoza/Buenos Aires (Argentina)Salta/Jujuy: Good city coverage; quebradas have long no‑signal sections.Mendoza: City 4G/5G; vineyards outside town can be patchy.Buenos Aires: Strong 4G/5G; ideal for cloud backups and large downloads before you fly home.Border crossings by bus: step‑by‑stepThe big ones on this route: Peru–Bolivia (Puno/Copacabana), Bolivia–Chile (Uyuni–San Pedro via Hito Cajón), Chile–Argentina (Paso Jama to Salta or Los Libertadores to Mendoza).How to keep service and sanity:1) The day before:- Top up your eSIM data.- Confirm your plan includes both countries you’re entering/leaving.- Download offline maps for both sides of the border and your town of arrival.- Save bus company WhatsApp and terminal address offline.2) On departure morning:- Keep a paper copy or offline PDF of tickets, insurance, and accommodation proof.- Charge phone and power bank; pack a short cable in your daypack.3) On the bus:- Don’t count on bus Wi‑Fi. Keep your eSIM as primary, but expect drops near mountain passes.- If your phone supports it, enable “Wi‑Fi calling” for later when you reach accommodation Wi‑Fi.4) At the border posts:- Data may be unavailable. Keep QR codes and booking numbers offline.- After exiting one country and entering the next, toggle Airplane Mode off/on to re‑register on the new network.- If the eSIM doesn’t attach, manually select a network in Mobile Settings.5) Arrival:- Send your accommodation a quick WhatsApp when you’re back online.- Recheck your eSIM’s data roaming is on; confirm you’re on an in‑country network, not a weak roaming partner.Pro tips: - Dual profiles: If your eSIM allows, keep a secondary profile for a different network in the same country—helpful in border towns.- Cash buffer: Some border terminals don’t accept cards; download a currency converter for offline use.Offline survival kit (5‑minute setup)Maps: Download regions for Cusco, Sacred Valley, Puno, La Paz, Uyuni, San Pedro, Salta/Jujuy or Mendoza, and Buenos Aires.Translations: Download Spanish for offline use; add phrasebook favourites (bus tickets, directions, dietary needs).Documents: Save PDFs of passports, tickets, hotel addresses; star them for quick access.Rides: Screenshots of pickup points; pin bus terminals and hotel doors.Entertainment: Podcasts and playlists for long bus legs, set to download on Wi‑Fi only.Altitude and your tech: what changesCoverage gaps lengthen: Fewer towers at high altitude; valleys can block signal. Assume offline on remote excursions.Batteries drain faster in cold: Keep your phone warm and carry a power bank (10,000–20,000 mAh).Hotel Wi‑Fi may be congested: Schedule big uploads (photo backups, app updates) for big-city stays like Santiago or Buenos Aires.GPS still works offline: Your blue dot shows on offline maps without data—preload everything.Data budgeting for 3 weeksTypical traveller usage across this route: - Messaging/Maps/Bookings: 0.2–0.5 GB/day- Social and photo sharing: 0.3–0.7 GB/day- Occasional video calls/streaming: 0.5–1.0 GB/dayFor a mixed-use trip, plan 15–25 GB for 3 weeks. Heavy creators should double it and upload over hotel Wi‑Fi when possible. If you work remotely, consider a higher‑capacity plan and a backup eSIM; see our guidance on For Business.Practical route with transport and connectivity cuesDays 1–4 Cusco base: Strong city signal; day trips may be spotty—go offline-ready.Days 5–6 Machu Picchu: Expect no service at the ruins; sync tickets ahead.Days 7–8 Puno to La Paz via Copacabana: Border signal drop; re‑register networks after crossing.Days 9–11 Uyuni tour to San Pedro: Treat as offline; charge nightly; carry spare cables.Days 12–14 San Pedro: Stable in town; tours offline; top up data before Paso Jama.Days 15–17 Salta/Jujuy or Mendoza: Good urban 4G; rural patches are offline.Days 18–21 Buenos Aires: Strongest connectivity of the trip; clear your uploads and map downloads for the flight home.Partnering and stopover extrasHospitality and tour operators in the Andes: help your guests stay connected—explore co‑branded solutions via our Partner Hub.Transatlantic flyers: test your eSIM setup on a layover with an Esim United States or Esim Western Europe before hitting high-altitude blackspots.FAQs1) Do I need a local SIM in each country?No. A multi‑country eSIM covering Peru, Bolivia, Chile and Argentina is simpler and works well for a 3‑week pace. Consider a local SIM only if you’ll spend longer in one country and want the absolute best regional coverage.2) Will my WhatsApp number change with an eSIM?No. WhatsApp is tied to your registered number, not your data line. Keep your home SIM active for voice/SMS (roaming off if you wish), and use the eSIM for data—WhatsApp continues as normal.3) Can I hotspot to my laptop or camera?Yes. Enable tethering on your eSIM. Mind your data: cloud backups and OS updates can burn gigabytes—set them to Wi‑Fi only or schedule in big cities.4) What if there’s no signal on the Uyuni/Atacama legs?That’s expected. GPS still works offline. Pre-download maps and translations, carry a power bank, and sync plans with your tour operator before departure.5) Will I get roaming charges at borders?If you’re using a multi‑country eSIM with coverage in both countries, you won’t incur extra roaming fees from your home carrier. Keep roaming off on your home SIM to avoid accidental use.6) I’m connecting via Europe or the US—worth getting a layover eSIM?Yes. It’s an easy way to test your setup and stay reachable. Try Esim North America or country options like Esim Spain, Esim France, or Esim Italy for common hubs.Next step: Browse South America coverage options and build your plan on Destinations.

31 Oct 2025

How to Set Up an eSIM on Samsung Galaxy S24/S25

Travelling with a Samsung Galaxy S24 or S25? Good news: both flagships support eSIM, so you can add a local data plan in minutes without swapping plastic SIMs. This guide walks you through samsung esim setup step by step for each device series, explains the three activation methods you’ll see (QR code, manual entry, carrier app), and shows how to run dual-SIM smartly while abroad. You’ll also find a practical troubleshooting checklist and region-specific tips to pick the right plan before you fly. If you’re new to eSIM, don’t worry — the process is quick once you know where to tap, and you can store multiple eSIMs on your phone, switching them on and off as you travel. Keep this page handy when you land, connect to Wi‑Fi, and you’ll be online in under five minutes.Explore ready-to-use travel plans for popular regions via our Destinations hub, or jump straight to curated bundles like Esim United States, Esim France, Esim Italy, Esim Spain, Esim Western Europe and Esim North America.Before you start: quick checklistWi‑Fi or a stable data connection for download and activation.Your eSIM QR code or activation details (SM-DP+ address, activation code).Phone battery above 30%.Phone unlocked from your carrier (if it’s carrier-locked, you can’t add non-approved eSIMs).Latest software installed: Settings > Software update > Download and install.Note your EID (sometimes required by providers): Settings > About phone > Status information > EID.Tip: Save your eSIM QR code to another device or print it. You’ll need to scan it using your phone.Confirm your Galaxy model and softwareSamsung’s menus vary slightly by One UI version.Galaxy S24/S24+/S24 Ultra (One UI 6/6.1): eSIM lives under Settings > Connections > SIM manager.Galaxy S25/S25+/S25 Ultra (One UI 7+): wording may show as SIM manager or SIMs, still under Settings > Connections.Most S24/S25 variants support multiple eSIM profiles stored and two lines active at once. Active combinations can vary by region/carrier: - Common: 1 physical nano-SIM + 1 eSIM active simultaneously. - On many variants: 2 eSIMs can be active simultaneously (Dual SIM Dual Standby). To confirm, open Settings > Connections > SIM manager: you’ll see available SIMs and which combinations can be toggled on together.Samsung eSIM setup on Galaxy S24 seriesFollow these steps on S24, S24+ and S24 Ultra.1) Open Settings. 2) Tap Connections. 3) Tap SIM manager. 4) Tap Add eSIM (or Add mobile plan). 5) Choose your method: - Scan QR code. - Enter activation code (manual SM-DP+). - Use via carrier/app (if your provider supports in‑app download). 6) Wait for download and installation (1–3 minutes). Stay on Wi‑Fi. 7) When prompted, label the eSIM (e.g., “Spain eSIM”). 8) Set defaults: - Mobile data: choose the travel eSIM. - Calls/Messages: keep your home SIM if you want your usual number active. 9) Turn on Data roaming for the travel eSIM (Settings > Connections > Mobile networks > Data roaming). 10) Toggle off Data roaming on your home SIM to avoid accidental charges.Samsung eSIM setup on Galaxy S25 seriesOn S25, S25+ and S25 Ultra, the flow is nearly identical, with minor wording changes.1) Open Settings. 2) Tap Connections. 3) Tap SIM manager (or SIMs). 4) Tap Add eSIM (or Add mobile plan). 5) Select your activation method: - Scan QR code. - Enter details manually (SM-DP+ and activation code). - From carrier/app (if available). 6) Keep Wi‑Fi on while the plan downloads and activates. 7) Name the line and set: - Preferred SIM for mobile data. - Preferred SIM for calls/messages. 8) Enable Data roaming for the travel eSIM; disable it on your home SIM.Note: On both S24 and S25, you can change these defaults anytime via Settings > Connections > SIM manager.Three ways to activate your eSIMScan a QR code (most common)On your Samsung, go to Settings > Connections > SIM manager > Add eSIM > Scan QR code.Point the camera at the QR from your eSIM provider.Confirm installation, label the plan, and set data/call preferences.If prompted for a confirmation code or PIN, enter the one provided with your eSIM.Enter details manually (SM-DP+)If you have text details instead of a QR:Settings > Connections > SIM manager > Add eSIM > Enter activation code.Enter the SM-DP+ address, activation code and (if required) confirmation code exactly as given.Proceed to install and set preferences.Use a carrier/app downloadSome providers support direct download via their app or via “Use via carrier”:Install the provider’s app over Wi‑Fi.Sign in and follow prompts to “Add mobile plan/eSIM” on your Samsung.Approve installation when the system dialog appears.Travel setup that just works: data on eSIM, calls on home SIMTo minimise roaming costs and keep your number reachable:Set Mobile data to the travel eSIM.Toggle Data roaming ON for the travel eSIM; OFF for your home SIM.Keep Calls and Messages on your home SIM if you want continuity.Enable Wi‑Fi Calling for your home SIM when supported (Settings > Connections > Wi‑Fi Calling), so you can receive calls/messages over Wi‑Fi without roaming.For Europe trips spanning multiple countries, look at Esim Western Europe. For multi-country hops across the US and Canada, see Esim North America.Managing two lines (dual-SIM) on SamsungRename lines for clarity: Settings > Connections > SIM manager > tap each SIM > Edit name/colour.Choose per‑contact default line in the Phone/Contacts app, or pick “Ask every time” for calls.Control which line uses data: SIM manager > Mobile data.Turn a SIM on/off without deleting it: SIM manager > toggle the switch next to the line.Store multiple eSIMs for future trips, then activate only the one you need.Pro tip: If your device supports two active eSIMs, you can run “Work” and “Travel” eSIMs together — handy for business trips. If you’re equipping a team, explore centralised options via For Business.Troubleshooting: fast fixesIf activation fails or you don’t get data, try these in order:1) Use solid Wi‑Fi, not mobile data, to download the eSIM. 2) Check date/time are automatic: Settings > General management > Date and time. 3) Reboot after installation. 4) Ensure the eSIM is toggled ON in SIM manager. 5) Set Mobile data to the eSIM and enable Data roaming on that line. 6) Network mode: set to 5G/LTE/3G/2G (auto) or LTE/3G/2G if 5G causes issues. Settings > Connections > Mobile networks > Network mode. 7) APN: if data connects but no internet, add the APN provided by your eSIM vendor: - Settings > Connections > Mobile networks > Access Point Names > Add. - Enter Name/APN exactly as provided, save, and select it. 8) Airplane mode ON for 10 seconds, then OFF. 9) Clear and re-add: Delete the eSIM profile and reinstall from the QR/activation code. 10) Carrier lock check: If “Add eSIM” is missing or you see “This device is locked,” contact your original carrier to unlock. 11) EID requirement: Some providers need your EID to push the plan. Find it under Settings > About phone > Status information > EID.Still stuck? Ensure your plan covers the country you’re in. Browse by country via Destinations, or pick region-ready options like Esim United States or Esim Spain.Picking the right plan for your tripUSA city breaks and road trips: choose Esim United States for nationwide coverage.Paris, Lyon, Côte d’Azur: start with Esim France.Rome, Florence, Amalfi: go with Esim Italy.Barcelona, Madrid, Andalusia: try Esim Spain.Pan‑European itineraries: Esim Western Europe keeps you connected across borders.US + Canada circuits: pick Esim North America.Partners and agencies managing multiple travellers can streamline procurement via our Partner Hub.Pro tips for smooth travel dataInstall and test the eSIM on Wi‑Fi before you fly, but don’t enable data roaming until you land.Download offline maps and key apps while on hotel Wi‑Fi to save data.Keep your QR/activation code somewhere safe for reinstallation if needed.Battery saver: if coverage is patchy, temporarily set Network mode to LTE/3G/2G to reduce 5G hunting.WhatsApp usually follows the account you set up originally, not your current data SIM. You can keep using WhatsApp on your home number while your eSIM handles data.When leaving a country, switch your Mobile data back to your home SIM or your next eSIM, and toggle Data roaming accordingly.FAQQ1) Can the Galaxy S24/S25 run two eSIMs at the same time?A) Many variants support two active lines at once, and on numerous models this can be “2 eSIMs active” or “1 eSIM + 1 physical SIM.” The exact combination depends on your region/carrier. Check Settings > Connections > SIM manager to see available toggles on your unit.Q2) How many eSIMs can I store on my Samsung?A) You can store multiple eSIM profiles (varies by model, typically 5+), but only two lines can be active simultaneously. You can turn profiles on/off without deleting them.Q3) Do I need to enable data roaming for my travel eSIM?A) Yes, outside the eSIM’s “home” country you typically must enable Data roaming for that eSIM. Keep Data roaming OFF on your home SIM to avoid charges.Q4) Will my home number still receive calls and texts?A) If you leave your home SIM active for calls/messages, you can continue receiving them (charges may apply if roaming). Use Wi‑Fi Calling where available to reduce costs, or set Calls/Messages to the eSIM if you’ve ported/forwarded your number.Q5) My eSIM installed, but data doesn’t work. What now?A) Set the eSIM as Mobile data, enable Data roaming on that line, and verify APN settings from your provider. Try a reboot, toggle airplane mode, and check network mode. If needed, delete and reinstall the eSIM.Q6) Can I move an eSIM from my old phone to my new Samsung?A) Most eSIMs are one‑device installs. Use “Transfer” only if your provider supports it; otherwise request a new QR/activation code from your provider. Delete the profile from the old phone once the new one is active.Next stepPick your destination and add your plan in minutes. Start with Destinations — or, if you’re touring multiple countries, go straight to Esim Western Europe.

30 Oct 2025

Private APN & Enterprise Security: When and Why to Use It

Mobile data isn’t just “internet in your pocket.” For enterprises with roaming staff, payment terminals, or IoT fleets, the path your traffic takes is a security control. A private APN creates a closed data path from SIMs to your network, letting you enforce policy, isolate traffic from the public internet, and integrate cleanly with VPNs or zero-trust tools. This guide explains what private APNs are, when to use them, how they work with VPNs, typical use cases, what they cost, and how to deploy successfully—without jargon.If your teams travel, the stakes go up: roaming adds new networks, new attack surfaces, and variable policies. A well-designed private APN keeps device traffic predictable and governable across borders. Whether you’re connecting laptops via eSIM, securing field equipment across Esim Western Europe, or building a partner-ready solution via our Partner Hub, the right APN choice determines how easily you can meet audit, compliance, and uptime targets.Use this as a practical checklist to decide if a private APN fits—and how to keep costs and complexity under control.What is a Private APN?A private APN (Access Point Name) is a carrier-side configuration that defines how SIM traffic is handled. Rather than breaking out to the public internet using NAT on a generic, shared APN, a private APN:Identifies your SIMs into a dedicated routing contextAssigns private/static IP ranges if requiredApplies custom firewall, DNS and content policiesDelivers traffic to you over a defined path (e.g., IPsec/GRE to your DC/cloud)Think of it as “your own lane” inside the mobile core, with enterprise-grade traffic isolation and policy controls.Key benefitsTraffic isolation: Your devices don’t share a public NAT pool with everyone else.Predictable addressing: Private or static IPs allow IP allowlisting and system-to-system integrations.Policy enforcement: Apply DNS filtering, firewall rules, and segmentation per SIM group.Controlled breakout: Choose where traffic exits—your data centre, cloud VPC, or a regional gateway.Common variantsPrivate APN with public breakout: Policy and IP control, but final internet egress is via carrier NAT.Private APN with private breakout: End-to-end private path to your network over IPsec/GRE/MPLS; no public internet until you decide.Roaming home routing vs local breakout: Decide whether traffic tunnels back to a home gateway or breaks out regionally for latency/compliance.When should you use a Private APN?Choose a private APN when one or more of these apply:You must IP-allowlist mobile devices to access corporate apps, SCADA, or payment backends.You need to block open internet access by default, allowing only approved destinations.You require consistent, auditable logs of device egress and DNS activity.You deploy IoT/OT fleets where devices are headless and should never be internet-reachable.You need static or reserved IPs per SIM for device-to-cloud rules or legacy systems.You’re operating in higher-risk or compliance-heavy sectors (finance, health, critical infrastructure).Travel scenarios where it shines:Regional workforces moving between the US, Canada and Mexico using Esim North AmericaTeams rotating across France, Italy and Spain with Esim France, Esim Italy and Esim SpainShort-term projects needing fast onboarding in the US via Esim United StatesCheck your target countries and carriers via Destinations.Private APN vs VPN vs Zero TrustThese are complementary, not either/or.Private APN: Carrier-layer isolation and policy. Ensures trusted device identity (SIM/IMSI), private addressing, and controlled gateways.VPN (IPsec/GRE/SSL): Secure tunnel from APN gateway to your network or cloud VPC. Use to terminate traffic into your security stack.Zero Trust/SASE: Identity-driven access per user/device/app. Often layered on top (device certificate, posture checks) for user devices.Recommended patternsCorporate laptops/phones on the roadPrivate APN + clientless approach: Route all traffic via your gateway where CASB/SWG runs.Or Private APN + device VPN: Enforce split tunnel for corporate apps; APN blocks all other internet.IoT/OT equipmentPrivate APN with private breakout to your VPC/DC; no public internet access.Partners/contractorsPrivate APN with segmented SIM groups and per-segment firewall policies; issue time-bound SIMs.Pro tips: - Avoid double encryption where unnecessary. If APN-to-cloud IPsec is in place and devices only talk to your internal services, you may not need device-level VPN. - Use device certificates via MDM/EMM for user hardware. The APN identifies the SIM; your MDM identifies the device.Security controls you actually getIdentity and segmentationSIM/IMSI-based policies and groupsOptional IMEI binding for device lockAddressingPrivate RFC1918 subnets, with optional static IPs per SIMCGNAT or 1:1 NAT as neededFirewallingDefault deny; allow only required FQDNs/IPs/portsGeo or ASN-based controls for sensitive backendsDNSForce safe resolvers; block DNS-over-HTTPS egressUse internal resolver via tunnel for split-horizon domainsLogging and SIEMPer-SIM flow logs and DNS logs exported to your SIEMDDoS postureWith private breakout, you decide internet egress; with public breakout, leverage carrier scrubbingRoaming and travel: what to plan forLatency vs controlHome routing centralises control but adds RTT from, say, Tokyo to a London gateway.Regional breakout (e.g., EU vs US gateways) reduces latency for users on Esim Western Europe or Esim North America.Regulatory constraintsSome countries restrict VPN or enforce local breakout. Match your APN design to the route permitted in the destination. Confirm on Destinations.IP allowlists and roaming IPsIf you rely on static source IPs, avoid scenarios where roaming uses dynamic CGNAT or changes egress country by country. Private breakout fixes this by presenting consistent IP space.Device onboarding during traveleSIM QR provisioning helps. Pre-stage profiles for each region (e.g., Esim France for an EU tour, Esim United States for US trips).Cost model: what you’ll actually payExpect costs in these buckets:One-off setupAPN configuration, IP ranges, SIM group policies, initial tunnel(s)Monthly platform feeCovers APN gateway capacity, monitoring, and managementPer-SIM chargeOften tiered; sometimes includes static IP optionsData usagePooled or per-SIM; roaming may have regional ratesTunnels and hostingIPsec/GRE tunnel endpoints in your DC/VPC; cloud egress costs may applyChange management/professional servicesPolicy updates, incident support, new region gatewaysWays to optimise: - Start with a private APN + public breakout for policy control; add private breakout later for critical apps. - Use regional gateways to avoid transatlantic hairpin data charges for travellers. - Reserve static IPs only for systems that truly need allowlists; use dynamic private IPs elsewhere. - Monitor top talkers; block chatty apps at APN firewall instead of paying for unnecessary data.Quick decision checklist: do you need a private APN?Tick “yes” if the statement is true:We must restrict mobile devices from open internet by default.We rely on IP allowlists for any critical app or third-party API.We need device fleet observability (per-SIM traffic and DNS logs).We operate IoT or unattended devices that should never be publicly reachable.We have travellers across multiple regions and require consistent egress policies.We must meet compliance or audit requirements for network segregation.Three or more “yes” answers usually justify a private APN.Implementation: step-by-step1) Define scope and risk - List device types (laptops, phones, IoT), users, and data sensitivity. - Map apps/domains/ports that must be reachable. - Decide “deny-by-default” vs “allow-by-default”.2) Choose coverage and form factor - Confirm countries and networks via Destinations. - Select regional plans (e.g., Esim North America or Esim Western Europe) and country add-ons (Esim Italy, Esim Spain).3) Addressing and segmentation - Allocate private subnets per SIM group (e.g., staff vs IoT). - Decide where static IPs are required.4) Breakout architecture - Start with private APN + public breakout if you only need policy/DNS controls. - For maximum control, deploy private breakout to your DC/cloud via IPsec/GRE. - If latency matters for travellers, request EU and US gateways.5) Security policy and DNS - Set default deny; allow only business apps/domains. - Enforce DNS to your resolvers; block DoH/DoT egress except approved endpoints. - Add geo/ASN blocks for risky destinations if relevant.6) Integrate identity and device posture - Bind SIMs to users via MDM/EMM; consider IMEI binding for corporate-owned devices. - For user devices, layer device certificates or ZTNA for application-level control.7) Build and test tunnels - Establish redundant tunnels; validate failover. - Test roaming from target countries (US/EU) for latency and policy correctness.8) Logging, monitoring, and alerts - Export flow and DNS logs to SIEM. - Create alerts for policy violations and unusual data volumes.9) Pilot and scale - Pilot with 10–50 users/devices across two regions. - Iterate rules, then scale to full fleet.Pro tips: - Test common collaboration apps (Teams/Zoom) for split vs full tunnel to avoid performance complaints. - Document emergency bypass processes for critical field operations.Common pitfalls (and how to avoid them)IP allowlists failing during roamingUse private breakout with consistent source IPs; avoid reliance on roaming CGNAT ranges.DNS leaksForce DNS to your resolver; block outbound UDP/TCP 53/853 except to approved IPs; manage DoH with SNI filtering.Overly broad “allow” rulesPrefer FQDN and minimal port ranges; segment by SIM group.Latency surprisesPlace gateways regionally; verify RTT from your top travel corridors.Tunnel single points of failureAlways build at least two tunnels to independent endpoints.Who is this for?Enterprises securing roaming staff devices with eSIMPayments, logistics, and field services managing unattended endpointsMSPs/ISVs embedding connectivity into their solutions via our Partner HubOrganisations looking for turnkey policies and global eSIM bundles via For BusinessFAQQ1: What is the main difference between a public and a private APN?A private APN creates an isolated routing context for your SIMs with custom policies and addressing. Public APNs use shared NAT to the internet with limited control and no dedicated security posture.Q2: Do I still need a VPN if I use a private APN?Often yes, but it depends. For IoT or tightly controlled fleets, APN-to-cloud IPsec may be sufficient without device VPN. For user devices, a device VPN or ZTNA provides identity and app-level control on top of the APN.Q3: Can I get static IPs for my SIMs?Yes. Private APNs can assign static or reserved private IPs per SIM, which is ideal for IP allowlisting and legacy integrations. Public static IPs are possible but less common; many use private breakout and egress via corporate firewalls.Q4: Will a private APN work while roaming internationally?Yes. Design for either home routing (all traffic returns to your gateway) or regional breakout (e.g., EU/US). This affects latency and compliance—verify coverage per country on Destinations.Q5: How much does a private APN cost?Expect a setup fee, a monthly APN platform charge, per-SIM pricing (optionally for static IPs), data usage, and tunnel/cloud costs. You can start small with policy-only public breakout, then add private breakout and regional gateways as needs grow.Q6: Does this support eSIM and multi-region bundles?Yes. Private APN policies apply to both physical SIMs and eSIMs. For travellers, pair your APN with regional plans like Esim Western Europe or Esim North America and country-specific options such as Esim France or Esim United States.Next stepDesign the right private APN for your fleet and travel patterns. Speak to our enterprise team via For Business to scope coverage, security policies, and rollout.

30 Oct 2025