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

30 Oct 2025

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 context
Assigns private/static IP ranges if required
Applies custom firewall, DNS and content policies
Delivers 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 benefits

Traffic 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 variants

Private 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 America
Teams rotating across France, Italy and Spain with Esim France, Esim Italy and Esim Spain
Short-term projects needing fast onboarding in the US via Esim United States

Check your target countries and carriers via Destinations.

Private APN vs VPN vs Zero Trust

These 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 patterns

Corporate laptops/phones on the road
Private 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 equipment
Private APN with private breakout to your VPC/DC; no public internet access.
Partners/contractors
Private 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 get

Identity and segmentation
SIM/IMSI-based policies and groups
Optional IMEI binding for device lock
Addressing
Private RFC1918 subnets, with optional static IPs per SIM
CGNAT or 1:1 NAT as needed
Firewalling
Default deny; allow only required FQDNs/IPs/ports
Geo or ASN-based controls for sensitive backends
DNS
Force safe resolvers; block DNS-over-HTTPS egress
Use internal resolver via tunnel for split-horizon domains
Logging and SIEM
Per-SIM flow logs and DNS logs exported to your SIEM
DDoS posture
With private breakout, you decide internet egress; with public breakout, leverage carrier scrubbing

Roaming and travel: what to plan for

Latency vs control
Home 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 constraints
Some 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 IPs
If 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 travel
eSIM 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 pay

Expect costs in these buckets:

One-off setup
APN configuration, IP ranges, SIM group policies, initial tunnel(s)
Monthly platform fee
Covers APN gateway capacity, monitoring, and management
Per-SIM charge
Often tiered; sometimes includes static IP options
Data usage
Pooled or per-SIM; roaming may have regional rates
Tunnels and hosting
IPsec/GRE tunnel endpoints in your DC/VPC; cloud egress costs may apply
Change management/professional services
Policy updates, incident support, new region gateways

Ways 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-step

1) 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 roaming
Use private breakout with consistent source IPs; avoid reliance on roaming CGNAT ranges.
DNS leaks
Force DNS to your resolver; block outbound UDP/TCP 53/853 except to approved IPs; manage DoH with SNI filtering.
Overly broad “allow” rules
Prefer FQDN and minimal port ranges; segment by SIM group.
Latency surprises
Place gateways regionally; verify RTT from your top travel corridors.
Tunnel single points of failure
Always build at least two tunnels to independent endpoints.

Who is this for?

Enterprises securing roaming staff devices with eSIM
Payments, logistics, and field services managing unattended endpoints
MSPs/ISVs embedding connectivity into their solutions via our Partner Hub
Organisations looking for turnkey policies and global eSIM bundles via For Business

FAQ

Q1: 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 step

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

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

Inflight & Maritime Roaming: How to Avoid Shock Bills (2025)

