What is MNP?
MNP stands for Mobile Number Portability: keeping your mobile number when you change network. An MNP lookup identifies the original network and the current network after a number has been ported. It helps businesses route calls and SMS using current network information; it does not prove the number is active or identify the person using it.
If you run a dialler or manage call routing in the UK, MNP explains why a number may not be on the network you think it is. An MNP lookup checks a mobile number against porting records and returns the network it sits on today, not the one it was first issued to.
A number prefix can indicate its original allocation, but it cannot reliably tell you the current network after porting. Use a mobile number portability lookup when current carrier information matters to your dialler, SMS routing or CRM reporting.
Mobile Number Portability is the right to keep your mobile number when you change provider. In the UK it works through a switching code: you text PAC to 65075, your current provider sends the code back within a minute, and your new provider completes the transfer within one working day. The number stays the same. The network behind it changes completely.
This is regulated by Ofcom and has been standard practice for years. Millions of UK mobile numbers now sit on a different network from the one that first issued them.
Here is the part most people miss. UK mobile numbers were originally allocated to networks in blocks, so a prefix used to indicate the operator. Portability broke that link permanently. A number might have started life on one network and now sit on a completely different one, with nothing in the digits to tell you.
The UK also uses onward routing, sometimes called indirect routing, for ported mobiles. Calls go to the original network first, which passes them on to the network the customer actually uses. That extra hop is invisible to your customer, but it is not invisible to your call routing or your carrier bill.
If your dialler is making assumptions about the network based on the number range, those assumptions are wrong for every ported number in the list.
Least cost routing works by picking the cheapest path to the destination network. Feed it the wrong network and you are optimising against a fiction. Calls take the long way round, and the rate you thought you were paying is not the rate you get.
Numbers that route badly connect slowly or fail outright. On a predictive dialler, connection delay is the difference between a live conversation and a prospect who says hello twice and hangs up.
Every dud attempt is a few seconds of agent life and a small dent in contact rate. Multiply that across a 40-seat floor running thousands of dials a day and it becomes a real number on a real spreadsheet.
Most diallers and CRMs pick up network information once, when the record is created. From that moment it decays. Nobody tells your CRM that a customer switched network last March. Porting is one of the quieter contributors to data decay, because nothing about the record looks wrong. The number is still valid. It is still live. It just is not where your system thinks it is.
Diallers and carrier platforms often pick a route, rate or gateway by destination network. When that choice is based on the original range holder, ported numbers go down the wrong route. An MNP lookup gives your routing rules the network the number is actually on, so calls and SMS take the path you priced for.
Connect rates, call costs and campaign results are often split by network. If part of your list carries the wrong network, carrier invoices will not reconcile with your own data and network-level reports will point you at the wrong problem.
Want the current network for every number? Run your list through Data Soap's MNP lookup.
An MNP lookup queries network information about a mobile number's original allocation and its current network after porting. Data Soap's documented MNP result contains original and ported network objects, with networkName, mcc and mnc values. Use the returned fields and any errors to interpret the result, rather than guessing from the prefix.
Illustrative sample only: Network A and Network B below are fictional labels. This is an explanation of the result, not a live lookup or a claim about a particular phone number.
| Item | Example | What it means |
|---|---|---|
| Original network | Network A | The network originally allocated the number range. |
| Current (ported) network | Network B | The network now serving the number after a transfer. |
| Existing CRM carrier | Network A | A stored value that needs reviewing against the new result. |
| Next action | Record Network B and the lookup date | Use current network data in routing and reporting rules where supported. |
The customer kept the same phone number when moving from A to B. A prefix-based check might still suggest A; the portability result shows B. Update the current-network field while retaining the original allocation separately if useful. If the response is missing or inconclusive, review the error or retry guidance instead of overwriting a known carrier with a guess.
This example does not establish whether the handset is on, whether a call will connect, who controls the number or whether marketing contact is permitted. For the exact response structure, see the MNP API documentation.
It is a silent check. Nothing rings, and the person holding the phone never knows.
What an MNP lookup does not tell you is whether the number is live. A disconnected number can still return network information. For mobile-network status, use an HLR lookup and interpret its status and any errors. Network checks are a snapshot, and a positive result cannot guarantee that somebody will answer or that an SMS will be delivered.
For a step-by-step explanation of formatting checks, network status and what validation can prove, see how to check if a phone number is real and active. It also explains why an inconclusive result needs review and why an active number does not establish ownership or marketing permission.
| MNP lookup | HLR lookup | |
|---|---|---|
| Answers the question | Which network is this number on now? | What mobile-network status is available for this number? |
| Returns current network | Yes | Yes |
| Returns original and ported network objects | Yes, in the documented MNP response | Use MNP when you need explicit portability detail |
| Provides mobile-network status information | No; network identity alone does not confirm activity | Yes, subject to the returned status and network response |
| Guarantees a person will answer or receive a message | No | No |
| Best for | Routing accuracy, carrier cost control, network-based segmentation | Cleaning a list before you dial or send |
| Typical use | Ongoing routing intelligence | Pre-campaign list validation |
| Data Soap service | MNP lookup | HLR lookup |
Use MNP for portability detail and current-network routing or reporting. Use HLR to assess mobile-network status before a campaign. Where your workflow needs both, request both checks and keep their results separate. For more on interpreting mobile validation, read our HLR lookup guide.
Use Data Soap's portal for a file of existing records, or integrate the API when you need checks within your CRM or dialler workflow.
View Data Soap's MNP lookup service or create an account to run your checks.
For an automated workflow, follow the Validation API documentation for MNP checks. Set up an API token in your account, include Mnp in the request's checks array, and map the original and ported network values back to the correct CRM record.
Store a lookup timestamp and handle errors before changing routing data. A syntax fallback confirms only format or range information; it is not a successful MNP result. Follow the documented retry guidance for temporary failures, and avoid unnecessary duplicate submissions because each lookup can incur a charge. Request HLR separately when your workflow also needs mobile-network status.
If your data has never had a proper clean, MNP is one piece of a bigger job. Our plain-English guide to data cleaning covers the rest of it.
Worth adding: keeping contact data accurate is not only a commercial matter. The UK GDPR accuracy principle expects personal data to be accurate and, where necessary, kept up to date. Routine validation is part of showing you take that seriously.
There is no single published figure for total ports per year, but switching is routine and Ofcom's text-to-switch rules deliberately made it easier. Any list more than a few months old will contain numbers that have moved network since you captured them, and older lists will contain a lot of them.
No. It returns original and ported network information. Use HLR for mobile-network status, review any inconclusive response, and remember that neither check guarantees a person will answer.
Yes. You can request an MNP check through Data Soap's Validation API as part of your CRM, web-form or dialler workflow. Response times depend on the network and request; build in handling for timeouts and temporary errors. See the API integration instructions.
No. Both MNP and HLR lookups are silent network queries. No call, no text, no notification.
MNP means mobile number portability: the right to keep your mobile number when you change network. An MNP lookup, sometimes called an MNP checker, shows which network a number is on now and whether it has been ported.
Run both when you need explicit portability information for routing as well as mobile-network status for list validation. Use the returned fields to decide what action to take, keep check dates, and review uncertain results. The right checks depend on your campaign and number types; marketing permission and suppression checks remain separate.
A mobile prefix can reflect an original allocation, while the current network may have changed. MNP helps you keep those two values separate and maintain more useful routing and reporting data. Pair it with HLR when you also need mobile-network status, without treating either result as proof of ownership, marketing permission or a guaranteed connection.
Check which network your numbers are on with Data Soap's MNP lookup, or run an HLR lookup to find dead numbers before you dial.
£100 of credits for £4.99. New customers, once.