Number Portability (MNP): Why Your Carrier Data Goes Stale
Number Portability (MNP): Why Your Carrier Data Goes Stale
TL;DR
- Mobile Number Portability (MNP) lets a subscriber keep their phone number when switching to a new carrier.
- Once a number is ported, the original carrier no longer serves it — but any system that stored the old carrier as “current” doesn’t know that.
- A number can be ported more than once, so even a six-month-old carrier record can already be wrong.
- Carrier data only stays accurate if it’s checked against a live MNP or HLR query at the time you use it, not stored once and reused.
- This is why a phone number’s carrier field in a CRM or marketing list is one of the fastest-decaying data points in the whole record.
A phone number’s area code tells you almost nothing about who currently provides service to it, and that’s by design. Mobile Number Portability (MNP) exists specifically so people can switch carriers without losing their number. That consumer convenience is also the exact mechanism that makes stored carrier data go stale faster than almost any other field in a contact record.
Table of Contents
- What Mobile Number Portability Is
- How the Porting Process Works
- Why This Makes Carrier Data Go Stale
- MNP Lookup vs HLR Lookup: What’s the Difference
- What This Means for SMS Routing and Validation
- Frequently Asked Questions
What Mobile Number Portability Is
Mobile Number Portability allows a subscriber to switch from one mobile carrier to another while keeping the same phone number. Before MNP existed in a given country, changing carriers meant changing numbers — which kept people locked into a provider just to avoid the hassle of notifying every contact of a new number.
MNP removed that friction. The tradeoff is that a phone number’s area code and original carrier prefix tell you only where the number was first issued, not who serves it today.
How the Porting Process Works
Every porting transaction involves two carriers and a central database.
| Role | Description |
|---|---|
| Donor operator | The carrier that currently serves the number before the port |
| Recipient operator | The carrier the subscriber is switching to |
| Number Portability database | The central registry (NPAC in the US, similar systems elsewhere) that records which carrier currently owns each ported number |
When a port completes, the donor operator’s records update to show the number has left, and the central database updates to reflect the new serving carrier. Any external system that queries that central database — rather than relying on a cached or purchased carrier list — gets the current answer. Any system that doesn’t query it keeps showing the carrier as it was issued, indefinitely.
Why This Makes Carrier Data Go Stale
A number can be ported more than once. A phone number originally issued by one carrier might be ported to a second carrier, then ported again to a third a year later. Each port is a fresh opportunity for stored data to fall out of sync with reality.
This is different from most other contact-record fields. A mailing address might go stale when someone moves, which happens occasionally. A phone number’s carrier field can go stale the moment a subscriber decides a competitor has a better plan — an event with no fixed schedule and no notification to anyone outside the two carriers involved.
The practical consequence: a CRM field that says “Carrier: [Provider A],” populated from a one-time lookup eight months ago, may already describe a carrier that hasn’t served that number in six of those eight months.
MNP Lookup vs HLR Lookup: What’s the Difference
These two lookups are related but answer different questions.
| Lookup type | What it tells you | What it doesn’t tell you |
|---|---|---|
| MNP lookup | Whether a number has been ported, and to which carrier | Whether the number is currently active or reachable |
| HLR lookup | Current network status, including porting status plus whether the number is active, roaming, or disconnected | — (HLR queries typically include MNP resolution as part of the result) |
In practice, an HLR lookup is the more complete check, since it resolves current carrier ownership and active status in a single query rather than requiring a separate MNP-only check.
What This Means for SMS Routing and Validation
For any business sending SMS, WhatsApp, or voice traffic at volume, stale carrier data has a direct cost. Messages routed based on outdated carrier information can hit unnecessary interconnect fees, get misrouted to the wrong network, or simply fail to deliver — all while the underlying number is perfectly valid and reachable on its actual current carrier.
This is why carrier and line-type data needs to be checked at the point of use rather than stored once and reused across campaigns. A live carrier lookup run against a current list resolves the actual serving network at send time, not whatever carrier happened to own the number when it was first added to a database. For lists that haven’t been checked in months, re-running validation across the full list before a campaign catches both the ported numbers and any that have gone inactive in the same pass.
Frequently Asked Questions
What is mobile number portability?
Mobile Number Portability (MNP) is the ability for a phone subscriber to keep their existing number when switching to a different mobile carrier, separating the number from any single provider.
How do I check if a number has been ported?
An MNP lookup or HLR lookup queries the current number portability database to identify whether a number has been ported and which carrier currently serves it, rather than relying on the carrier implied by the number’s original prefix.
Why does my carrier lookup show the wrong carrier?
This usually happens when the carrier data being referenced was stored from a past lookup or a static prefix-based list, rather than queried live. Since numbers can be ported at any time, only a current, live lookup reflects the actual serving carrier.
What is the difference between MNP lookup and HLR lookup?
An MNP lookup confirms whether a number has been ported and to which carrier. An HLR lookup typically includes that same porting resolution plus additional status information, such as whether the number is currently active, roaming, or disconnected.
How often should carrier data be re-checked?
Carrier data should be re-checked at or near the time it’s used — immediately before an SMS campaign or routing decision — rather than stored and reused, since porting events happen continuously and without any fixed schedule.
Conclusion
Mobile Number Portability is a consumer protection that happens to be one of the most common reasons stored carrier data turns out to be wrong. A number can move carriers more than once, with no external notification, which means any carrier field that isn’t re-verified at the point of use is a guess dressed up as a fact. For SMS routing, carrier-based segmentation, or basic list hygiene, the fix is the same: query current network data when you need the answer, rather than trusting a value that was correct only on the day it was first recorded.