For the text (ASCII, tab delimited) files, for each region
of the country there are two links,
one containing utilized codes, and one containing available codes.
The file contains either all of the available
or all of the utilized central office codes in the region.
(Updated weekly, courtesy, NANPA)
|
| Central - North |
IA, IL, IN, KY, MI, MN, OH, WI |
Available
Utilized |
| Central
- South |
AL, AR, LA, MO, MS, TN, TX |
Available
Utilized |
| Eastern
- Atlantic |
PR, VI |
Available
Utilized |
| Eastern
- North |
CT, MA, ME, NH,
NJ, NY, PA, RI, VT |
Available
Utilized |
| Eastern
- South |
DC, DE, FL, GA,
MD, NC, SC, VA, WV |
Available
Utilized |
| Western
- North |
CO, ID, KS, MT,
ND, NE, NV, OR, SD, UT, WA, WY |
Available
Utilized |
| Western
- Pacific |
AK, GU, HI, NN |
Available
Utilized |
| Western
- South |
AZ, CA, NM, OK |
Available
Utilized |
For the Excel files, there are
three regions; the spreadsheet for each region contains
a tab for each State in that region. The Excel spreadsheets contain all the codes,
both available and utilized.
(Updated weekly, courtesy, NANPA)
|
| Central-North |
AL,
AR, IA, IL, IN, KY, LA,
MI, MN, MO, MS, OH, TN, TX, WI |
All Codes |
| Eastern |
CT,
DC, DE, FL, GA, MA, MD, ME, NC, NH, NJ, NY,
PA, RI, SC, VA, VT, WV (PR, USVI) |
All Codes |
| Western |
AK,
AZ, CO, CA, HI, ID, KS, MT, ND, NE, NM, NV,
OK, OR, SD, UT, WA, WY (GU, CNMI) |
All Codes |
The Access database file contains
all the States and NPAs.
(Updated weekly, courtesy, NANPA) |
| ALL |
ALL |
All Codes |
|
The
"available" (unassigned) files contain the following data fields: |
| Field |
Definition |
| State
Abbreviation |
Standard two
character abbreviation. |
| NPA-NXX
|
Area Code and
Prefix |
|
|
|
The
"utilized" (in use) files contain the following data fields: |
| Field |
Definition |
| State
Abbreviation |
Standard
two character abbreviation |
| NPA-NXX
|
Area
Code and Prefix |
| OCN |
Operating
Company Number |
| Company
Name |
Full
Company Name; Company Names are enclosed with quotes if they contain special characters. |
| Rate
Center |
10
character abbreviation for the Rate Center in which the code is assigned. |
| Switch |
11
character COMMON LANGUAGEŽ identifier of the switch. |
| Future
Effective Date (EffectiveDate) |
The
future date when a new code will be in service (for new codes only). Once the effective
date is reached, this date will no longer appear. |
| Use |
VC
These codes are not included in the "utilized" text files |
VC
indicates codes that are vacant; they are available for assignment to a service provider. |
| AS |
AS indicates
codes that are assigned to a service provider. If a code with AS has no information,
except for an effective date, it has been assigned to a service provider, but the
information has not yet appeared in the LERG, and is still considered proprietary. |
| PR |
PR indicates
codes that are protected for a split; that is, these codes are assigned in the old or the
new NPA and can not be assigned in the other NPA until after the end of permissive
dialing. |
| RV |
RV indicates
codes that have been reserved by a service provider. The identity of the service provider
is considered proprietary information and will not be shown. |
| UA |
UA indicates
codes that are unavailable for assignment. These codes include, but are not limited to,
test and special use codes (e.g., 958, 959, 555, time), N11 and other unique codes (e.g.,
976, 950), codes set aside for pooling, and codes with special dialing arrangements (e.g.,
7-digit dialing cross NPA boundary). |
|
|
|
| Assigned
Date (AssignDate) |
Date the code
was assigned to the service provider by NANPA. This field is populated only for those
codes assigned from January 2001 on. |
| Initial or
Growth (Initial/Growth) |
Initial is
the first geographic NXX code assigned at a unique switching entity or point of
interconnection for a service provider. Growth is a code assigned to a switching entity or
point of interconnection subsequent to the assignment of the first code, for the same
purpose as a code that was previously assigned for a service provider to the same
switching entity or point of interconnection. |
|
|
|
|
TO ALL PARTIES UTILIZING THIS
DATA:
ACCURACY OF DATA
NANP information is provided by the major Regional Bell Operating Companies (RBOCs), and
Competitive Local Exchange Carriers (CLECs) all over North America, as well as many more
independent operating companies. Although currently Neustar is the NANP administrator, it
is up to each individual operating company to accurately report administration of their
respectively assigned numbering space. In some markets, the RBOCs use affiliates to manage
local service and code assignments.
Given the magnitude and volatility of numbering data and the fact that the data is
collected from many different sources, inaccuracies are inevitable. The following
enumerates possible inaccuracies. These examples are by no means complete.
1. Some small towns may not appear if they share a central office with a
nearby, perhaps larger city. This is commonplace.
2. A prefix in a medium to large city may have an incorrect city name.
This may be because the listed city name may actually be an old Central Office name, not
the real (or current) city name.
3. A new area code or prefix does not appear. This may be due to the
operating company not having yet reported implementation of the new prefix to the NANP
administrator. Even if it is reported, it takes time to incorporate new NPAs into the
master database at Neustar.
4. An NXX may be shown to belong to a Central Office when it actually
belongs to a neighboring CO. The operating company must provide accurate data. If they do
not, then data collection efforts will contain inaccuracies.
INTENDED USE
The accompanying data is intended to be used as an aid in cross referencing area codes and
prefixes with state and city names for INCONSEQUENTIAL use. It is NOT RECOMMENDED
that this data be used in any manner that may materially affect parties using the data or
any other party affected by parties using the data. Examples include, but are not
necessarily limited to, the following:
1. Loading the data into a PBX (or "switch") for the purpose
of affecting call routing.
2. Using the data in a basis for calculating fees for delivered
services. e.g. Toll charges.
WARRANTY
AREACODE-INFO.COM, IT'S ADMINISTRATORS, AND IT'S AGENTS, MAKE NO WARRANTY OF ANY KIND WITH
REGARD TO THIS MATERIAL (MEANING THE DOCUMENTATION, DATA, AND MEDIA), INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. AREACODE-INFO.COM, IT'S ADMINISTRATORS, AND IT'S AGENTS SHALL NOT BE LIABLE FOR
ERRORS CONTAINED WITHIN THESE MATERIALS OR FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN
CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DATA.
|