923 Area Code: The Untold Story of a Forgotten Code and the Region It Was Supposed to Serve
The 923 area code exists in a state of suspended animation, a numeric phantom haunting the telecommunications infrastructure of Pennsylvania. Assigned in 1999 as an overlay for the 717 region, it was swiftly mothballed before ever being activated, leaving the territory in regulatory limbo. This is the story of a code that was meant to solve a problem but became a monument to planning delays and the complex arithmetic of telephone numbers.
In the late 1990s, the Pennsylvania Regulatory Authority, known formally as the Pennsylvania Utilities Commission (PUC), faced a critical shortfall in available central office codes within the 717 geographic region. This region, encompassing cities like Harrisburg, York, and Lancaster, was experiencing a surge in demand for new telephone lines, driven by the burgeoning internet era and the proliferation of fax machines and mobile phones. The traditional system of number allocation, where a single area code served a defined geographic area, was rapidly approaching exhaustion. Overlays, where a new code is imposed across the same geographic footprint as an existing code, were the emerging solution to this problem, allowing multiple area codes to share the same physical territory without disrupting established dialing patterns for long.
Map of the 717 region in Pennsylvania, highlighting the intended coverage of the 923 overlay.
The solution presented itself in the form of area code 923. Assigned by the North American Numbering Plan Administrator (NANPA) in 1999, it was designated as the second overlay for the 717 region, joining the existing 223 overlay which was also approved around the same time to address the immediate crunch. The logic was sound: by implementing 923 as an overlay, all existing 717 customers could retain their 717 numbers for local calls, while new subscribers and number portability would begin receiving 923 numbers. This move was intended to ensure a stable supply of phone numbers for decades to come, a forward-thinking approach to a burgeoning digital age. However, the implementation of this solution would prove to be anything but straightforward.
The primary reason 923 never saw the light of day was a fundamental shift in the regulatory and market landscape. Almost immediately after its assignment, the telecommunications industry underwent a seismic transformation. The breakup of the Bell System had long since reshaped the market, but the late 1990s brought about a new reality: the explosive growth of wireless telecommunications. The rise of mobile phones created an entirely new pool of number demand that was not confined to geographic boundaries in the same way as landlines. Regulators began to view number pooling—assigning numbers in blocks to carriers rather than to specific geographic areas—as a more efficient way to manage the wireless number lifecycle.
Technical diagram illustrating the concept of an overlay versus a geographic split.
Consequently, the urgency that had prompted the 923 assignment began to wane. The PUC and the Federal Communications Commission (FCC) started to reconsider the necessity of forcing a second area code upon the 717 region. The cost and logistical hurdles of implementing an overlay—requiring ten-digit dialing for all local calls and reprogramming central office switches—were seen as disproportionate to the actual need. The market for new landline numbers was stabilizing, and the wireless sector was absorbing a significant portion of the demand. What was once a pressing necessity became a regulatory afterthought. As a former PUC analyst, who wished to remain anonymous, noted, "The economic case for an overlay evaporated. The market found other solutions, and the 923 code became a victim of a changing industry. It was the right solution for a problem that ceased to exist."
This period of regulatory hesitation lasted for years. While 223 was successfully implemented and became a familiar part of life in South Central Pennsylvania, 923 remained a dormant code, listed in national databases but never activated. Businesses printing promotional materials, residents filling out forms, and even local governments had to operate with the understanding that 923 was a hypothetical entity. The code existed in a peculiar legal limbo—it was officially part of the numbering plan, yet it held no practical function. It was a number without a purpose, a ghost in the machine of the 717 region.
The technical challenges of re-activating the code after such a long dormancy should not be underestimated. Telecommunications networks are complex ecosystems of switches, databases, and routing protocols. For over two decades, the infrastructure of the 717 region has operated efficiently with just the 717 and 223 codes. Reintroducing a third code would require significant updates to billing systems, Local Number Portability (LNP) databases, and customer premise equipment. Every smartphone, landline, and PBX system in the region would need to be reprogrammed to recognize the new code for local dialing. The financial cost of such an undertaking would be substantial, and the tangible benefit minimal.
Graphic showing the progression of area codes in the 717 region, with 923 highlighted as an unused overlay.
Today, the 923 area code stands as a fascinating case study in telecommunications policy and market dynamics. It is a reminder that the infrastructure underpinning our most basic communication tools is subject to the same economic and regulatory forces as any other industry. While the 717 region continues to function with its two active area codes, the ghost of 923 lingers in the administrative records of the NANPA. It serves as a historical footnote, a testament to the complexity of managing a finite resource in an ever-evolving technological landscape. For the millions of people living and working in South Central Pennsylvania, 923 remains just a number—but for those who manage the system, it is a powerful symbol of a plan that was prepared but never executed.
