Why Your eSIM Isn’t Working — And How to Actually Fix It
You’ve landed at a new airport, airplane mode off, and nothing. No signal, no data, just a spinning icon mocking you from the status bar. If you’re running an eSIM — especially a travel eSIM from one of the big retail providers — this moment is more common than any of them want to admit. ESIM Not Working
The frustrating part isn’t the failure itself. It’s that eSIM errors are rarely explained clearly, and most troubleshooting guides read like they were written for someone who’s never seen a smartphone. So let’s skip the basics and get into what actually goes wrong, and why.
The Device Compatibility Problem Nobody Talks About Enough
Most eSIM providers will tell you to “check device compatibility” as a first step. What they won’t tell you is that compatibility is far more layered than a simple yes/no list. A device can be eSIM-capable in hardware but locked by a carrier, or running firmware that doesn’t properly support remote SIM provisioning on a specific network band.
Apple devices have historically been the most reliable eSIM experience, partly because Apple controls both hardware and software, and partly because their GSMA-compliant implementation is tight. Android is messier — even within the same brand, two models released the same year can behave differently depending on regional variants and modem firmware.
Devices released before 2018 are almost universally incompatible. But even newer devices can surprise you. If you’re traveling with a budget Android and your eSIM refuses to install, the problem might not be the eSIM at all.
Activation Failures — The Most Misdiagnosed Issue
Here’s where things get interesting from a technical standpoint. When an eSIM fails to activate, most users assume the QR code is broken or that the plan hasn’t been processed. In reality, the failure often happens at the SM-DP+ server level — the backend infrastructure that handles remote SIM provisioning.
If that server times out, returns an error, or experiences a momentary load issue, your device gets stuck mid-handshake. The eSIM profile lands in a broken state, and no amount of restarting will fix it cleanly without deleting and re-downloading the profile.
A few things that trip people up consistently:
Common activation mistakes
- Scanning the QR code without a stable Wi-Fi connection
- Activating before the provider has actually “armed” the profile on their end
- Using the same QR code twice (most providers issue single-use codes)
- Installing the eSIM on a device that’s still carrier-locked
That last one is particularly worth flagging. Carrier locks are still active on many devices sold through operators in markets like the US and Japan, and unlocking isn’t always straightforward for travelers who didn’t buy their device outright.
Once It’s Installed — Why You Still Might Have No Internet
Getting the profile installed is half the battle. Actually, routing data through it is another problem entirely.
The most overlooked setting is Data Roaming. It sounds counterintuitive — you’re using a local-ish eSIM plan, why would roaming need to be on? — but many travel eSIMs operate as virtual networks piggybacking on local infrastructure via roaming agreements. If your device doesn’t have roaming enabled for that profile, it simply won’t connect, even with full signal bars.
APN settings are the other frequent culprit. Most modern eSIM providers push the correct APN automatically when the profile installs. But some budget providers, and some older carrier implementations, require manual configuration. If your provider’s app or documentation doesn’t spell this out clearly, that’s a red flag about their support quality overall.
A few things worth checking before you call it broken:
Steps that actually fix it
- Toggle Data Roaming on specifically for the eSIM profile
- Confirm the correct line is set as your mobile data line (dual-SIM devices need this manually set)
- Reset network settings as a last resort — it clears APN conflicts
- Check your data balance; some plans auto-pause at the limit rather than throttle
When to Contact Support — And Who’s Actually Good at It
If none of the above solves it, you’re into support territory. And this is where the gap between eSIM providers becomes very visible.
Airalo has built a large user base and decent documentation, but their live support is slow and mostly async. Holafly’s support is more responsive for retail customers, particularly on WhatsApp. Ubigi, which targets a more business-leaning audience, tends to have better technical support quality. Nomad and Yesim sit somewhere in the middle — functional, not exceptional.
The brutal truth is that most eSIM providers are resellers building on top of the same handful of network partners. When something breaks at the network layer, their support team often can’t do much until the upstream carrier resolves it. That’s a structural limitation of the current ecosystem, not just a support team problem.
The Bigger Picture ESIM Not Working
eSIM technology is genuinely more reliable than it was three years ago — the GSMA’s SGP.22 standard has matured, device support has widened, and provisioning infrastructure has improved significantly. But the travel eSIM market specifically is still growing faster than its quality control can keep up with.
The providers that will win long-term aren’t the ones with the cheapest data packages. They’re the ones building real-time diagnostic tools, transparent network status pages, and support pipelines that can actually escalate to the carrier level. A few — including Airalo with its recently expanded API ecosystem, and Ubigi’s enterprise-grade backend — are moving in that direction. Most aren’t.
For travelers, the practical takeaway is simple: test your eSIM before you need it. Install it at home, verify connectivity, and confirm your settings. Because troubleshooting a broken eSIM on airport Wi-Fi, jet-lagged, with a meeting in two hours, is a very different experience than doing it from your couch.
The technology works. The execution is still catching up.
