NANPA numbering reports
NANPA numbering reports, as installed here (file dated 2026-09-27): 205,027 codes (198,523 allocated to 2,766 holders and 6,504 reserved) and 1,398,944 thousands-blocks (1,309,908 allocated to 1,989 holders and 89,036 unassigned). Terms: no terms of use published (NANPA).
| Publisher | North American Numbering Plan Administrator (NANPA) |
|---|---|
| Published | The code and thousands-block reports are rebuilt daily and re-dated each time; the NPA report is re-dated daily. |
| Refreshed here | The codes, the thousands-blocks and the NPA report daily; the rate centre report weekly. |
| Terms | no terms of use published (NANPA) |
| Version | file dated 2026-09-27 |
| Synced here | 2026-09-21, the oldest of its tables |
| Dataset names | nanpa-co-codes, nanpa-rate-centres, nanpa-npa-report |
| Regions | United States, Puerto Rico, U.S. Virgin Islands, Guam, American Samoa, Northern Mariana Islands |
What it is
The administrator the FCC appoints for the North American plan publishes, every day, which central office codes (NPA-NXX, ten thousand numbers each) are assigned and to which carrier, and, inside the pooled codes, which blocks of a thousand are assigned, retained or free and to whom. Its rate centre report spells out the abbreviations those files use for places, and its NPA report describes every area code: where it serves, when it went into service and which codes overlay it.
What the copy installed here holds
| table | rows | allocated | unassigned | reserved | holders | version |
|---|---|---|---|---|---|---|
| Central office codes nanpa-co-codes | 205,027 codes | 198,523 | 0 | 6,504 | 2,766 | file dated 2026-09-27 |
| Thousands-blocks in pooled codes nanpa-co-codes | 1,398,944 thousands-blocks | 1,309,908 | 89,036 | 0 | 1,989 | file dated 2026-09-27 |
| Rate centre names nanpa-rate-centres | 18,452 rate centres | — | — | — | — | file dated 2026-09-20 |
| Area codes (NPA report) nanpa-npa-report | 800 area codes | — | — | — | — | file dated 2026-09-27 |
Counts only. Holders are counted, never named, and no row of the table is republished here: the publisher’s own files are linked below.
How the rows read, and what a number outside them answers
An assigned code (AS) reads as allocated to its holder; an unavailable code (UA), such as N11 or 555, as reserved. An assigned or retained thousands-block reads as allocated to its own carrier; an available block as unassigned. A contaminated available block, and one available only from a future date, is left to its code.
Complete for geographic numbers: while the copy installed here is under 45 days old, a geographic number outside every listed block answers unassigned_block.
The files
- CoCodeAssignment_Utilized_AllStates_Public.zipZIP of one tab-separated text file, headed by a “File Updated” date. Every assigned (AS) and unavailable (UA) central office code with its holder, OCN, rate centre, assignment date and pooled and in-service flags.the page that links it
- ThousandsBlockAssignment_All.zipZIP (about 12 MB) of one comma-separated file (about 112 MB). Every block of a thousand in a pooled code, with its status (assigned, retained, available), the carrier it is assigned to and its OCN.the page that links it
- NPARateCenterAllStatesReport.XLSXExcel workbook, dated by its creation time. The full name of each rate centre abbreviation, state by state.the page that links it
- npa_report.csvCSV headed by a “File Date”. One row per area code: where it serves, whether it is assigned and in service and since when, its overlay complex, NANPA’s time-zone letters and the dialling plan.the page that links it
The terms, as the publisher states them
nanpa.com publishes no terms of use and no licence for its reports: the only policy the site links is a privacy policy. The reports are posted openly by the administrator the FCC appoints. Spaw shows facts and counts read from them, credits NANPA with the file date, and does not republish the files.
terms checked 2026-09-26
What the table cannot say
- A regulator’s table records the original allocation of each block, never who serves a number today: a number ported to another carrier keeps its block.
- An allocated block says a number in it can be in service, not that it is.
- The counts are rows of the regulator’s own table, not numbers or traffic: a busy block and an empty one count once each.
- Mobiles and landlines share the same blocks in the North American plan, so the file cannot say which a number is; the holder’s name settles it only where it names a wireless carrier or a virtual-number wholesaler.
- Toll-free (8XX) and the other non-geographic codes are not in the files, so only geographic numbers outside them are answered as unassigned.
- A block its holder retained when the code was pooled carries no date.
The risk signals read from it
The other sources of a phone answer
- CNAC central office code status
- Ofcom numbering data
- ARCEP numbering resources
- ACMA numbering register
- ACM number register
- NAD number register
- Mexico’s national numbering plan
- UKE numbering tables
- MIMIT assigned numbering
- libphonenumber
- SMS-receiving number lists
- FTC Do Not Call reported calls
- Every source, and the regulators not synced
- Where each field comes from
- Look up a number
counts read from the installed tables · terms checked 2026-09-26
More free tools
All free toolsNeed this at scale?
The Spaw API runs the same lookup with batch and bulk endpoints, monitored number lists, your own suppression list and SMS outcome reporting — 10 free lookups a month, no card required.