On Wednesday evening, 28-April-2010, NeuStar-NANPA uploaded the latest issue of their semi-annual NANP and NPA Exhaust Projections, known as the NRUF, Number Resource Utilization Forms. There are two PDF reports, each can be downloaded from:
NeuStar-NANPA and the rest of the industry began calling these reports the NRUF around 2000 or so, and then they became twice-a-year around
2004, in April/May, and in October/November.The NANP exhaust report for April 2010 shows that the NANP is anticipated to "exhaust" its 10-digit format, i.e., its supply of assignable 3-digit area codes, "beyond 2040". The October 2009 report indicated "beyond 2039" as its projection for "complete" NANP exhaust.
The NPA exhaust report shows individual NPAs for all US jurisdictions, and also for Canada (all Canadian provinces and NPAs are simply referred to as "Canada", almost "as if" Canada were a "single state"), but the _NON_ US NANP-Caribbean is _not_ included in the NPA exhaust report. Puerto Rico and the US Virgin Islands in the Caribbean, as well as Guam, the Northern Marianas/Saipan, and American Samoa, in the Pacific, _are_ included, since these are all "US" jurisdictions.
Nothing much is "earth shattering" when comparing the previous NPA exhaust report from October 2009, with the current one of April 2010. Most "imminent" exhaust projections are about the same, or else are pushed out one or two quarters. Some of the Canadian NPA anticipated to exhaust, however, have been pushed "earlier", by several quarters, i.e., a few years, when compared to what they had been projected in last Fall's report, but the CRTC and CNA have recently issued reports as to specific scheduled dates for OVERLAYS on these Canadian NPAs, see some of my posts in the past few weeks.
The forthcoming Kentucky 270/364 split has been pushed FURTHER OUT by just over a year from what it had previously had been projected to exhaust! This is not surprising, since the KY 270/364 split has been re-scheduled several times now, always pushed further into the future, ever since the KY-PSC approved the split back in late May 2007. At that time, the KY-PSC ordered a 270/364 split in western KY, with the "far west" changing to 364, and points to the east yet still in the western half of Kentucky to retain 270, permissive for April 2008, mandatory for October 2008. However, within weeks (mid-June-2007), the KY-PSC revised its order, this time for permissive being moved out to July 2008 and mandatory "TBD". And there have been several postponements ever since, all of them having mandatory "TBD". Presently, permissive dialing in a
270/364 western Kentucky area code split is for 29-October-2011, and mandatory "TBD". It is quite likely that this date will be pushed out even further, yet again!The KY 270/364 pending relief does seem to parallel what happened in the Salt Lake City UT Metro 801/385 area code relief. In the latter part of
2000, the UT-PSC ordered a DIS-contiguous split of 801, the northern and southern end suburbs/exurbs of SLC Metro would have split to 385, with SLC itself retaining 801, permissive on 31-December-2000, mandatory on 30-June-2001. But within weeks of this announced start of permissive dialing, the UT-PSC began postponing the permissive/mandatory dates. They postponed the implementation dates several times, and by Spring or Summer 2004, they announced that the 801/385 split was postponed "indefinitely, until further notice". The last "announced" permissive date would have been March 2005, the last "announced" mandatory date would have been September 2005.The telco industry had originally requested an 801/385 NPA overlay for the SLC UT metro area though. By Spring 2007, the telco industry appealed to the UT-PSC for the originally requested 801/385 area code OVERLAY, which was granted by the UT-PSC in Summer 2007, for implementation by February/March 2009, which is what has taken place. And there _ARE_ several "POTS" 385-NXX c.o.codes which have since been assigned and activated, with actual customers' line-numbers on those 385-NXX codes!
I am hopeful that the same will ultimately happen with western KY's
270/364, that the KY-PSC will eventually revise its previous decision, and instead order a 270/364 area code OVERLAY in western Kentucky, for whatever date it will actually need to become effective. NOTE that 270 split from 502 back in April 1999 (permissive). THAT was ORIGINALLY approved by the KY-PSC back in 1998 as an OVERLAY. But the KY-PSC subsequently "chickened-out", and reversed the overlay, instead ordering the 1999 502/270 area code split.Back in 2008/08, however, several previously approved area code splits were changed to overlays and implemented as such -- the 801/385 Utah relief mentioned above, and also West Virginia 304/681, California's
818/747 (originally announced as a split back in 1999, implementation dates always had been "TBD", revived in 2006/07 and approved for 2009 as an overlay), and California's 760/442 in the eastern edge of California along the borders with Nevada and Arizona, extending into some exurbs and suburbs of the extended Los Angeles Metro area, as well as suburbs of the San Diego Metro area.In the 760/442 relief, it was originally approved as a SPLIT to be implemented back in 2000/01, with the San Diego suburbs changing to 442 with everything else 760 retaining 760. This was put on hold before it could have been implemented. During 2006/07, it was revived, the telco industry desiring an overlay, but the CA-PUC voting for the original split, to take effect during 2008/09. But after an active grass-roots campaign of residents, businesses, local governments, etc. including the US Navy in the San Diego area, the CA-PUC instead canceled the split and instead ordered an overlay for 2009/10.
So, hopefully, the KY-PSC can be persuaded to change 270/364 from a (pending) split, into an overlay, as well!
Mark J. Cuccia markjcuccia at yahoo dot com Lafayette LA, formerly of New Orleans LA pre-Katrina