The 224 area code blankets Chicago’s northern suburbs as the overlay of 847 — the North Shore from Evanston through Winnetka and Highland Park, Lake County up to Zion and Antioch at the Wisconsin line, and the northwest Cook towns from Des Plaines and Arlington Heights out to the Fox River at Elgin. In service since January 5, 2002, it added a second code to the 847 map without changing a single existing number.
Most area codes arrive on a schedule. 224 arrived on a tripwire — barred by state order from issuing its first prefix until its parent had issued every one of its own. The three and a half years between assignment and dial tone hold the busiest regulatory file of any Chicago-area code: a prefix lottery, the pooling experiment the FCC let Illinois keep, and an exhaust declaration the state refused, at first, to accept.
Zion to Evanston to Elgin: one map, two codes
The rate-center map NANPA published with Planning Letter PL-305 draws a single boundary for 224 and 847. Along Lake Michigan it runs from Evanston through Wilmette, Winnetka, Glencoe, Highland Park, and Lake Forest to Waukegan, Zion, and Antioch. Inland Lake County fills in with Libertyville, Mundelein, Grayslake, Round Lake, Fox Lake, Wauconda, and Lake Zurich; northwest Cook contributes Skokie, Glenview, Northbrook, Park Ridge, Des Plaines, Wheeling, Arlington Heights, Palatine, and Barrington; the far edge reaches Cary, Algonquin, Dundee, Hampshire, and Elgin.
South of that line the region changes codes quickly — 630 and 331 along the western corridor, 708 and 464 nearer the city, and Chicago proper’s own three codes beyond that. North of it, every local number to the state border answers on 224 or 847: two codes, one territory, identical in price and equally local on a caller ID.
In jeopardy before its second birthday
847 is the elder of the pair, and its emergency is why 224 exists. Carved from the all-suburbs 708 ring — itself a 1989 offshoot of Chicago’s original 312 — the northern-suburbs code took its first calls on January 20, 1996. The Illinois Commerce Commission’s relief chronology logs a notice of impending exhaust by May 1997, and on October 10, 1997 the administrator declared 847 in jeopardy, with conservation measures in force by November.
Rationing followed. Planning Letter PL-NANP-127 records a lottery handing out five central-office prefixes per month — carriers queued for a draw, ten thousand numbers per ticket. In May 1998 the ICC ordered relief under the plan approved in Consolidated Docket 97-0192/97-0211: an all-services overlay, plus a thousand-block number-pooling trial for 847. NANPA’s database dates 224’s assignment to May 1, 1998, announced that June 30 in PL-NANP-127.
The trial soon collided with national policy. The FCC’s October 1998 Pennsylvania Order held that states could not mandate number pooling — and granted Illinois limited authority to keep its 847 trial running. That December the commission confirmed the pooling directive and began collecting utilization data from carriers across all five Chicago-area codes, treating the number supply as something to be audited rather than taken on faith.
The exhaust notice that went back for a recount
By late 2000 the countdown itself was in dispute. A Neustar officer had testified before the commission that carrier-reported usage data was “historically inaccurate,” and an emergency conference call on 847’s status followed that November. NANPA notified the ICC on January 17, 2001 that 847 was exhausted and the 224 schedule was underway — and the commission checked the math instead. Two days after a company officer described “fatal errors” in the reported data, the ICC on February 15, 2001 rejected the exhaust notice, ordered nine still-assignable prefixes issued, and directed carriers to return every code they were not using.
The recount paid. Between February and July 2001, fourteen more 847 prefixes went out to carriers — an extension the ICC’s chronology credits with six additional months of life. Only on July 20, 2001 did the administrator certify the true end, exhaust within thirty days, and the first 224 prefix was assigned on September 14, 2001, starting the ninety-day consumer-education clock the state had attached to the launch.
Penciled in for 1998, live in 2002
On paper, the overlay was nearly a 1990s event. PL-NANP-127 projected 224 operational on November 7, 1998, with permissive full-number dialing already running since May 11, 1998. Then PL-NANP-157 withdrew the date entirely: under ICC Docket 98-0497, every available 847 prefix had to be assigned before the first 224 prefix, and final implementation could come no earlier than ninety days after that first assignment. No calendar — a condition, and a template Chicago’s later overlays would follow.
The condition finally tripped in the autumn of 2001. With the first 224 prefix out in September, the ICC notified NANPA on October 4 of the finish line, and PL-305 published it: mandatory 1-plus-ten-digit dialing and the overlay’s in-service date together on January 5, 2002 — the first overlay to reach service anywhere in Illinois. Carriers confirmed their routing against 224-444-1234, a test number first switched on in August 1998 for a launch that never came, and back in service through January 5, 2003 for the one that did.
The dialing plan, unchanged since 2002
NANPA lists one pattern for every call in the 224/847 complex — local or toll, inside the footprint or out: 1 plus the ten-digit number, with operator-assisted calls taking 0 plus ten. It has worked that way since the morning the overlay went live, closing a permissive stretch of nearly forty-four months.
That head start shows in what never happened here. When the arrival of 988 pushed 82 seven-digit area codes to full-number dialing — NANPA Planning Letter PL-556, January 8, 2021, superseding PL-544 — Illinois contributed 309, 618, and 708 to the list and the 224/847 territory nothing at all, having dialed this way for nineteen years. PL-556 also notes the state habit behind the leading digit: California and Illinois dial local calls as 1 plus ten.
The family’s next shortage lands here first
NANPA’s exhaust analysis for cycle 2026-1, issued in April 2026, projects the combined 224/847 pool empty in the third quarter of 2033 — the earliest exhaust date of any Illinois complex, though three quarters later than October 2025’s call. For scale inside the family: 773/872 runs to late 2046, 312/872 to 2049, 464/708 to 2053, and 331/630 clear out to 2080. One correction has followed, on July 6, 2026 — four Texas entries, nothing in Illinois.
No alarm is sounding yet — the administrator’s database lists the pair without a jeopardy mark or any relief activity — but the suburbs that once rationed prefixes by lottery sit first in line for a third code, and how that decision gets made is a process this region has lived through twice already. The everyday effect is older than the forecast: with fresh prefixes issuing from the 224 side since September 2001, new north-suburban numbers usually carry 224, while vintage 847 stock circulates through pooling returns and ported lines.
Earning the pickup north of the city
For a sales floor or service desk calling into these suburbs, the code on the display is the first impression: a 224 or 847 number reads as Waukegan or Palatine on the line, where an out-of-market string reads as a solicitation. That difference is measurable in answer rates — the arithmetic is in our local presence dialing guide — and the standard caution travels with it, because spoofed caller ID wears familiar digits precisely because they get answered.
SIPNEX operates as the carrier itself — a direct FCC authorization, with RespOrg status on the toll-free side — and stocks local DIDs at the rate-center level, north-suburban Chicago inventory included, in either code as availability runs. Delivery runs over SIP trunking to the PBX or dialer already in your rack, and every outbound call is signed for A-level attestation under the STIR/SHAKEN certificate that carries SIPNEX’s own name — so the local number you show is also a verified one.
Getting specific about 224
Is a 224 number different from an 847 number?
Only in age. The two codes are an overlay pair covering identical territory since January 5, 2002, so calling either costs the same, dialing is identical, and each reads equally local from Antioch to Evanston. Because 224 prefixes only began issuing once 847 had assigned its last available prefix, an 847 number simply predates the overlay era — 224 is where nearly all newly opened number ranges have lived since.
Why did the 224 area code take until 2002 to launch?
Because Illinois forbade an early start. Under ICC Docket 98-0497, no 224 prefix could be assigned until every available 847 prefix was gone, and implementation had to wait at least ninety days past that first assignment. Conservation — a five-per-month prefix lottery, a thousand-block pooling trial, and a 2001 clawback of unused codes — kept 847 alive long past the November 1998 start NANPA had originally projected. The first 224 prefix was finally assigned on September 14, 2001.
What digits does a 224 area code call take?
With all eleven digits: 1, then the area code, then the seven-digit line number — the plan NANPA lists for every local and toll call in the 224/847 complex. Operator-assisted calls substitute 0 for the 1. The format has been mandatory since January 5, 2002, so the 2021 conversions for the 988 crisis line, which moved 82 other area codes onto full-number dialing, required no change here.
What towns are in the 224 area code?
The northern suburbs of Chicago. NANPA’s overlay map names rate centers including Evanston, Wilmette, Winnetka, Glencoe, Highland Park, Lake Forest, Waukegan, Zion, Antioch, Libertyville, Mundelein, Grayslake, Fox Lake, Wauconda, Lake Zurich, Skokie, Glenview, Northbrook, Park Ridge, Des Plaines, Wheeling, Arlington Heights, Palatine, Barrington, Cary, Algonquin, Dundee, Elgin, and Hampshire. Every one of them is 847 territory too — the codes are interchangeable across the footprint.
How much runway does the 224 area code have left?
NANPA’s April 2026 exhaust analysis projects the combined 224/847 inventory running out in the third quarter of 2033 — the earliest forecast in Illinois, though the newest study added three quarters over the last one. Jeopardy has never been declared and no relief case is open, so numbers remain orderable normally; a business that wants specific north-suburban rate centers can check current DID stock and lock them in well ahead of any squeeze.
North of the city, SIPNEX supplies the whole number stack on its own FCC license: 224 and 847 DIDs by rate center while inventory holds, local numbers in every other US market, toll-free through RespOrg registration, and SIP trunks built for dialer duty, each call signed A-level under SIPNEX’s own STIR/SHAKEN certificate. Dial (833) 665-2220, compare published rates, or write to the team.
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.