360 Area Code: Washington’s Ring Around Seattle

The 360 area code is western Washington outside the urban core — Olympia, Bellingham, Bremerton, Port Angeles, Aberdeen, Mount Vernon, and Vancouver on the Columbia River — wrapping the Seattle-area codes on every side. In service since January 15, 1995, it has shared its entire territory with the 564 area code overlay since August 28, 2017.

Those three digits carry a distinction no 1947 code can claim: they were undialable as an area code until the very morning this one lit up. And the territory behind them then spent eight years as the only place in the country where a 564 number could be issued. Both stories are small windows into how the numbering plan really operates.

Five days ahead of its Alabama twin

For the numbering plan’s first forty-eight years, every area code carried a 0 or 1 as its middle digit — a constraint the old electromechanical switches imposed. When the format finally opened, NANPA’s database records exactly two codes entering service on January 15, 1995: Washington’s 360 and Alabama’s 334. The assignment ledger gives 360 a five-day head start, logged January 21, 1994 against 334’s January 26 — so Puget Sound holds, by the thinnest of margins, the older claim on the modern format.

The new code’s job was relieving Seattle’s 206, which had already shed eastern Washington to 509 in 1957 and would be cut again in April 1997, when 253 and 425 carved out Tacoma, Everett, and the Eastside. The 1995 split worked the other way around: 360 took everything in the west that wasn’t the metro, and NANPA’s database still lists 206 as its parent.

Neah Bay to Camas, with a metro in the middle

The 1999 planning letter that first described this territory reads like a road trip: Ferndale, Bellingham, Arlington, Stevens Pass, Neah Bay, Port Angeles, Bremerton, Olympia, Aberdeen, Long Beach, Vancouver, and Camas. The list runs from the Pacific coast to a Cascade ski pass, taking in the state capital, the Kitsap Peninsula around Bremerton, and the second Vancouver — the Washington city facing Portland across the Columbia, where 503 holds the far bank.

What a map shows better than any list is that this code surrounds the metro completely: north of the Everett line, west across the Sound, south past Olympia — and east as well, up in the mountains behind the suburbs. The same 1999 letter proves the point in passing. It held five rate areas — Black Diamond, Enumclaw, Crystal Mountain, Stevens Pass, and Skykomish — out of early 564 assignment while King County installed an E-911 router, and every one of them drew its numbers from 360.

The code that ordered up 564

By decade’s end, growth had outrun the prefix supply. NANPA’s Planning Letter 196, dated October 29, 1999, opens bluntly: substantial number growth in the 360 NPA necessitates area code relief. The remedy was to be an all-services overlay — 564, in service August 1, 2000 — covering this territory and nothing else. Within nine months, Washington regulators had stretched that plan across all four western codes; within two years, number conservation was working so well they suspended the project outright. The full shelf-and-revival saga is told in our 564 area code guide.

The aborted rollout left a curious paper trail. Carriers stood up routing test numbers for a code that would not truly arrive for another seventeen years — 564-200-0564 answering in Bellingham, 564-201-0564 in Olympia, with siblings in Bremerton, Vancouver, Aberdeen, Port Angeles, Monroe, and Mount Vernon. Meanwhile thousands-block pooling kept the legacy inventory alive; the NPA-NXX breakdown covers how 1,000-number blocks stretch a code that whole prefixes would drain.

Ten digits, seventeen years to the day

When the overlay came back, it came back 360-only. On May 19, 2016, the Washington Utilities and Transportation Commission approved relief in Docket UT-143787, Order 01, and NANPA’s Planning Letter 492 set the terms: 564 would initially overlay the 360 territory alone, reaching 206, 253, or 425 only as each neared exhaust.

The schedule carried a quiet echo. Permissive ten-digit dialing began January 28, 2017, and the mandatory cutover landed at 12:01 a.m. on July 29, 2017 — the same calendar date the original 1999 letter, later superseded by the four-code plan, had once set for mandatory ten-digit dialing in the year 2000. Seventeen years to the day after the conversion was first scheduled, it happened. The first 564 prefixes could activate from August 28, 2017, with a routing check available at test number 564-564-1564 through late October.

Eight years as the only 564 country

From August 2017 to June 2025, every 564 number was issued against this footprint — Olympia, Bellingham, Vancouver, the peninsulas. That exclusivity ended on June 10, 2025, when the commission’s Seattle phase took effect: under Dockets UT-230108 and UT-143787, customers in the 206 region may now receive a 564 number once 206 inventory assigns out. 253 and 425 still hand out only their own digits.

The 2025 opening quietly inverted the two codes’ meanings. A 564 display now spans half the state, city and countryside alike — while 360 digits still mean exactly what they meant in 1995: the west side, minus the metro. In a numbering plan where area codes grow vaguer every year, this one got more precise by standing still.

Dialing has not moved since 2017: ten digits for local calls, 1 plus ten for toll, across 360 and 564 alike. The 2021 conversions for 988 had no work left to do here — NANPA’s Planning Letter 556 listed a single Washington code still dialing seven digits with a 988 prefix in use, and it was 509, across the mountains. The west side had done its homework four years earlier.

Decades of runway, freshly recounted

NANPA’s April 2026 exhaust cycle moved this complex harder than almost any other. The 360/564 pool, which the October 2025 edition had lasting to the second quarter of 2072, now carries a fourth-quarter-2057 exhaust date — fifty-eight quarters closer in one cycle, among the sharpest downward revisions in the entire report. The July 6, 2026 update list went no further than four Texas codes, so 2057 is the number on the books today.

Context softens the swing. The report’s note on complexes that share a code — and 564 now belongs to both the 360/564 and 206/564 complexes — explains that demand in any one overlay draws down the shared inventory, so Seattle’s growth now pulls on the same 564 pool. Even so, the Seattle row reads 2073, this one 2057, and NANPA’s database opens no jeopardy file and no relief docket for either. Three decades of supply is a comfortable place to sit.

What a 360 display is worth

For outbound teams, the practical question is what these digits do on a screen. The footprint holds three distinct audiences: the state-government orbit around Olympia, the trades-and-tourism economy of the coast and peninsulas, and Clark County’s commuter belt, where a business often works both banks of the Columbia. To all three, a 360 display reads as the neighbor calling — and the local presence mechanics of answer rates reward exactly that.

The standard caveat applies with extra force here. Caller-ID spoofing can put western Washington digits on any call, and the overlay era means even an honest 564 caller may be dialing from Seattle rather than Shelton. What vouches for a call is the carrier signing it — A-level attestation under STIR/SHAKEN — not the three digits up front.

SIPNEX operates under its own FCC carrier authorization and fills local DID orders at the rate-center level — Olympia, Bellingham, or Vancouver digits where inventory allows — carried by SIP trunking to the PBX or dialer your team already uses. Every outbound leg is signed at the A level with a STIR/SHAKEN certificate issued to SIPNEX itself, and toll-free numbering runs through SIPNEX’s RespOrg registration.

360 and 564, asked and answered

Capital, coastline, and Cascade towns wear these digits — and a call floor anywhere can wear them too. SIPNEX issues 360 and 564 numbers as a direct FCC-licensed carrier, lands them by SIP trunk, and signs each one A-level on a STIR/SHAKEN certificate the company itself holds. Write to the SIPNEX desk, check current rates, or call (833) 665-2220.