The 425 area code is the Seattle metro north and east of Lake Washington — Bellevue, Kirkland, Redmond, Bothell, and Issaquah on the Eastside, Renton at the lake’s southern tip, and Everett to the north. Cut from Seattle’s 206 on April 27, 1997, it has never issued anything but its own digits: the 564 overlay that legally blankets it has yet to place a single number here.
Two documents bracket this code’s life so far. The first is a 1996 Bellcore planning letter that invented it. The second is NANPA’s April 2026 exhaust table, where 425 posts the earliest projected empty date of any western Washington code — first quarter of 2044 — which makes the Eastside the next candidate, ahead of Tacoma’s 253, to actually receive the overlay that so far only the 360 territory and Seattle share.
A growth problem cut three ways
On October 31, 1996, the numbering plan’s administration — then a desk at Bellcore — issued Planning Letter PL-NANP-019. US WEST had reported that “substantial number growth” around Seattle required dividing 206 into three codes at once, and NANPA’s database logs 425 and 253 as assigned that same day. Seattle proper, Richmond Beach, and the islands kept 206; Tacoma, Kent, and Federal Way took 253.
The middle paragraph of that letter is still the cleanest legal definition of this territory — the new 425 would consist of “Everett, Renton/Maple Valley and the existing 206 NPA exchanges north and east of Lake Washington.” The lake itself is the border — Seattle numbers on the west shore, Eastside numbers on the east.
The split took effect at 12:01 a.m. on Sunday, April 27, 1997 — a moment the letter, drafted in New Jersey, scheduled in Eastern time. Either code connected until the permissive window closed on November 16, 1997, and from April 13 carriers could hear a recorded announcement at 425-452-0009 confirming their routing, up to the line’s November 30 disconnection. Local calls stayed at seven digits, and no local calling areas changed.
The lake in the boundary line
The map stapled to PL-NANP-019 labels the new territory simply: the “Bellevue area.” It runs from Everett and Halls Lake at the top, down through Bothell, Kirkland, Bellevue, and Issaquah, east past Fall City to the North Bend and Snoqualmie Pass rate centers, and south to Renton and Maple Valley — essentially a King–Snohomish county pair, wrapped around two sides of a lake.
One landmass inside that wrap belongs to someone else. Mercer Island sits in the middle of Lake Washington, connected by bridge to both shores, and the 1996 letter kept it with Seattle’s 206 — so an island reached by bridge from both shores answers on Seattle’s code, while the Bellevue waterfront it faces to the east picks up on 425. Beyond the metro in every landward direction, 360 picks up, from the Cascade passes to the peninsulas.
Blanketed on paper in 2000, untouched since
Three years after the split, Washington decided its next relief would cover everyone at once. NANPA’s Planning Letter PL-239 (July 27, 2000) recorded the WUTC’s decision in UT-990219: one all-services overlay, 564, spanning 206, 253, 360, and 425 together, with the first 564 prefixes cleared to activate after October 20, 2001. The letter’s roll call of communities to be served already read Bellevue, Everett, Kirkland, Redmond.
None of it happened on that schedule. Number conservation caught up with demand, regulators shelved the whole project in 2001, and the shelf held for a decade and a half — the full detour is told in our 564 area code guide. When the plan returned in Planning Letter PL-492 (June 28, 2016, following the WUTC’s May 19, 2016 order in Docket UT-143787), it came back narrower: 564 would open over the 360 territory alone.
PL-492 then wrote the rule that has governed the Eastside ever since: “The 564 NPA may be assigned to the 206, 253 and 425 NPAs only when those NPAs are nearing exhaust.” Seattle crossed that line first — an August 2023 planning letter, PL-620, implemented the WUTC’s June 15, 2023 approval in Docket UT-230108, and 564 assignment opened in the 206 territory on June 10, 2025. In 425, the trigger stays unpulled: NANPA’s database still records the code with its overlay flag reading No.
One dialing change in three decades
For its first twenty years, 425 dialed the way its parent always had — seven digits for a neighbor, 1 plus ten for toll. The overlay’s revival ended that: under PL-492’s schedule, permissive ten-digit dialing began across all four western codes on January 28, 2017, and seven-digit dialing died region-wide at 12:01 a.m. on July 29, 2017, a month before 564 itself went live.
That early conversion bought the Eastside a pass on the next one. When the 988 rollout forced 82 area codes onto ten-digit dialing in 2021, NANPA’s Planning Letter PL-556 named exactly one Washington code — 509, east of the mountains. Today the plan is unchanged: ten digits for local calls, 1 plus ten for toll, and carriers may accept 1 plus ten on local calls at their discretion.
The first west-side pool to empty
The 2026-1 edition of NANPA’s exhaust analysis — April 2026, reading utilization reported through March 1 — projects 425 out of assignable prefixes in the first quarter of 2044. That is fourteen quarters sooner than the October 2025 study said, a revision NANPA footnotes as increased historical and projected demand, and the single correction since — July 6, 2026, four Texas entries — left every Washington row alone.
Line the four western codes up and the order of succession is plain: 425 empties in 2044, 253 in mid-2056, the 360/564 complex in late 2057, and Seattle’s 206/564 pool not until 2073. The code covering the metro’s fastest-growing office corridors is, fittingly, the one drawing down fastest — how prefix-by-prefix consumption turns into these dates is the subject of our NPA-NXX breakdown.
Nothing about that is an emergency. The database holds nothing against the code — no jeopardy note, no relief docket — because the relief already exists: when 425 nears exhaust, the WUTC opens the Eastside phase of 564 the way it opened Seattle’s in 2023, new lines begin drawing the overlay code, and — as with every modern area code transition — existing numbers never change.
What Eastside digits do for a business
Within the footprint, 425 reads as specifically local in a way the eventual overlay never will: software campuses in Redmond and Bellevue, aerospace floors in Everett, and the trades that serve both recognize the code as their own. For outbound teams, matching that expectation is measurable — our local presence dialing guide puts figures on it — and because no second code shares the pool yet, an Eastside display still narrows the caller to one corner of the metro.
What the three digits cannot do is answer for the call. Caller-ID spoofing will stamp 425 onto traffic from anywhere, so the trustworthy signal rides underneath: cryptographic signing under STIR/SHAKEN, where a carrier stakes its identity on knowing its caller.
SIPNEX holds FCC carrier authority directly and stocks local DID numbers by named rate center — Bellevue, Everett, or any other US market with available inventory — delivered over SIP trunking to whatever PBX, softphone, or dialer your day already runs on. Outbound calls pick up A-level attestation from SIPNEX’s own STIR/SHAKEN certificate, and toll-free service runs under SIPNEX’s RespOrg registration.
Questions that follow a 425 number
Which cities use the 425 area code?
Bellevue, Kirkland, Redmond, Bothell, Issaquah, Renton, Maple Valley, and Everett, plus rate centers reaching east to Fall City, North Bend, and Snoqualmie Pass. The 1996 planning letter defined the territory as Everett, Renton/Maple Valley, and the former 206 exchanges north and east of Lake Washington. Mercer Island, though bridged to Bellevue and its 425 shore, kept 206, and Tacoma’s side of the metro dials 253.
Does the 425 area code have a 564 overlay yet?
On paper since 2000, in practice not yet. The 564 overlay legally spans 425 under Washington’s four-code relief plan, but the 2016 planning letter allows 564 assignment there only when 425 nears exhaust — a condition not yet met, so every number issued in the territory is still a 425. The overlay is active in the 360 region and, since June 10, 2025, in Seattle’s 206; the sequence is laid out in our 564 area code guide.
When did 425 split away from area code 206?
At 12:01 a.m. on Sunday, April 27, 1997, in a three-way division announced by Bellcore-era planning letter PL-NANP-019: Seattle kept 206, the Tacoma side became 253, and Everett plus the exchanges north and east of Lake Washington became 425. Calls dialed with the old code still completed through November 16, 1997, and carriers verified routing against a test number, 425-452-0009, from that April 13.
Are local calls in 425 dialed with ten digits?
Yes, and they have been since 12:01 a.m. on July 29, 2017, when ten-digit dialing became compulsory across 206, 253, 360, and 425 ahead of the 564 overlay’s launch. Toll calls take 1 plus ten digits, and carriers may accept 1 plus ten on local calls at their own discretion. Before 2017, the code had dialed seven-digit local calls for its entire existence — and the early conversion meant the 2021 changes tied to 988 required nothing of it.
When will the 425 area code exhaust its numbers?
NANPA’s April 2026 analysis projects the first quarter of 2044 — the nearest exhaust date among western Washington’s codes, and fourteen quarters closer than the previous study put it. No declaration or docket is pending, because the remedy is pre-built: approaching exhaust triggers the 564 overlay’s Eastside phase, existing numbers keep working unchanged, and local DID inventory in 425 rate centers remains orderable today.
The lake draws the border, and the right digits put your business on its east shore. SIPNEX provisions 425 numbers under its own FCC carrier license, routes them anywhere over SIP trunking, and signs every outbound call at A-level attestation on a certificate issued to SIPNEX itself. Reach the SIPNEX team, check current pricing, or dial (833) 665-2220.
Keep reading.
The carrier built by operators, for operators.
FCC-licensed carrier with its own STIR/SHAKEN SP certificate. Operator-owned. SIP trunks built for operators who dial at volume.