Local Number Portability (LNP)

What Is LNP?

Local Number Portability (LNP) is the technical and regulatory framework that allows telephone subscribers to keep their existing telephone number when they switch carriers, move between service types (wireline to wireless, or to VoIP), or in some cases when they change their physical location within a rate center.

Before LNP, your phone number was permanently tied to the physical line and the carrier that provided it. Switching from AT&T to MCI meant getting a new phone number — a significant deterrent to competition. LNP broke this lock-in, enabling genuine carrier competition and consumer choice.

History: The Telecom Act of 1996

LNP was mandated by the Telecommunications Act of 1996, which required telephone carriers to implement number portability as a condition of operating in the US market. The FCC specified that:

• Local wireline-to-wireline porting must be supported by all carriers
• Wireline-to-wireless porting (taking a home number to your cell phone) became required in 2003
• Wireless-to-wireline porting was also mandated, allowing cell numbers to be moved to landlines
• VoIP providers (under the Vonage decision and subsequent orders) were integrated into the porting framework

The technical implementation of LNP required building a new national database infrastructure that didn't previously exist. The FCC designated a Number Portability Administration Center (NPAC) to manage the central database. Telcordia (now Ericsson) won the original NPAC contract. iconectiv currently operates the NPAC under an FCC contract.

The NPAC Database

The NPAC (Number Portability Administration Center) is a centralized national database containing every ported telephone number in the US. Whenever a phone number is ported from one carrier to another, a record is created or updated in the NPAC identifying the new serving carrier (the "porting-in" carrier, called the NPAC LSO or LSMS).

Each carrier connects to the NPAC via a Local Service Management System (LSMS). The LSMS is the carrier's local copy of porting data — it downloads updates from the NPAC continuously. When a call arrives at a carrier's switch and needs to be routed, the switch queries its LSMS to check if the called number has been ported. If it has, the call is forwarded to the serving carrier rather than following the default NPA-NXX routing.

Key NPAC data elements for each ported number:

The Location Routing Number (LRN) is a critical technical concept. Rather than routing ported calls based on the subscriber's actual number (which would change with every port and require massive routing table updates), the PSTN routes based on the LRN — a stable number assigned to each switch. The originating switch looks up the LRN for the called number, then routes the call to that LRN. The receiving switch then maps the LRN to the actual subscriber.

The Porting Process

When a subscriber wants to port their number to a new carrier, a standardized process takes place:

Porting Timelines

How to Detect Ported Numbers

Detecting whether a number has been ported — and to what carrier — requires querying either the NPAC directly (requires carrier authorization) or using a number lookup service that integrates NPAC data. Here's how different lookup methods work:

• LERG-based lookup: Uses the Telcordia LERG database to find the NPA-NXX assignment. Returns the original carrier for that number block — does not account for porting. This is the "assigned carrier" result.
• NPAC/live query: Queries the NPAC in real-time or near-real-time to check if a specific number has been ported. Returns the current serving carrier post-port. More accurate but requires carrier-level data access.
• Hybrid lookup: Many commercial services (including foneinfo.us) cross-reference LERG data with regularly refreshed NPAC data to provide both the assigned carrier and, where porting data is available, the current serving carrier.

The practical result: when you look up a number and see "AT&T" as the carrier, that likely means AT&T is the assigned carrier for that NPA-NXX block. But if the number was ported to T-Mobile last year, the most current data source should reflect that. Freshness of the underlying data matters significantly.

STIR/SHAKEN and Its Relation to LNP

STIR/SHAKEN (Secure Telephone Identity Revisited / Signature-based Handling of Asserted information using toKENs) is a framework for authenticating caller ID — specifically to combat spoofed caller ID used in robocall campaigns. It's related to LNP in important ways:

STIR/SHAKEN works by having the originating carrier digitally sign a call's caller ID information using a certificate tied to that carrier's identity. When the call arrives at the destination, the terminating carrier can verify the signature to confirm the calling number was legitimately placed by the carrier that signed it.

The connection to LNP: a carrier can only provide a high-confidence ("A-level") attestation for a call if it can verify that it is the legitimate serving carrier for the calling number. For ported numbers, this requires the carrier to know that the number was ported to their network — i.e., to have accurate NPAC records. Carriers without complete porting data may be forced to provide lower-confidence attestations, flagging calls as potentially spoofed even when they're legitimate.

This is one reason why keeping NPAC records accurate and current is not just a routing issue but increasingly a call quality and anti-fraud issue. Mismatch between who "owns" a number in NPAC and who's actually generating calls from it is a red flag that sophisticated carrier anti-fraud systems watch for.

Why Carrier Lookup Results May Differ from Reality

Given everything above, here's a summary of why a carrier lookup result might not match the carrier a subscriber believes they have: