DISCLAIMER
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.