LATA (Local Access and Transport Area) is one of roughly 200 geographic regions the US telephone network was divided into at the 1984 AT&T breakup. LATAs defined where local phone companies could carry calls themselves and where long-distance carriers had to take over — and the boundaries still appear in routing data, intercarrier billing, and every enhanced LRN lookup today.
Where LATAs Came From
When the Bell System was broken up in 1984, the consent decree split the telephone business in two: the Regional Bell Operating Companies (RBOCs) kept local service, and AT&T (plus competitors like MCI and Sprint) got long distance. LATAs were the dividing lines. An RBOC could carry a call within a LATA (intraLATA); any call crossing a LATA boundary (interLATA) had to be handed to an interexchange carrier (IXC).
Each LATA has a 3-digit code (sometimes 5 digits for later additions): 132 is New York Metro, 722 covers much of Chicago, 730 is Minnesota. Most states contain several LATAs; some LATAs cross state lines.
Do LATAs Still Matter?
The Telecommunications Act of 1996 and the rise of wireless and VoIP dissolved most of the regulatory restrictions, but LATAs persist as infrastructure facts:
- Intercarrier compensation: access charges and settlement rates between carriers are still classified intraLATA vs. interLATA.
- Tariffs and interconnection agreements: many are still written in LATA terms.
- Routing databases: NPAC records, LERG data, and LRN lookups all carry LATA codes.
- Least-cost routing: wholesale voice pricing engines use LATA + OCN + rate center to price call legs.
LATA vs. Rate Center vs. Area Code
| Unit | Approx. Count (US) | Purpose |
|---|---|---|
| LATA | ~200 | Regional access/transport boundary from the AT&T breakup; intercarrier billing classification |
| Rate center | ~18,000 | Local billing area; governs local calling and porting eligibility |
| Area code (NPA) | ~350 | Numbering resource; does not align with LATA or rate center boundaries |
The hierarchy is loose but useful: a LATA contains many rate centers, and a rate center belongs to exactly one LATA. Area codes overlap both freely — one area code can span multiple LATAs and vice versa.
LATA in LRN Dips and Number Portability
Every LRN dip resolves a dialed number to the switch currently serving it, and the associated record carries the LATA and rate center. Two operational points:
- Porting stays within the LATA. Because number portability is bound to the rate center, and rate centers nest inside LATAs, a ported number's LATA never changes. The LRN assigned by the new carrier belongs to the same LATA.
- Billing classification follows the LATA pair. Carriers compare the originating and terminating LATAs (via the LRN, not the dialed number) to classify traffic for access billing. Using the dialed number instead of the LRN misclassifies ported traffic — a real revenue leak for carriers handling wholesale voice.
LATA in VRI API Responses
VRI returns the LATA with every enhanced LRN lookup, alongside the rate center, OCN, and current carrier:
curl -X POST https://verirouteintel.com/api/v1/lrn \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"phone_number": "13364086644", "include_enhanced_lrn": true}'
# Response
{
"phone_number": "13364086644",
"lrn": "13364086644",
"enhanced_lrn": {
"carrier": "Verizon Wireless",
"carrier_type": "WIRELESS",
"ocn": "6006",
"lata": "424",
"rate_center": "WINSTN SAL",
"state": "NC"
}
}Because the lookup resolves through the LRN, the lata field is correct for ported numbers — it reflects the serving switch's LATA, which is what intercarrier billing and routing engines need.
Get LATA, rate center, and OCN for any US phone number. Real-time LRN lookup with enhanced routing data. $0.0009/lookup, no minimum.
Get Free API Key