An area code is not a place. It is a routing key — the first three digits a switch reads to decide where a call goes and what it costs. Most guides to area codes are written for someone choosing a phone number. This one is written for whoever has to route to it.
By Vedant Vhanyalkar
In the North American Numbering Plan a number breaks into NPA-NXX-XXXX. The NPA is the area code. The NXX is the central office code — historically the exchange, now more usefully thought of as the block a carrier was allocated numbers from.
Routing decisions get made on NPA-NXX. Not on the area code alone. That pairing is what a rate deck prices against, what a least-cost routing table matches on, and what a dial plan keys off. The area code by itself is too coarse to route with — one NPA can span multiple rate centres with different termination costs.
An area code does not tell you where the person answering is. It tells you which rate centre the number was originally assigned to. Two changes broke the link permanently: number portability, which lets a subscriber keep a number when they move, and cloud numbering, which lets a business hold a number for a city it has never had an office in.
Treating an NPA as a location is a routine cause of misrouted traffic and wrongly estimated termination cost. If you need to know where a number actually terminates, that is an LRN lookup, not an area code lookup.
Each NPA holds a finite number of assignable NXX codes. NANPA monitors supply and demand and publishes exhaust forecasts twice a year. When an area code is projected to run out of assignable codes within roughly a 36-month window, NANPA petitions the relevant state commission for relief planning on behalf of the industry.
Relief is not a technical decision made by a carrier. It is a regulatory proceeding, and the state commission decides the form it takes. That matters operationally: the timeline is public well in advance, which means nobody routing traffic into that market has an excuse for being surprised.
A split divides the existing geography. Part of the region keeps the old code, part gets a new one, and those subscribers change number. Unpopular. Disruptive. Largely out of favour.
An overlay adds a second area code across the same geography. Nobody changes number. New assignments come from the new code. This is the form of relief the industry generally prefers, and per NANPA it is what almost all current relief plans use.
Because two codes now serve the same streets, seven-digit dialling stops being unambiguous. Overlays therefore require ten-digit dialling for all local calls in the affected area — the cost of not making anyone change their number.
The transition runs through a permissive dialling period, during which both patterns work, before ten digits becomes mandatory. Duration varies by implementation. In the 202 overlay, permissive ten-digit dialling began in April 2021 and mandatory dialling took effect that October.
For a subscriber, a new area code means updating a few contacts. For anyone carrying traffic, it is a data change with a deadline. Four things go wrong, and they go wrong in a predictable order.
A dial plan that validates against a list of known NPAs will reject numbers in the new code as malformed. The call never leaves the platform. This tends to surface as scattered user reports rather than an outage, which is why it can run for weeks before anyone connects the reports to a numbering change.
New NPA-NXX combinations need loading into least-cost routing. Until they are, calls either fail or fall through to a default route, which is usually the expensive one. The failure is quiet. It is also billable.
A prefix with no rate entry gets priced at whatever the fallback is. Reconciling an invoice against a deck that predates a numbering change is how a small operational gap becomes a disputed bill three weeks later.
Any internal system that still dials seven digits inside the affected region breaks at the end of the permissive period. PBX speed dials, stored callback numbers, hard-coded strings in scripts — none of it is glamorous and all of it is real.
Presenting a number whose NPA matches the called party's region generally improves answer rates. That observation is old and it is why local-presence dialling exists as a product category at all.
It also attracts scrutiny. Presenting a number you have no right to use in order to mislead the called party is a separate thing from presenting a legitimately assigned local number, and regulators treat them differently. The distinction is whether the number is genuinely yours and genuinely reachable.
Call authentication frameworks sign the calling number, so what you present determines what can be attested. A number you hold and can demonstrate rights to behaves differently downstream from one you cannot. This is a numbering question before it is a signalling one.
The mechanics of caller ID delivery, and the three separate reasons a number goes missing on route, are covered in CLI vs NCLI routes.
NANPA publishes planned area codes with in-service dates well ahead of implementation. State commissions publish the proceedings. Both are public. A quarterly check against the destinations you actually carry is enough, and it is cheaper than discovering a change through a customer.
An in-service date is when numbers in the new code start being assigned. Your routing tables need the prefixes before that, not after. The permissive period protects dialling patterns; it does not protect a routing table with no entry.
Dial plans that allowlist known NPAs break every time the plan changes. Validating format — length, structure, valid NPA range — rather than membership of a list you maintain by hand removes an entire class of recurring failure.
Place real calls to numbers in a newly active code and confirm they complete, at expected cost, with caller ID intact. A routing table that loads without error is not a routing table that works. Test it.
Three questions worth putting to any provider carrying your US traffic, none of which are unreasonable to ask:
MCC provisions wholesale voice by traffic profile — see Wholesale Voice for network-scale outbound, and CC Routes for call-centre and dialer traffic. Coverage and CLI presentation vary by destination and are confirmed per destination rather than promised in general.
Related reading: VoIP routes explained, Wholesale voice termination, CLI vs NCLI routes.
Worked example: the 213 area code — five splits, a recombination, and a third overlay in November 2024.
Numbering plan detail in this article follows NANPA published guidance on area code relief. Confirm current dialling rules and in-service dates with NANPA or your carrier before changing a dial plan.
MCC provides wholesale voice termination and CC routes for carriers, ITSPs and platforms. Confirm coverage and route type for your destination mix.