Zac Kew-Denniss / Android Authority
TL;DR Numerous Pixel owners are experiencing random eSIM connectivity issues.
While some lose connection intermittently, others complain of not being able to switch eSIM carriers.
Google has acknowledged the issue, but there’s no fix yet.
Another day, another instance of a Pixel throwing a wrench in daily usage. After dealing with widespread battery woes and the March update randomly bricking some Pixel phones, owners of these devices are now reporting connectivity issues, particularly when using an eSIM.
We’ve come across numerous reports of difficulties using eSIM on Pixel devices over the past few weeks. The reports are scattered across multiple online channels, including X, Reddit, Pixel support forums, and Google’s Issue Tracker. The most commonly affected Pixel models include the Pixel 9 and the Pixel 10 series, and users across the board have confirmed that physical SIM cards work just fine.
Don’t want to miss the best from Android Authority? Set us as a favorite source in Google Discover to never miss our latest exclusive reports, expert analysis, and much more.
to never miss our latest exclusive reports, expert analysis, and much more. You can also set us as a preferred source in Google Search by clicking the button below.
One such Reddit user, ErvinMarec, reports that the eSIM on their Pixel 10 Pro stops showing any signs of life frequently. This forces them to restart the phone every three to four days to get it to work again. A similar issue has been described by another user on a Google Issue Tracker thread. Meanwhile, some other users have not been able to use the eSIM at all due to an unexplained error. The exact cause of the issue remains unclear.
A few others are ached by their inability to switch to another eSIM provider, despite using a carrier-unlocked Pixel phone. While most users report difficulty in porting, the issues reported vary with each, which is why we’re unable to draw a common line, nor could we establish whether this is caused by a hardware or a software issue.
... continue reading