202 Area Code: DC’s 74-Year One-Code Run

The 202 area code serves Washington, DC — the full District of Columbia and not an inch beyond it — and has done so since January 1, 1947, when NANPA’s records show it entering service among the numbering plan’s original codes. Since November 9, 2021 it shares the city with 771, the District’s first overlay.

Area-code histories usually chronicle change — maps split, territory lost, overlays stacked three deep. 202 spent 74 years declining to have one: a single code running a single city, untouched, while the numbering map around it kept redrawing itself.

The map that never moved

The original 1947 codes mostly covered whole states or big slices of them, and growth eventually carved nearly all of those maps up. Manhattan’s 212 lost the outer boroughs and then the Bronx; next door, Maryland’s 301 was split in 1991 and overlaid by 240 in 1997. 202 had nothing to carve: the District is a fixed federal footprint of roughly 68 square miles, with no suburb inside it to break away.

NANPA’s NPA database says it plainly. Assigned January 1, 1947. In service January 1, 1947. No parent code — and the only code that lists 202 as its parent is 771, an overlay rather than a split. The Maryland suburbs have always answered on their own codes, Northern Virginia on its own as well. 202 meant the city, the whole city, and nothing else.

That containment is what turned three digits into shorthand. Congress, the agencies, the press corps, and the industries built around them all answer on the same code, so “a 202 number” reads less like geography and more like a job description.

Seventy-four years of headroom, then 2020

An area code’s real capacity is its stock of three-digit NXX prefixes, and a compact city burns through them far slower than a sprawling metro. Even so, decades of second lines, faxes, mobiles, and VoIP services ate at the pool, and by 2020 the District’s regulators moved before the math forced them to.

On September 16, 2020, the Public Service Commission of the District of Columbia approved an all-services distributed overlay as 202’s relief in Commission Order No. 20627, issued in Formal Case 1165. NANPA’s database records 771 assigned to the job six days later, on September 22, 2020. Planning Letter PL-547, dated October 22, 2020, set down the schedule — the overlay path our area-code explainer weighs against splits, chosen here so no Washington number would change.

How the switchover ran

Three dates in PL-547’s implementation table carried the switchover:

• April 10, 2021 — permissive ten-digit dialing began at 12:01 a.m. ET; seven-digit calls still completed.
• October 9, 2021 — mandatory ten-digit dialing took effect; every local call now carries the code.
• November 9, 2021 — 771 entered service.

The letter also wrote a pecking order into the plan: no 771 prefix is assigned until every available 202 prefix is exhausted. Local calls dial ten digits, with 1-plus-ten permitted at each carrier’s discretion — the same plan NANPA’s database shows for both codes today.

The timing makes it look like part of the 2021 national ten-digit wave. It wasn’t. Planning Letter PL-556 — the January 8, 2021 letter naming the 82 codes forced onto ten digits so 988 could become the crisis line — includes no District of Columbia entry. DC’s conversion was already on the overlay calendar, and its October 9 mandatory date landed fifteen days ahead of the national October 24 deadline the 988 letter set.

Where the count stands in 2026

NANPA’s April 2026 NPA Exhaust Analysis, built on NRUF and prefix data as of March 1, 2026, projects the combined 202/771 pool to exhaust in the third quarter of 2088 — pushed out a full sixty quarters from the 3Q 2073 date in the previous forecast, on reduced historical and projected demand. The July 6, 2026 revision list left the DC figure untouched.

The database backs that calm reading — no jeopardy flag, no active relief project. PL-547’s assignment gate has already swung, though: NANPA’s code-assignment records show no available 202 prefixes left, so brand-new prefixes now come from 771 — while individual 202 numbers still come from the inventory carriers hold inside the code’s long-assigned prefixes.

Local to the federal city

In a city where whole industries exist to be near the government — associations, government-affairs firms, federal contractors, newsrooms — the code works as a credential of proximity. A 202 display tells a Hill office or an agency contact that the call is from town, and local presence dialing turns that recognition into answer rates.

The display still proves less than it implies. Numbers port, VoIP travels, and caller-ID spoofing can dress any robocall in Washington digits — which is why a signed call now says more than a familiar code.

That signature is where SIPNEX comes in. We hold our FCC carrier authorization directly, provision DC numbers by rate center, and deliver them over SIP trunking built for real outbound volume. Every call leaves signed at the A level under the STIR/SHAKEN certificate SIPNEX itself holds — attestation a spoofed 202 display cannot borrow.

Five questions about the 202 area code

A Washington number belongs on carrier rails. SIPNEX holds its FCC authorization directly, stocks rate-center DID inventory across US markets, runs toll-free through its own RespOrg registration, and signs every outbound call at the A level. DID and trunk rates are on the site; ordering starts at (833) 665-2220 or with a line to the carrier team.