What Is a LATA?
Local Access and Transport Areas — the 196 geographic regions that define the boundaries of local telephone service in the United States, created by the 1984 AT&T divestiture.
What Is a LATA?
A LATA (Local Access and Transport Area) is a geographic region of the United States within which a local telephone company (ILEC) may provide telephone service without involving a separate long-distance carrier. LATAs were created as part of the settlement agreement that broke up AT&T's Bell System on January 1, 1984 — commonly called the "Modified Final Judgment" (MFJ) or the AT&T Consent Decree.
There are 196 LATAs in the United States, plus additional LATAs in US territories (Puerto Rico, the US Virgin Islands, Guam, American Samoa, and the Northern Mariana Islands). Each LATA corresponds roughly to a metropolitan statistical area, a group of adjacent counties, or a region with strong economic and social ties.
Why Were LATAs Created?
Before the 1984 AT&T breakup, AT&T controlled both local telephone service (through its Bell Operating Companies) and long-distance service (through AT&T Long Lines). This vertical integration meant AT&T could effectively prevent competitors like MCI and Sprint from competing in the long-distance market by controlling the local network access points.
Federal Judge Harold Greene, who oversaw the AT&T divestiture, created LATAs as a structural solution. The terms of the breakup required:
- The seven newly independent Bell Operating Companies (Ameritech, Bell Atlantic, BellSouth, NYNEX, Pacific Bell, Southwestern Bell, US West) could only provide telephone service within LATAs
- Calls that crossed LATA boundaries (inter-LATA calls) had to be carried by a separate long-distance carrier — AT&T, MCI, Sprint, or others
- This created a clear structural separation between local and long-distance service, enabling long-distance competition
The Telecommunications Act of 1996 later relaxed some of these restrictions, eventually allowing the Bell companies to provide long-distance service once they demonstrated sufficient competition in their local markets. But the LATA boundaries themselves remain as fundamental geographic units in US telecom routing and regulation.
Intra-LATA vs. Inter-LATA Calls
Intra-LATA Calls
Calls that begin and end within the same LATA. Originally, only the ILEC (Bell company or independent) could carry these calls. After 1996, CLECs and other carriers can compete for intra-LATA traffic. Intra-LATA calls are typically billed as local or regional calls.
Inter-LATA Calls
Calls that cross a LATA boundary — commonly called "long distance." Before 1996, only IXCs (inter-exchange carriers like AT&T, MCI, Sprint) could carry these. The call leaves the originating ILEC's network at an access tandem, is handed off to the chosen IXC, and is delivered to the terminating ILEC in the destination LATA.
The distinction matters less for consumers today — flat-rate calling plans and VoIP have made per-call LATA boundaries largely invisible. But for carrier routing, billing, and regulatory purposes, LATA boundaries remain important reference points. When you see a LATA number in a phone lookup result, it identifies the geographic routing region for that number.
LATA Boundaries and Area Codes
LATAs do not map directly onto area codes (NPAs). A single LATA may contain multiple area codes (for example, the Chicago LATA contains 312, 773, 847, 630, and others). Conversely, a single area code is typically contained within one LATA, though overlay area codes in large LATAs can complicate this.
The important point is that a LATA boundary, not an area code boundary, determines whether a call is "local" or "long distance" for regulatory and routing purposes. Two numbers with the same area code could be in different LATAs if they're near a LATA border — though this is unusual because LATA boundaries were generally drawn along county lines and MSA boundaries.
Major US LATAs — Reference Table
| LATA # | Region / City | State | Key Area Codes |
|---|---|---|---|
| 132 | New York City (Manhattan / Bronx / Brooklyn / Queens / Staten Island) | NY | 212, 718, 917, 347, 646, 929 |
| 220 | Chicago | IL | 312, 773, 630, 847, 708, 224, 331, 872 |
| 730 | Los Angeles | CA | 213, 310, 323, 424, 818, 626, 747, 661 |
| 552 | Dallas / Fort Worth | TX | 214, 972, 469, 817, 682 |
| 920 | Houston | TX | 713, 281, 832, 346, 936 |
| 228 | Philadelphia | PA | 215, 267, 445, 610, 484, 835 |
| 438 | Atlanta | GA | 404, 678, 470, 770, 762 |
| 740 | San Francisco / Oakland / San Jose | CA | 415, 510, 408, 650, 669, 628 |
| 278 | Washington DC / Northern Virginia / Maryland | DC/VA/MD | 202, 703, 571, 301, 240, 443 |
| 122 | Boston / Eastern Massachusetts | MA | 617, 781, 508, 978, 351, 857 |
| 960 | San Antonio | TX | 210, 726 |
| 762 | San Diego | CA | 619, 858, 442 |
| 350 | Detroit / Southeast Michigan | MI | 313, 734, 248, 947, 586 |
| 480 | Minneapolis / St. Paul | MN | 612, 651, 763, 952 |
| 476 | Miami / Southeast Florida | FL | 305, 786, 954, 954 |
| 472 | Tampa / St. Petersburg / Central Florida | FL | 813, 727, 407, 689, 321 |
| 668 | Seattle / Western Washington | WA | 206, 253, 425, 360, 564 |
| 656 | Portland / Western Oregon | OR | 503, 971 |
| 528 | Denver / Colorado Front Range | CO | 303, 720, 719 |
| 434 | Charlotte / Western Carolinas | NC | 704, 980, 743 |
| 936 | Phoenix / Central Arizona | AZ | 602, 480, 623, 520 |
| 224 | Buffalo / Western New York | NY | 716, 585 |
| 236 | Pittsburgh / Western Pennsylvania | PA | 412, 724, 878, 814 |
| 330 | Cleveland / Northeast Ohio | OH | 216, 440, 330, 234 |
LATAs and Number Portability
LATA boundaries play a role in number portability (LNP) rules. The core rule is that a telephone number can generally only be ported to carriers that serve the same rate center — the specific geographic subdivision within a LATA. Numbers cannot typically be ported across LATA boundaries while retaining the same NPA-NXX, because the number's prefix implies a specific local routing area.
This means a Chicago-area number (in LATA 220) cannot be ported to a carrier serving only, say, Milwaukee (LATA 436), even if the customer moves there. The subscriber would need to obtain a new telephone number reflecting their new location. However, within a LATA, porting between carriers is broadly available regardless of whether those carriers operate wireline, wireless, or VoIP services — thanks to both wireline and wireless number portability mandates.
When you look up a phone number and see its LATA designation, you're seeing the geographic routing region that governs that number's local routing, portability, and in some cases, regulatory treatment.
The Evolution of LATA Relevance
The practical significance of LATA boundaries has diminished substantially since the 1996 Telecom Act and the rise of nationwide flat-rate calling. When AT&T, Verizon, and T-Mobile offer unlimited nationwide calling for a single flat monthly rate, the LATA distinction is invisible to consumers. No one pays more for a cross-LATA call today than for an intra-LATA call.
However, LATA boundaries remain deeply embedded in the technical infrastructure of the PSTN. Routing databases, interconnection agreements, 911 call routing, and numbering plan administration all use LATA as a fundamental geographic unit. Any serious work with PSTN routing or number administration requires LATA awareness.
Look up a number's LATA: Search any US phone number at foneinfo.us to see its assigned LATA number and geographic region. Cross-reference with the table above to understand the routing region.
