SIM Country Versus IP Country: The Mobile Mismatch Apps Check
On Android, any app can ask the phone two questions without requesting a single permission. What country is the SIM from? And what country is the network the phone is attached to right now? The answers come back as two letter country codes, like “sg” and “sg”. A third answer comes from the app’s own server, which sees the IP address the request arrived from and looks up where it’s located. When all three say the same country, nothing is interesting. When the SIM says Singapore, the network says Singapore and the IP says Germany, the phone is sitting on its home network in Singapore while its traffic appears to leave from Europe. There’s a narrow set of real world explanations for that, and a much wider set of operator mistakes that produce it. This piece covers what apps can and can’t read, which mismatches real people produce every day, which ones they almost never do, and how to set up a phone so the SIM, the network and the exit IP agree.
The three countries a phone reports
It helps to separate the three sources clearly, because people often lump them together as “location” and then fix the wrong one.
The SIM country comes from the SIM card itself. Every SIM carries an identity that includes a mobile country code and a network code for the carrier that issued it. Android turns that into a country code and a carrier name. A Singapore SIM reports Singapore wherever in the world the phone is.
The network country comes from the mobile network the phone is registered on at the moment. The network broadcasts its own country and network codes, and the phone reports them. At home, it’s your own carrier in your own country. Abroad, it’s whichever local network you’re roaming on.
The IP country comes from the address the app’s traffic arrives from, as seen by the app’s servers. It’s looked up in a geolocation database. The phone doesn’t report this. The server works it out.
These three can legitimately disagree. A roaming traveller has a SIM from one country and a network from another. Someone on hotel Wi-Fi has an IP from wherever the hotel’s connection is. But the ways they disagree in real life follow patterns, and those patterns are what an app compares you against.
There’s also a fourth source some apps use, which is the phone number itself. If an account was verified with a phone number, that number has a country code. It’s often the most permanent of the four, because it’s attached to the account rather than the device.
What Android apps can read
On Android, the telephony interface gives apps a surprising amount without any permission prompt.
An app can read the SIM’s country code, the SIM operator’s name, and the SIM operator’s numeric code, which is the country code and network code combined. It can read the same three things for the network the phone is currently registered on. It can ask whether the phone is roaming. It can read the type of data network, such as LTE or 5G, and whether a SIM is present at all.
Some things are behind permissions. The phone number needs a phone related permission and isn’t always available even then, since many SIMs don’t store it. Cell tower identities and signal details for nearby towers need location permission. Precise location needs location permission.
Some things are now locked away from ordinary apps entirely. Since Android 10, the permanent SIM and device identifiers, like the IMSI and the IMEI, need a privileged permission that normal apps from the store can’t get. That closed off a lot of the old ways of tying a device to a subscriber.
So on Android, the SIM and network countries are cheap, permissionless signals. Any app that cares can collect them on every launch.
Whether a given app does, and what it does with them, isn’t something the app will tell you. Fraud SDKs commonly include them, because they’re free to read and useful for exactly the comparison this piece is about.
What iPhones stopped telling apps
Apple went a different direction. For years, iOS apps could read the carrier name, the mobile country code and the network code through a framework called Core Telephony. In iOS 16 Apple deprecated the class that provided this, and in later versions it returns placeholder values instead of real carrier information.
So on a current iPhone, an ordinary app mostly can’t read the SIM country or the carrier the way an Android app can. It can still see the IP address on its servers, the device’s region and language settings, the time zone, and location if the user grants it. It can see the phone number if the user types it in during verification.
That makes the SIM versus IP comparison largely an Android question today. On iOS the equivalent checks lean on region settings, time zone and the verified phone number.
For operators, this has a practical consequence. The advice in this piece applies most directly to Android devices, including most cloud phones, which run Android. If you’re working with iPhones, the SIM itself is less exposed, and the other country signals carry more of the weight.
It also means that anything written about iOS carrier detection before 2023 may be out of date. Check the date on any guide you read, including this one.
What real people produce every day
The reason this comparison is useful to apps is that real phones produce a small number of predictable patterns, and most mismatches that operators create fall outside them.
The most common pattern by far is all three agreeing. A Singapore SIM, on a Singapore network, with a Singapore IP, whether on mobile data or home Wi-Fi.
The next is a traveller on roaming. A Singapore SIM, registered on a Malaysian network, with the roaming flag set. What the IP says depends on how the carrier handles roaming data, which the next section covers.
Then there’s the traveller on Wi-Fi. A Singapore SIM, maybe registered on a local network or with mobile data off, but the phone using a hotel or café connection in another country. The IP is local to wherever they are.
There’s the foreign resident. Someone living in Singapore with a local SIM, whose phone’s language and region settings are from home. The SIM, network and IP agree. Only the settings differ.
And there’s the Wi-Fi only device. No SIM at all, just an IP from whatever network it’s on. Tablets, old phones used at home, and some cloud setups look like this.
What’s notably absent is a phone on its home network, in its home country, whose traffic arrives from another country over mobile data. That combination has very few everyday causes.
Roaming data usually comes home
This is the detail that surprises most people, and it changes which mismatches look normal.
When a phone roams abroad and uses mobile data, the data usually doesn’t leave the internet from the country the phone is in. By default in most roaming arrangements, the traffic is carried back to the subscriber’s home carrier and leaves the internet there. It’s called home routing. Local breakout, where the visited network sends the traffic straight to the internet, exists but is less common for ordinary roaming.
So a Singapore SIM roaming in Malaysia on mobile data usually has a Singapore IP address. The SIM says Singapore. The network says Malaysia. The IP says Singapore.
That’s a very ordinary pattern. Anyone who has roamed and noticed that websites still showed them content from home has seen it.
This matters because it means a network country that differs from the IP country is normal for roamers, as long as the IP matches the SIM’s home. The combination that stays unusual is the one where the network and the SIM agree, meaning the phone is at home, but the IP is somewhere else entirely.
If you’re designing a phone setup, the roaming pattern tells you what a real traveller from your SIM’s country looks like, and it’s one of the few legitimate reasons for the network to disagree with the other two.
The mismatches that don’t have a story
Now the combinations that real phones rarely produce, and which operators produce all the time.
The first is the one from the opening. SIM and network both say one country, not roaming, and the IP says another. The phone is at home on its own carrier, but its traffic arrives from abroad. The main everyday cause is a VPN or proxy app running on the phone. Platforms know that, and many treat a proxied mobile device as a proxied device.
The second is a SIM from one country, a network from the same country, and an IP that belongs to a hosting company. That’s a phone at home whose traffic is coming out of a data centre. Again, a VPN or proxy is the likely explanation.
The third is a phone with a SIM that says one country and a verified phone number from another. Someone could have two SIMs, and dual SIM phones are common. But if the account’s number is a US number and the phone’s only SIM is from Indonesia, that’s another join in the story that needs explaining.
The fourth is a device with no SIM claiming, through its other signals, to be a phone on a carrier. Or a device whose network operator is a default value no real carrier uses, which is an emulator tell.
The fifth is the fleet version of any of the above. Several phones all showing the same unusual combination, like SIM in one country and IP in another, at the same time.
None of these proves anything by itself. Each one is a combination with few innocent explanations, which is exactly what makes it worth weighing.
Dual SIM, eSIM and travel data plans
Real phones have become messier in the last few years, and that mess is worth understanding, because it’s part of why apps weigh these signals carefully rather than harshly.
Dual SIM phones are common. Many people carry a personal SIM and a work SIM, or a home SIM and a travel SIM. Android exposes information per SIM slot, and an app reading the default telephony values usually gets the SIM set for data or the default one. Two SIMs from two countries in one phone is unusual but real, especially for people who live near a border or travel for work.
eSIMs make it easier still. A traveller can install a data plan for another country in a few minutes without swapping any physical card. That plan shows up as a second SIM with its own country and carrier.
Travel data eSIMs add a twist. Many of them are issued by a carrier in one country and roam on local networks everywhere else, with data routed through a hub that may sit in a third country. A traveller using one can have a SIM from one country, a network from a second and an IP from a third, all perfectly innocently.
So real users produce more combinations than the tidy list earlier suggests. That’s exactly why a single mismatch rarely decides anything. Apps that punished every odd combination would lose a lot of travellers.
What the mess doesn’t change is the fleet picture. A traveller’s odd combination is temporary and personal. A set of accounts that all show the same odd combination, permanently, with no travel pattern around it, looks like a setup rather than a trip.
If you use dual SIM phones in a fleet, check which SIM an app actually sees, and make sure the one it sees fits the account.
How apps combine the signals
It’s worth being clear about what an app does with these comparisons, because nobody outside the app knows the details and it’s easy to imagine something more dramatic than the reality.
Most apps that collect SIM and network country do it as part of a wider set of device and network signals. Those signals go into a risk score alongside the account’s age, its history, its verification status and its behaviour. A country mismatch raises the score. A clean, consistent set of signals lowers it or leaves it where it was.
What happens at a higher score varies. An extra verification step. A limit on some action, like sending money or messaging strangers. A manual review. For payment and banking apps, a block on the transaction. For social apps, perhaps nothing visible at all, just a lower level of trust that affects what the account can do later.
Country mismatches also matter more at certain moments. At signup, where a new account has no history to offset them. At login from a new device. When changing security settings or recovery details. At payment.
And they stack. A mismatch between SIM and IP, on a new account, on a device seen with other accounts, on an IP with a poor reputation, is four problems rather than one.
I can’t tell you how heavily any particular app weighs a SIM versus IP mismatch. I can tell you it’s cheap to collect, it’s collected by the kinds of fraud tools many apps use, and it has few innocent explanations in the forms listed above.
Time zone and the other quiet agreements
The SIM and IP aren’t the only country signals on a phone. Several others follow from them on a real device, and an app can compare them too.
Time zone is the biggest. Most phones set their time zone automatically from the mobile network, using time information the network broadcasts. A phone on a Singapore network with automatic time zone on reports Singapore time. If the phone’s time zone says one place, the network says another and the IP says a third, the phone has three different opinions about where it is.
Language and region settings add a softer signal. They don’t have to match, because plenty of people use their phone in a language that isn’t the local one. But they add context. A phone set to Indonesian with an Indonesian SIM in Singapore looks like a visitor or resident from Indonesia. That’s a perfectly good story, as long as the rest agrees.
Installed apps can hint at a country too. Local banking apps, transport apps, food delivery apps and carrier apps are country specific.
GPS, where an app has location permission, is the strongest location signal of all. A phone whose GPS is in one country and whose IP is in another has an obvious mismatch, unless it’s roaming with home routed data.
Keyboards and input languages, SMS sender names and even the date format in settings can all point somewhere. None of these are big on their own. On a real phone they all quietly agree, because they were set by the same person in the same place.
How operators create the mismatch
Most SIM versus IP mismatches in fleets come from a handful of setups. Knowing them makes them easy to avoid.
The most common is a proxy on a phone that already has a SIM. The phone has a local SIM for SMS or because it came with one, and the operator routes the phone’s traffic through a proxy in another country to match an account’s intended location. The SIM and network say one country. The IP says another.
A close second is using a SIM just for verification. The operator buys a SIM from one country to receive verification codes, puts it in a phone, and then uses the phone on Wi-Fi or a proxy from somewhere else. Every app that reads the SIM sees the mismatch.
Third is the cloud phone with a mismatched proxy. The phone sits in a rack in one country with a local SIM, and an app on it tunnels traffic to a proxy elsewhere.
Fourth is moving an account between devices. The account was created on a phone with one country’s SIM and is later used on a phone with another’s, while the IP stays the same. The SIM history of the account now has a jump in it.
Fifth is emulators. Default operator values, or a spoofed SIM country that doesn’t match the network or the IP, or no SIM with telephony signals claiming otherwise.
Each of these has a straightforward fix, which starts with deciding what country the identity actually lives in.
Choosing the country first
The cleanest way to keep SIM, network and IP aligned is to make one decision up front and let everything else follow.
Pick the country the identity lives in. That should be the country the account’s purpose makes sense in, the country its phone number will come from, and the country its activity will be aimed at.
Get a SIM from that country, properly registered. In many countries, including Singapore, SIM registration is tied to real identity documents, and that’s the kind of thing you should be doing properly rather than around.
Put the phone on a network in that country. For a hosted phone, that means the phone physically sits there and attaches to a local carrier.
Let the phone’s own mobile data carry its traffic where you can. That way the IP is the carrier’s own address in the same country, and the SIM, network and IP agree without anything being configured.
If you do need a proxy for some reason, choose one in the same country and ideally on the same carrier the SIM is from, so the IP’s carrier and country match the SIM’s.
Set the time zone to automatic. Leave language and region consistent with the person the account represents.
This is less work than trying to reconcile mismatched pieces afterwards, and it produces the most common pattern real phones produce, which is all three agreeing.
When an account needs a different country
Sometimes the account genuinely needs to look like it’s in a country other than where the phone is. The honest options are limited, and it’s worth knowing what each one looks like to an app.
The cleanest is to have the phone in that country. A hosted phone in the target country, with a local SIM, on a local network. Nothing to reconcile.
The next is to use a phone with no SIM on a connection in the target country. The app sees no SIM country and no network country, just the IP. That’s how a Wi-Fi only tablet looks. It gives the app less to compare, which is not the same as passing a comparison. Some apps treat a phone with no SIM as lower trust, and verification by SMS still needs a number from somewhere.
The roaming pattern is the third. A SIM from the account’s home country, roaming on a network elsewhere, with data home routed back to the SIM’s country. That’s a traveller, and it’s consistent. But it’s a temporary state for real people. A phone that roams permanently for months looks like something other than a traveller.
What doesn’t work well is combining a SIM from one country with a proxy in another while the phone sits at home. That’s the pattern with the fewest innocent explanations.
Whatever the choice, the account’s phone number should fit it. A verification number from the same country as the SIM, or at least a plausible one for the person the account represents.
A worked example across three phones
Here’s a hypothetical fleet of three Android phones, set up by someone who hasn’t thought about this layer, to show how the checks play out.
Phone one has a Singapore SIM, sits in Singapore and uses its own mobile data. SIM, network and IP all say Singapore. The IP belongs to the SIM’s carrier. The time zone is automatic. This phone produces the most common pattern there is.
Phone two has a Singapore SIM, sits in Singapore, and runs a proxy app that sends its traffic through an address in the United States, because the account on it is supposed to be American. The SIM says Singapore, the network says Singapore, the roaming flag is off, and the IP says the United States. The time zone, set automatically by the network, says Singapore. The account was verified with a US number. That’s a phone at home, on its own carrier, claiming to be in another country, with a phone number from a third story. Several mismatches, none with an easy innocent explanation.
Phone three has no SIM and runs on Wi-Fi through a residential connection in Singapore. There’s no SIM country and no network country. The IP says Singapore. The account on it was verified with a Singapore number. It looks like a Wi-Fi only device, which gives an app less to go on, and nothing contradicts anything.
The fix for phone two depends on what the account needs. If it genuinely needs to look American, the honest version is a phone in the United States on a US SIM. If it doesn’t, drop the proxy and let the phone be what it is. What doesn’t work is keeping the Singapore SIM and the American exit together and hoping nobody compares them.
Checking what your phone reports
You can see exactly what an app would see, and you should, especially on any phone you didn’t set up yourself.
On Android, install a SIM or device information app from the store. Look for the SIM country, the SIM operator, the network country, the network operator and the roaming status. Write all five down.
Open the phone’s browser on the connection the account actually uses and load a “what is my IP” page. Note the IP, its country and its carrier or organisation. If the account’s traffic goes through a proxy app, test with the proxy app running.
Check the time zone in settings and whether it’s automatic.
Now compare. SIM country, network country and IP country should match, or form the roaming pattern where the network differs but the IP matches the SIM’s home. The IP’s carrier should ideally be the SIM’s carrier, or at least a consumer carrier in the same country. The time zone should match the network.
If you run several phones, repeat the check on each and look for a shared oddity across them.
For iPhones, check the region, language and time zone settings, and the IP. The SIM itself matters less to apps there, but the phone number used for verification still does.
What cloud phones do and don’t solve
Cloud phones built on real handsets with real SIMs make this comparison easy to pass, when they’re set up simply. The phone has a SIM from the country it’s in, it attaches to a local network, and its mobile data leaves through that carrier. All three countries agree because the phone really is where it says.
That simplicity is also the limit. A cloud phone in Singapore is a Singapore phone. It’s the right tool for identities that live in Singapore, or for identities whose story fits a phone there. It’s the wrong tool for pretending to be in another country, and adding a foreign proxy to it creates the exact mismatch this piece describes.
Cloud phones built on emulators or virtualised Android often have no real SIM at all, or report default telephony values. Those fail the comparison in a different way, since the telephony signals themselves don’t look like a real carrier.
Before renting any hosted phone, ask what SIM it has, which carrier, which country, and whether its traffic goes out over that SIM’s data or over something else. Then check it with the steps above.
The honest limit
Keeping SIM, network and IP in agreement removes one of the cheapest checks an Android app can run. It doesn’t make an account trustworthy on its own, and it doesn’t excuse what an account does.
I can tell you which signals ordinary Android apps can read without permission, how roaming data is usually routed, and which combinations real phones produce. I can’t tell you which apps compare them today or how much weight each app gives the result. Those are internal decisions that change without notice. Apple has already changed what iPhone apps can see once, and either platform could change again.
What stays true is that a real phone set up by a real person in a real place produces signals that agree with each other without anyone trying. That’s the pattern to match, and the simplest way to match it is to have the phone genuinely be where its SIM and its IP say it is.
I run Singapore mobile proxy and cloud phone farms myself, with local SIMs on local carriers, so the SIM, the network and the exit IP on those phones all say Singapore because that’s where they are. If you want the rest of the mobile and location picture, start on the Multi Account Ops home page.
Get new guides and videos first — join the Telegram channel.