If your travel eSIM fails to connect or stops working mid-trip, most issues have a small set of causes — installation errors, APN misconfiguration, data routing to the home SIM, profile conflicts with the physical SIM, or a weak local network. This guide walks through the checks that resolve the majority of problems in order, from most common to least common.
Activation fails the first time you scan the QR
The most common activation failure is a QR scan that produces an error before the profile installs. Three reasons in practice. First, the camera failed to focus — hold the phone steady 15 cm over the QR, fill the viewfinder entirely, avoid glare on the screen. Second, the QR was already redeemed on a different device — every travel eSIM QR is single-use; if you installed it on a previous phone, reactivation requires a new code from the provider’s support team. Third, the phone had no working network at install time — eSIM profiles download over Wi-Fi or cellular data and won’t install in airplane mode with no Wi-Fi.
When the scan succeeds and the profile installs but the line still does not connect after you exit airplane mode, the next check is that the profile is the active data line: Settings > Cellular > Default Voice Line, on iPhone, or Settings > SIM cards on Android. If “Default data” is on the physical home SIM, the eSIM is installed but idle.
No signal after switching data line to the eSIM
If the eSIM is correctly selected as the data line but the phone shows no service, three causes dominate. The first is that data roaming is disabled on the eSIM specifically. On iPhone, Settings > Cellular > Cellular Data > Data Roaming must be on; on Android, Settings > Mobile Network > Data Roaming likewise. Home operators default this to off because they do not want you roaming on their network; travel eSIMs depend on roaming being explicitly enabled.
The second is that the APN has not auto-configured. Some eSIMs install the access-point name automatically; some phones require Settings > Cellular > [the eSIM line] > Network Selection → Automatic, and then to confirm APN. If data roaming is enabled, signal bars are showing, and the line still does not work, this is almost always the missing APN. The provider’s app or order-confirmation email usually lists the APN to enter manually.
The third is simply weak local coverage. If the bars are 1 of 5 or none, walk to a window, a stairwell exit, or an upper floor; building materials — concrete, brick, foil-backed insulation — routinely absorb LTE signal in hotels.
Slow speeds that don’t match your home network
If the eSIM connects and pages load but everything feels sluggish, the cause is network-side, not eSIM-side. Travel eSIM rides whatever local carrier the profile authenticates against, at whatever coverage and capacity that operator has at your location. Common bottlenecks: the local network is heavily loaded at peak tourist hours (early evening in hotels, mid-afternoon in airports); you are in a 4G-coverage hole between two cells with hand-off failing; the plan is throttled after a fair-use threshold (unlimited plans typically speed-cap to 1 Mbps or 512 kbps after the priority bucket is exhausted, documented as “unlimited” with a footnote).
To verify, run a Speedtest against a nearby server during off-peak hours. If at 7 a.m. you see 25 Mbps and at 10 p.m. you see 0.5 Mbps, the network is fine and the timing is the problem. If off-peak speeds are under 5 Mbps, the local carrier has weak coverage in your area, and switching to a different eSIM (if the provider offers a partner network) is the only fix.
”Invalid profile” or “Profile could not be installed” error messages
Invalid-profile errors at install time mean the QR or activation code was already redeemed, the code expired before you scanned it (some providers issue time-bound codes), or the file contents were corrupted during download. The fix is always a fresh code from the provider’s order history or support team; the profile itself is keyed to one device and one redemption.
If you previously installed the eSIM on a different phone — even years ago, even if the device is no longer in your possession — the profile is still considered used. Email the provider the order number and the device you switched from; they invalidate the old binding and reissue a code.
eSIM profile is installed but does not appear in Cellular settings
If Settings > Cellular shows only the home SIM line and no eSIM, the profile is technically installed but not visible. The fix differs by phone. On iPhone: General > VPN & Device Management > remove any old eSIM profiles left over from previous trips, then Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings. On Android: Settings > Connections > SIM card manager > Add mobile plan; if no QR appears, manually re-enter the activation code from the order email.
A profile can also be present but not labeled. Check by going to Settings > General > About and looking for “Digital SIM” or “EID” entries — multiple plans may be installed under that heading.
Old eSIMs from previous trips crowding the available slots
Every phone caps the number of stored eSIM profiles at five to ten depending on manufacturer. After several trips the slots fill up; the install error then says “Profile could not be added — maximum reached”. The fix is to delete profiles you no longer use: iPhone > Settings > Cellular > tap the eSIM > Remove Cellular Plan; Android > Settings > Connections > SIM card manager > tap the plan > Erase.
Deleting an unused profile does not affect the live eSIM currently in use. Do not delete the plan you’re currently on — the live data line will drop.
When to contact support and what to share
If the steps above do not resolve the issue within ten minutes of troubleshooting, contact the provider’s support team with this exact information: order number, destination country, arrival date, phone model, iOS or Android version, the exact error message if any, what you have already tried, and a screenshot of the eSIM detail screen from Settings > Cellular. With those six points support can usually diagnose in one reply whether the issue is an APN, a profile reissue, or a coverage gap.