If you’ve ever stepped off a flight or cruise to an unexpected roaming bill, you’ve likely met the inflight and maritime networks that quietly connect your phone at 35,000 feet or out at sea. These aren’t normal mobile networks. They use satellite backhaul, sit outside most inclusive roaming plans, and are priced at premium wholesale rates that get passed straight to you. Data can be charged by the megabyte at eyewatering rates; calls and texts aren’t cheap either. The good news: bill shock is 100% avoidable with a little prep. In this guide, we’ll demystify how inflight and shipboard networks bill, show you exactly how to disable them, and share safer alternatives—like port‑day eSIMs and Wi‑Fi packages—that keep you connected for a sensible price. Whether you’re flying long‑haul, cruising the Med, or ferry‑hopping, use this checklist-driven playbook to stay online without risking maritime roaming charges.Why inflight and maritime roaming is differentHow these networks billAircraft and ships run small onboard cellular networks (often branded AeroMobile, SITAONAIR/OnAir, Panasonic, Telenor Maritime, WMS, or “Cellular at Sea”).Your phone sees them like any other roaming partner and may auto‑connect if mobile data/roaming is on.Usage is routed via satellite, then rated by your home carrier at special “non‑terrestrial” tariffs. These typically sit outside any domestic allowance or standard roaming bundles.On your device, the operator name may show as “AeroMobile”, “OnAir”, “Cellular at Sea”, or an unfamiliar code (often starting with 901-xx).Not included in your roaming bundle“Roam Like at Home” in the EU and most global roaming add‑ons usually exclude inflight/maritime networks.Welcome texts and usage alerts can be delayed or missing while you’re connected at sea/in‑air, so don’t rely on them.Spend caps and data bars may not trigger in real time; charging records can arrive hours later.Typical costs to expectPrices vary by carrier, but this is a realistic market picture (per-person, pay‑as‑you‑go roaming):Data: £5–£15 per MB inflight; £3–£10 per MB at sea. A single photo upload or app update can cost pounds.Calls: £2–£6 per minute (both inbound and outbound).SMS: £0.50–£1.50 each.Bundles: A few airlines offer paid inflight roaming “passes” via certain carriers, but read the small print—many still cap at very low data amounts.Bottom line: keeping data roaming on around these networks is the fast lane to maritime roaming charges and bill shock.Where travellers get caughtAt altitude: Phones latch onto the cabin network; background services (mail, messaging backups, cloud photos, app refresh) burn megabytes within minutes.At sea days: Cruise lines broadcast a strong shipboard signal; your phone prefers it once the shore network fades.Near port: You may still see the ship’s network at the pier. If “automatic” network selection is on, your phone can reattach to the maritime signal when you step back onboard.False confidence in caps: Spend caps and warning texts can arrive too late to save you from charges already incurred.Dual‑SIM confusion: Travellers think the travel eSIM protects them, but the primary SIM remains “roam‑enabled” and quietly connects to the ship/plane network.How to avoid bill shock: step‑by‑stepBefore take‑off or boarding a cruiseDo this while you still have reliable terrestrial signal.1) Turn off data roaming on all SIMs- iPhone: Settings > Mobile Data > Data Roaming = Off (repeat for each line).- Android: Settings > Network & Internet > SIMs > Data Roaming = Off (per SIM).2) Lock network selection to “Manual” and pick your current terrestrial carrier- iPhone: Settings > Mobile Data > Network Selection > turn off Automatic.- Android: Settings > Mobile Networks > Network Operators > turn off Automatic.3) Keep Airplane Mode as your default in the air/at sea; plan to re‑enable Wi‑Fi only- This completely blocks auto‑attach to satellite networks.4) Optional but recommended- Turn off Wi‑Fi Assist (iPhone): Settings > Mobile Data > Wi‑Fi Assist = Off.- Disable Background App Refresh (iPhone) / restrict background data (Android).- For dual‑SIM: set the travel eSIM as the only “Data” line; set your primary SIM to “Off” for data and ideally for voice while airborne/at sea.In the air: safest settingsBefore pushback: enable Airplane Mode.Then enable Wi‑Fi only for the airline hotspot.Do not turn off Airplane Mode to “grab a quick signal.” Even a minute of background data can be costly.At sea: safest settingsWhile sailing: keep Airplane Mode on; enable Wi‑Fi only if you’ve bought the ship’s plan.On port days: once the ship is docked, step ashore and connect to a terrestrial network or your port‑day eSIM.If you remain onboard in port, your phone may still see the ship network. Leave Airplane Mode on until you have strong shore Wi‑Fi or a verified local mobile signal.Quick checklist: zero‑risk configurationAirplane Mode: On (in air/at sea)Wi‑Fi: On (only if you intend to use onboard/airport/port Wi‑Fi)Bluetooth: As needed for headphonesData Roaming: Off (all SIMs)Network Selection: ManualDual‑SIM: Only your intended data eSIM is active for dataPro tip: Add these settings to a note or screenshot so you can re‑check quickly.Safer alternatives that actually work1) Airline Wi‑Fi and messaging plansMany carriers offer flat‑price passes for browsing or messaging.Pros: predictable cost; often enough for email and IM; unlimited messaging passes are increasingly common.Watch‑outs: streaming or VPN may be blocked or sold as an add‑on; speeds vary by route and aircraft.2) Cruise Wi‑Fi packagesBuy for the days you need rather than the whole voyage.Pros: unlimited data tiers exist; cheaper than cellular satellite roaming; supports calls/messages via apps.Watch‑outs: per‑device limits, throttling, and app blocks (video calling) are common; premium tiers may be required for video.3) Port‑day eSIM strategyUse a local or regional eSIM for each country you’ll visit—only when you’re ashore. Switch data to Wi‑Fi while sailing.Browse country and regional options on Destinations.Examples:USA calls? See Esim United States.City breaks in France? Use Esim France.Italian ports? Consider Esim Italy.Barcelona and the Balearics? Try Esim Spain.4) Regional passes for multi‑country tripsIf you’re visiting several countries in one cruise or fly‑drive, regional eSIMs keep things simple:Western Europe: Esim Western Europe covers popular EU stops under one plan.USA, Canada, Mexico: Esim North America is ideal for repositioning cruises or North American tours.How to use on port days:1) Keep Airplane Mode on until docked.2) Step ashore, then turn off Airplane Mode and select your eSIM as the data line.3) Confirm you’re on a terrestrial network (carrier name from the eSIM’s coverage list).4) When sailing again, revert to Airplane Mode and Wi‑Fi only.Pro tips to minimise data while travellingPre‑download maps, playlists, and shows over hotel or home Wi‑Fi.Turn off cloud photo backups and auto‑updates while abroad.Use apps that offer “low data mode” (e.g., streaming services, maps).Prefer Wi‑Fi calling and messaging apps (iMessage, WhatsApp, Signal) when on paid Wi‑Fi; disable carrier voice roaming entirely if you don’t need it.On iPhone, set your travel eSIM as “Data Only” and keep your primary SIM for calls/texts on Wi‑Fi calling.If you must keep mobile voice on for critical calls, set network selection to manual and re‑check after every take‑off or sail‑away.For business travellers and travel partnersCorporate travellers: equip teams with a clear inflight/at‑sea policy and pre‑trip device setup. Managed eSIMs and rules-based spend caps reduce risk. Learn more For Business.Travel trade and cruise specialists: add bill‑shock prevention to your pre‑departure comms and offer packaged eSIMs for port days. Explore our tools in the Partner Hub.Frequently asked questionsQ1) If data roaming is off, can I still be charged?A: With data roaming off, you shouldn’t incur data charges—but calls and SMS can still be billed at inflight/maritime rates if your device connects to the ship/plane network for voice/SMS. The safest approach is Airplane Mode with Wi‑Fi on.Q2) Will my EU “Roam Like at Home” plan cover maritime roaming charges?A: No. Roam Like at Home applies to terrestrial networks in the EEA. Inflight and maritime networks are excluded and typically charged at special rates.Q3) How do I know I’m on a ship or aircraft network?A: Look for operator names like “AeroMobile”, “OnAir”, “Cellular at Sea”, “Telenor Maritime”, or unfamiliar numeric codes. If you’re in the air or far from shore and you see any signal without Airplane Mode, assume it’s a satellite-backed network and disconnect.Q4) Are airline “mobile roaming passes” good value?A: They can be if priced sensibly and you only need light messaging. Compare them with the airline’s Wi‑Fi plans—Wi‑Fi often offers more data for less money. Always check the data cap and what services are included.Q5) Can I use WhatsApp on a cruise without paying for Wi‑Fi?A: Not safely. If your phone connects to the ship’s cellular network, even small messages can trigger maritime roaming charges. Buy the cruise Wi‑Fi package or wait for port‑day terrestrial service with a local/regional eSIM.Q6) What’s the best setup for a multi‑country cruise?A: Use Airplane Mode at sea, buy a cruise Wi‑Fi package if you need connectivity while sailing, and activate a regional eSIM—such as Esim Western Europe or Esim North America—for port days.The takeawayInflight and shipboard mobile networks are designed for convenience, not value. They sit outside most roaming bundles and bill at satellite‑grade prices. Prevent maritime roaming charges by defaulting to Airplane Mode in the air and at sea, re‑enabling Wi‑Fi only, and using port‑day or regional eSIMs when you’re back on shore.Next step: Plan your port‑day coverage with our country and regional options on Destinations.

30 Oct 2025

VPN for Travel: When You Need It, When You Don’t, and Best Practices

Travelling with a VPN can be a smart move—but not for every connection or every task. The right setup keeps your banking and accounts safe, helps when streaming libraries change, and prevents snooping on public Wi‑Fi. The wrong setup can drain your battery, slow you down, or even cause bank apps to lock you out. This guide cuts through the noise with practical, traveller-first advice on when to use a VPN, when to skip it, and how to configure it properly. We’ll cover banking and streaming workflows, split tunnelling, battery impact, and regional legality notes—plus checklists you can follow before you fly.Most importantly: mobile data from a reputable eSIM is typically safer than public Wi‑Fi. If you can move sensitive tasks (like banking) to cellular data via a local plan—think [Esim Western Europe], [Esim North America], or country options like [Esim United States], [Esim France], [Esim Italy], and [Esim Spain]—you’ll reduce the need for a VPN and avoid many connection headaches. When you do use a VPN, do it deliberately.When you need a VPN while travellingUse a VPN for any of the following:Public Wi‑Fi (hotels, cafés, airports): Encrypts your traffic to reduce snooping and rogue access point risks.Banking logins from a new country: A VPN with a home-country exit can reduce fraud flags and MFA loops. See best practices below.Streaming or sites with regional libraries: A VPN may help access your home library while abroad. Expect mixed results; platforms actively block VPNs.Voice and messaging apps where services are blocked: A VPN can sometimes restore access where VoIP or messaging is restricted.Bypassing DNS hijacking and content injection: Some networks tamper with traffic. A VPN gives you a clean path.Remote work requirements: Your employer may mandate a VPN for internal tools. If you’re travelling for work, coordinate with IT or see [For Business].Pro tip: - If Wi‑Fi makes your apps glitchy, toggle a VPN on with a local server (for performance) or switch to mobile data via an eSIM.When you don’t need a VPNSkip the VPN in these cases:On mobile data via an eSIM: Cellular networks are inherently harder to snoop than open Wi‑Fi. For sensitive tasks abroad, use data from [Esim Western Europe], [Esim North America], or a country plan like [Esim United States] rather than hotel Wi‑Fi.Speed-sensitive tasks where encryption overhead matters: Real-time calls, gaming, or large uploads may perform better without a VPN—especially on weak Wi‑Fi.Services that require your true location/IP: Some airline apps, local transport tickets, and banking fraud engines may block or challenge VPN IPs.Apps with end-to-end encryption already in place: Messaging apps with E2EE are safe transport-wise, though a VPN can still hide metadata from local networks.When your VPN is causing more harm than good: If your bank locks you out or streaming refuses to load, disconnect or use split tunnelling.VPN vs eSIM mobile data: which to use and whenBest default: eSIM mobile data (no VPN). Use a trusted provider, avoid public Wi‑Fi for sensitive tasks, and you’ll be secure enough for everyday travel.Add a VPN on Wi‑Fi. Especially in airports, cafés, co‑working spaces, or rentals with unknown routers.Add a VPN on mobile data only when needed. For example, to reach corporate resources or to try a home streaming library.Not sure which eSIM you’ll need? Browse country and regional plans via [Destinations], including bundles like [Esim Western Europe] and [Esim North America], or country plans such as [Esim France], [Esim Italy], [Esim Spain], and [Esim United States].Banking abroad: the smart setupWhy banks flag loginsBanks use device fingerprints, IP geolocation, and behaviour analytics. A sudden login from a new country—or from a known VPN data centre—can trigger extra verification or temporary blocks.Step-by-step: banking that “just works”Update your banking app at home. Test logins on Wi‑Fi and mobile data.Enable strong authentication. App-based 2FA or biometrics are best.Prefer mobile data over Wi‑Fi when abroad. Use your eSIM for all banking sessions.If you must use Wi‑Fi, enable your VPN—but choose a server in your home country.Disable ad‑blockers/trackers for the banking app if it fails to load; they can interfere.Keep your phone number active for OTPs if your bank relies on SMS, or switch to app-based OTP before departure.Avoid repeated failed logins. If you get stuck, switch off the VPN and try again on mobile data.Troubleshooting: - Banking app won’t load on VPN: Switch to a home-country server. If still failing, disconnect VPN and try on mobile data. - MFA loop: Clear the app cache and cookies (or reinstall). Swap networks (e.g., move from hotel Wi‑Fi+VPN to eSIM). - New device detection: Don’t factory reset or switch phones mid-trip unless necessary.Pro tip: - Keep a secondary bank/credit card with a separate app as backup in case one provider is overzealous with fraud rules.Streaming on the road: realistic expectationsWhat can work: - Catch-up TV or home library access via a VPN exit in your home country. - Downloaded content before travel—most reliable, no VPN needed. - Regional free-to-air apps that don’t enforce strict geo-checks.What often won’t: - Big platforms with aggressive VPN detection. Even “working” servers can stop at any time. - Casting from a VPN’d phone to a smart TV on hotel Wi‑Fi. The TV and phone must be on the same network; VPN can break discovery.Battery and data impact: - VPN + streaming = more CPU and up to 5–15% extra data overhead. Use efficient protocols (WireGuard) and drop video resolution if on metered data. - On weak Wi‑Fi, adding a VPN can amplify buffering. Try a nearby server, or use eSIM data.Split tunnelling for streaming: - Want only your streaming app on the VPN and the rest local for speed and maps? Use split tunnelling (details below). If unavailable on your device, consider a second browser or a dedicated streaming device.Pro tip: - Download episodes over a fast network before a long train or flight. It sidesteps geo-blocks and saves battery.Split tunnelling: how and when to use itWhat it is: - Split tunnelling lets you choose which apps or sites use the VPN and which go direct.When to use: - Banking: Route your bank app via a home-country VPN while leaving maps and ride‑hailing off VPN for better location accuracy. - Streaming: Put the streaming app through the VPN; keep everything else local for speed. - Work: Send corporate tools via the company VPN, keep personal browsing normal.How to set it up (general): - Android: Many VPN apps offer “Split tunnelling” or “Per‑app VPN.” Choose apps to include or exclude from the tunnel. - Windows/macOS: Look for “Split tunnelling,” “App exclusions,” or “Bypass VPN for selected apps” in your VPN client. Some allow domain-based rules. - iOS/iPadOS: Per‑app split tunnelling is limited. Some VPNs provide app exclusions; if yours doesn’t, use workarounds like a dedicated browser for VPN use, or keep critical apps on mobile data while other tasks run on Wi‑Fi+VPN.Pro tips: - Prefer “include list” (only chosen apps use VPN) for tighter control. - Test each app after changes—some ignore system proxies and behave differently.Battery, speed and data: making a VPN travel‑friendlyProtocol matters: WireGuard (or modern variants) is efficient and fast; IKEv2 is stable on mobile; OpenVPN can be heavier on battery.Server choice: Nearby servers reduce latency and drain. Use a home-country server only when you truly need that IP.Auto‑connect logic: Configure “auto‑connect on insecure Wi‑Fi” rather than “always on” to save battery.Kill switch: Enable it on laptops; on phones, use it when you must ensure no leaks (e.g., on hostile networks). Remember it blocks traffic if the VPN drops.Background apps: Limit background sync and cloud photo uploads on metered/VPN connections.Tethering: VPN on the phone plus hotspot adds overhead. If possible, run the VPN on the tethered device instead.Legal and policy notes by regionLaws and enforcement vary. High‑level guidance for travellers:EU/UK/US/Canada: VPNs are generally lawful for personal use. Platforms may still block VPN IPs; terms of service apply.Turkey/Egypt: VPNs are sometimes throttled or specific services blocked. Have multiple protocols available (WireGuard and IKEv2/OpenVPN).India: VPN use is legal; some services changed logging policies. Stick to reputable providers.UAE/Oman: Authorities penalise misuse of VPNs to commit offences. Access to unlicensed VoIP may be limited. Expect some blocks.Russia: Many VPNs are restricted or blocked; connections may be unreliable.China: Most foreign VPN apps are blocked. If you need one, set it up before arrival and expect instability. Corporate solutions fare better.Iran: Extensive restrictions; connections can be risky and unreliable.Practical tips: - Install and test your VPN before you go. - Keep multiple protocols and server options. - Be prepared to fall back to mobile data via eSIM where Wi‑Fi is filtered.Note: Rules change. Check local regulations and service terms in your destination. For plan coverage, see [Destinations].Quick setup checklistBefore you travel: - Choose a reputable VPN with WireGuard and IKEv2 support. - Install on all devices and test banking logins at home. - Enable app‑based 2FA for financial accounts. - Configure auto‑connect on insecure Wi‑Fi and a kill switch where needed. - Set up split tunnelling for banking/streaming apps if available. - Download offline maps and streaming content in advance. - Add a travel eSIM for safer mobile data: check regional bundles like [Esim Western Europe] and [Esim North America], or country plans such as [Esim France], [Esim Italy], [Esim Spain], and [Esim United States].On the road: - Prefer eSIM mobile data for sensitive tasks; avoid public Wi‑Fi when possible. - Use VPN on public Wi‑Fi; pick the nearest server unless you need a home IP. - If something breaks, toggle VPN off/on, switch servers, or move to mobile data.For teams and business travellersCoordinate with IT: Use approved clients/protocols and per‑app VPN profiles.Separate profiles: Keep work apps in a managed profile (Android) or use MDM on iOS/macOS to enforce per‑app VPN.Performance planning: Offer regional gateways for roaming staff to reduce latency.Policy: Document when VPN is mandatory vs optional to preserve battery on the move.If you manage roaming teams or resell travel connectivity, explore Simology’s solutions [For Business] and our [Partner Hub].FAQDo I need a VPN for hotel Wi‑Fi?It’s strongly recommended. Hotel Wi‑Fi is shared and often poorly segmented. A VPN encrypts your traffic and reduces exposure to snooping or rogue hotspots.Will a VPN break my banking app?It can. Banks often block data centre IPs. Try your bank on mobile data first. If using Wi‑Fi, connect your VPN to a home‑country server. If it still fails, disconnect the VPN and use eSIM data.Is it legal to use a VPN abroad?In many countries, yes. Some restrict or block VPNs, and misuse can carry penalties. Check local rules in your destination and follow platform terms. Be prepared with eSIM data as a fallback.Which VPN protocol is best for travel?Start with WireGuard for speed and battery efficiency. If blocked or unstable, switch to IKEv2 (good on mobile) or OpenVPN UDP/TCP as a last resort.Do I need a VPN if I use an eSIM?Often no, especially for banking and routine browsing on mobile data. Still use a VPN on public Wi‑Fi or when you specifically need a home IP or company access.Will a VPN reduce my battery life?Modestly. Expect extra drain, especially on weak networks. Use efficient protocols, nearby servers, and auto‑connect only on insecure Wi‑Fi to minimise impact.Next step: Pick a local or regional eSIM to keep sensitive tasks on mobile data and reduce VPN headaches. Start with [Destinations].

30 Oct 2025