LRN Lookup for Telecom Carriers — Real-Time Number Portability Data

For telecom carrier ops and intercarrier billing teams who need authoritative LRN data without maintaining NPAC infrastructure. Number portability is foundational to how calls route and how money moves between carriers. Get that LRN wrong—or rely on stale data—and you misroute calls, miscalculate access charges, and spend hours in billing disputes you could have avoided.

What Telecom Carriers Need from LRN Data

  • Accurate LRN for every ported number — the 10-digit routing number that drives SS7 call setup and determines the terminating switch
  • SPID and OCN — to identify the current owning carrier for access charge calculations and intercarrier settlements
  • Port completion timestamps — to know when a port actually activated, not just when it was ordered
  • High query throughput — billing reconciliation runs can involve millions of CDR lookups against a tight settlement deadline

How the VeriRouteIntel LRN API Works

The VeriRouteIntel LRN API aggregates NPAC data and carrier-reported port activity into a single REST endpoint. A lookup request returns a full portability record in under 100ms (median): 

GET /v1/lookup?number=12125550100
Authorization: Bearer {api_key}

{
  "number": "12125550100",
  "lrn": "12125550000",
  "spid": "1234",
  "ocn": "2773",
  "carrier_name": "Example Carrier LLC",
  "line_type": "wireless",
  "ported": true,
  "activated_at": "2026-03-14T09:22:11Z",
  "original_carrier": "Original Wireline Co"
}

The same endpoint handles wireline, wireless, and VoIP numbers uniformly. For batch reconciliation, the /v1/batch endpoint accepts up to 10,000 numbers per request.

Use Cases for Carrier Operations

Intercarrier Billing and Access Charge Calculation

Interstate and intrastate access charges depend on correctly identifying the terminating carrier for each call. A ported number routes to the new carrier's switch, but billing must reflect the current carrier of record—not the original LSOC. Stale LRN data produces settlement errors that take weeks to unwind.

With VeriRouteIntel, billing teams run a batch LRN lookup across their CDRs before each settlement cycle. The spid and ocn fields return the authoritative carrier-of-record at the time of the query, providing a documented data trail for dispute resolution.

Real-Time Call Routing

SS7 call setup for ported numbers requires the correct LRN before IAM transmission. Carriers without fast, accurate LRN lookups either cache NPAC data locally (with staleness risk) or make expensive real-time NPAC queries (with latency and infrastructure cost).

VeriRouteIntel's sub-100ms latency supports inline routing decisions without adding meaningful delay to call setup. The API returns the LRN directly—no translation or local table lookup required before populating the routing digit.

Port Completion Verification

Number ports have two states that matter operationally: ordered and activated. A port that's been ordered but not yet activated will fail if you route traffic to the new carrier before NPAC confirms completion. The window between order and activation can be minutes or hours, and it varies by carrier.

The activated_at field returns the ISO 8601 timestamp of when NPAC recorded the port as active. Always check activated_at before routing traffic to a newly ported number—routing before activation results in failed calls, re-attempt costs, and a poor experience for the subscriber who just ported.

Why Carriers Choose VeriRouteIntel

No NPAC Subscription or LSMS Infrastructure Required

Maintaining a NPAC LSMS mirror costs six figures annually in subscription fees, hardware, and engineering time. VeriRouteIntel eliminates that overhead entirely—you make an API call and get the data.

Normalized Data Across All Number Types

Wireline, wireless, and VoIP numbers return the same response schema. No special handling per number type.

Timestamped Port Activation

The activated_at field surfaces data that most portability vendors omit or only provide in raw NPAC XML format. For carrier ops, this is the difference between proactive routing gates and reactive trouble tickets.

Pricing Built for Carrier Volumes

At $0.0005 per lookup, a carrier running 5 million monthly lookups pays $2,500/month—a fraction of LSMS maintenance costs.

Tier Volume Price/Lookup
Standard Up to 10M/month $0.0005
Enterprise 10M+ /month Contact for quote

Integration for Carrier Engineering Teams

The REST API authenticates via Bearer token with a static API key. No OAuth flow, no session management. Integration typically takes under a day for a carrier already running HTTP-based lookups. 

# Single lookup
curl -s "https://api.verirouteintel.com/v1/lookup?number=12125550100" \
  -H "Authorization: Bearer $VRI_API_KEY"

# Batch lookup (up to 10,000 numbers)
curl -s -X POST "https://api.verirouteintel.com/v1/batch" \
  -H "Authorization: Bearer $VRI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"numbers": ["12125550100", "18005551234", "13105559876"]}'

Frequently Asked Questions

What is an LRN lookup and why do telecom carriers need it?
An LRN (Local Routing Number) lookup queries NPAC data to find the current routing number for a ported telephone number. Carriers need this to correctly route calls in SS7 networks, calculate accurate intercarrier access charges, and verify port completion before accepting traffic. Without accurate, real-time LRN data, carriers misroute calls and generate incorrect intercarrier billing.
How does VeriRouteIntel differ from maintaining a local NPAC mirror?
Direct NPAC access requires a NPAC subscription, SOA/LSMS infrastructure, and ongoing database maintenance. VeriRouteIntel aggregates NPAC data via API—no infrastructure, no subscription, and a normalized response that includes the activated_at timestamp not readily available from raw NPAC XML.
What fields does the LRN API return?
Each response includes: lrn, spid, ocn, carrier_name, line_type, ported, activated_at, and original_carrier. Enterprise tiers return port_status for in-flight port orders.
What is the activated_at field and how should it be used?
activated_at is an ISO 8601 timestamp of when NPAC recorded the port as active. Before routing traffic to a ported number, check that activated_at is not null and is not in the future. Routing before activation results in failed calls during the porting window.
What is the price per LRN lookup?
Standard carrier tier: $0.0005 per lookup. Enterprise volume pricing is available for carriers running 10M+ lookups per month. No monthly minimums and no NPAC subscription fees.
Does the API support both real-time and batch lookups?
Yes. The single-number endpoint returns results in under 100ms (median) for real-time call routing. The batch endpoint handles up to 10,000 numbers per request for billing reconciliation and CDR enrichment workflows.

Carrier Pricing Available — Request a Quote

LRN infrastructure is a cost center. VeriRouteIntel turns it into a line item you control. Request carrier pricing for your monthly volume, or view the LRN API docs to get your 10 free lookups.

Get Free API Key View Pricing