numbering identity · stub

The FCC Reassigned Numbers Database

Verified 2026-10-14 · 59 sources · tier 1–2

Also known as Reassigned Number Database.

Stub. This topic has 59 sources and no published article. The sources below are everything recorded so far.

So far, no summary has been generated for this topic. The sources below are everything recorded so far.

See also

Related to

Sources

  1. 1
    FCC 18-177 provides for the database to be run by an independent third-party administrator chosen through competitive bidding.
    Advanced Methods to Target and Eliminate Unlawful Robocalls, Second Report and Order (FCC 18-177, CG Docket 17-59) · FCC 18-177 paragraph 33 (text rendition numbering) · Checked 2026-10-14
  2. 2
    When an agent queries on a caller's behalf, the caller, not the agent, must prove that the most recent version of the database was queried and returned an erroneous response.
  3. 3
    A caller that otherwise meets the safe harbor criteria does not need to query the database itself and may rely on a query made by a duly authorized agent.
  4. 4
    A disconnected geographic number previously assigned to a business customer must be aged for no less than 45 days and no more than 365 days before reassignment.
    47 CFR 52.15 Central office code administration · 47 CFR 52.15(f)(1)(ii) · Checked 2026-10-14
  5. 5
    A disconnected geographic number previously assigned to a residential customer must be aged for no less than 45 days and no more than 90 days before reassignment.
    47 CFR 52.15 Central office code administration · 47 CFR 52.15(f)(1)(ii) · Checked 2026-10-14
  6. 6
    Callers can automate queries through an API and through SFTP file upload, with results retrievable as described in the Caller API User Guide and email notification when results are ready.
    Reassigned Numbers Database FAQ · Caller FAQ, 'Is there automation?' and 'Will I be notified when results are ready?' · Checked 2026-10-14
  7. 7
    The database's operating costs are recovered through usage charges the Administrator collects from callers; providers recover their database creation costs through the numbering administration cost mechanism.
    Advanced Methods to Target and Eliminate Unlawful Robocalls, Second Report and Order (FCC 18-177, CG Docket 17-59) · FCC 18-177 paragraphs 46-49 (text rendition numbering) · Checked 2026-10-14
  8. 8
    A reporting carrier must keep records of the most recent date each NANP number allocated or ported to it was permanently disconnected.
    47 CFR 64.1200 Delivery restrictions (paragraphs (l) and (m)) · 47 CFR 64.1200(l)(1) · Checked 2026-10-14
  9. 9
    The Administrator may adjust the interim usage charges monthly, including tiers, query counts and prices, only with Commission approval and after posting changes on the RND website two weeks before they take effect.
  10. 12
    The database and its permitted use cover both calls and text messages.
    Advanced Methods to Target and Eliminate Unlawful Robocalls, Second Report and Order (FCC 18-177, CG Docket 17-59) · FCC 18-177 Appendix C paragraphs 27-28 (text rendition numbering) · Checked 2026-10-14
  11. 13
    DA 25-537 set October 1, 2026 as the date on which all efforts to repay providers' Reassigned Numbers Database creation-cost contributions cease.
  12. 14
    Under DA 25-537, creation-cost funds that cannot be repaid are applied first to a provider's NANP Fund debt and then, through the Database Administrator, to prior-year deficits, faster repayment of other providers, and lower future RND subscription fees.
  13. 15
    Large and medium providers submitted their first disconnect reports on April 15, 2021, and small providers began on October 15, 2021.
    Reassigned Numbers Database FAQ · Caller FAQ, 'Who populates the RND?'; Service Provider FAQ, record-keeping and seed data answer · Checked 2026-10-14
  14. 16
    The Federal Register summary of FCC 18-177 (84 FR 11226) lists an effective date of March 26, 2019, with compliance for the record-keeping, aging and reporting rules deferred until separately announced.
  15. 17
    The database became available for full use by callers on November 1, 2021, the date the interim usage charges began to apply.
  16. 18
    At launch on November 1, 2021 the interim usage charges had six subscription tiers: Extra Small, Small, Medium, Large, Extra Large and Jumbo, with the same tiers and charges for callers and caller agents.
  17. 19
    At launch, subscriptions were sold in one-, three- and six-month terms, with an annual option expected later.
  18. 20
    Reporting carriers must report to the Administrator, on the 15th day of each month, the most recent permanent disconnection date of each NANP number allocated or ported to them.
    47 CFR 64.1200 Delivery restrictions (paragraphs (l) and (m)) · 47 CFR 64.1200(l)(2) · Checked 2026-10-14
  19. 21
    The database returns no data when the queried number is not in the database and the date supplied is before January 27, 2021; a no data response is not eligible for the safe harbor.
  20. 22
    The database returns no when the number is in the database with a disconnect date before the supplied date, or when the number is not in the database and the supplied date is on or after January 27, 2021; a no response may be safe harbor eligible.
  21. 23
    Numbers are not removed from the database after reassignment; disconnect history stays so callers can test any consent date against it.
    Reassigned Numbers Database FAQ · Service Provider FAQ, 'Are reassigned numbers removed?' · Checked 2026-10-14
  22. 24
    The reassigned-number information collection is OMB control number 3060-1273, first approved by OMB on June 2, 2020.
    Advanced Methods To Target and Eliminate Unlawful Robocalls (announcement of compliance date), 85 FR 38334 · 85 FR 38334, Synopsis (OMB approval paragraph) · Checked 2026-10-14
  23. 25
    The database holds, per number, only the date of its most recent permanent disconnection; the FCC declined to include subscriber names, addresses or other subscriber information.
    Advanced Methods to Target and Eliminate Unlawful Robocalls, Second Report and Order (FCC 18-177, CG Docket 17-59) · FCC 18-177 paragraphs 24 and 37 (text rendition numbering) · Checked 2026-10-14
  24. 26
    FCC 18-177, the Second Report and Order in CG Docket 17-59 that created the database, was adopted December 12, 2018 and released December 13, 2018.
  25. 27
    47 CFR 52.15(f)(8), headed Reports of Permanently Disconnected Numbers, requires reporting carriers to report NANP number information in accordance with 47 CFR 64.1200(l).
    47 CFR 52.15 Central office code administration · 47 CFR 52.15(f)(8) · Checked 2026-10-14
  26. 28
    For reporting purposes a NANP number is permanently disconnected when the subscriber has permanently relinquished it, or the provider has permanently reversed its assignment so the number is disassociated from the subscriber.
    47 CFR 64.1200 Delivery restrictions (paragraphs (l) and (m)) · 47 CFR 64.1200(l)(3) · Checked 2026-10-14
  27. 29
    A NANP number that is ported to another provider is not a permanent disconnection and is not reported as one.
    47 CFR 64.1200 Delivery restrictions (paragraphs (l) and (m)) · 47 CFR 64.1200(l)(3), final sentence · Checked 2026-10-14
  28. 31
    A caller using an agent should be prepared to prove it authorized the agent to query the database on its behalf before the calls were made.
  29. 32
    The administrator states query limits of up to 50 numbers per event in the web GUI, up to 1,000 per API call, and up to 1 million per uploaded file, further bounded by the subscription.
    Reassigned Numbers Database FAQ · Caller FAQ, 'How many TNs can I query at once?' · Checked 2026-10-14
  30. 33
    A caller queries the database with a U.S. NANP telephone number and a date; the date can be any past date on which the caller is reasonably certain the consumer could be reached at that number.
    Advanced Methods to Target and Eliminate Unlawful Robocalls, Second Report and Order (FCC 18-177, CG Docket 17-59) · FCC 18-177 paragraph 19 (text rendition numbering) · Checked 2026-10-14
  31. 34
    Compliance with the 45-day aging rules (47 CFR 52.15(f)(1)(ii), 52.103(d)) and the disconnection record-keeping rule (64.1200(l)(1)) was required as of July 27, 2020.
  32. 35
    Regulation F's procedures for debt-collection emails and text messages to a consumer's telephone number include confirming, using a complete and accurate database, that the number has not been reassigned since the consumer's most recent consent; the regulation text does not name the FCC database.
    12 CFR 1006.6 Communications in connection with debt collection (Regulation F) · 12 CFR 1006.6(d)(5)(i)(B) and (d)(5)(ii)(B) · Checked 2026-10-14
  33. 36
    A reporting carrier is a telecommunications carrier that receives numbering resources from the NANPA, a Pooling Administrator or another telecommunications carrier.
    47 CFR 52.15 Central office code administration · 47 CFR 52.15(f)(2) · Checked 2026-10-14
  34. 37
    Compliance with the monthly reporting requirement in 47 CFR 64.1200(l)(2) was required as of March 10, 2021.
  35. 38
    The administrator FAQ states that queries can be used any time during the subscription term but unused queries do not carry over.disputed
    Reassigned Numbers Database FAQ · Caller FAQ, 'Subscription terms?' answer · Checked 2026-10-14
  36. 39
    The administrator pricing page states that once at least 75% of queries are used, a subscriber can buy a new subscription before term end and unused queries roll over.disputed
    Reassigned Numbers Database Pricing · Pricing page text on the Change Immediately renewal option · Checked 2026-10-14
  37. 40
    The caller seeking the safe harbor bears the burden of proof and persuasion on each safe harbor element.
    47 CFR 64.1200 Delivery restrictions (paragraphs (l) and (m)) · 47 CFR 64.1200(m), introductory text · Checked 2026-10-14
  38. 41
    The safe harbor applies only if the call to the reassigned number was the result of the database erroneously returning no to a query made with the consented number and the date consent was obtained.
    47 CFR 64.1200 Delivery restrictions (paragraphs (l) and (m)) · 47 CFR 64.1200(m)(2) · Checked 2026-10-14
  39. 42
    FCC 18-177 requires a caller relying on the safe harbor to have checked the most recent update of the database and declined to extend protection beyond the most recent update.
    Advanced Methods to Target and Eliminate Unlawful Robocalls, Second Report and Order (FCC 18-177, CG Docket 17-59) · FCC 18-177 paragraphs 55-56 (text rendition numbering) · Checked 2026-10-14
  40. 43
    The FCC rejected a broad safe harbor covering every call by a database user; protection is tied to reasonable reliance on a specific erroneous no response for a specific call.
    Advanced Methods to Target and Eliminate Unlawful Robocalls, Second Report and Order (FCC 18-177, CG Docket 17-59) · FCC 18-177 paragraph 54 (text rendition numbering) · Checked 2026-10-14
  41. 45
    To use the reassigned-number safe harbor, the caller must have queried the Administrator's database using the most recent numbering information reported to it and received a response of no.
    47 CFR 64.1200 Delivery restrictions (paragraphs (l) and (m)) · 47 CFR 64.1200(m)(1) · Checked 2026-10-14
  42. 46
    FCC 18-177 created a single, comprehensive database holding reassigned-number information so that a caller can check whether a number has been reassigned before calling it.
    Advanced Methods To Target and Eliminate Unlawful Robocalls (final rule), 84 FR 11226 · 84 FR 11226, Synopsis paragraphs 2 and 14 · Checked 2026-10-14
  43. 47
    Providers with 100,000 or fewer domestic retail subscriber lines (aggregated across affiliates, per their most recent Form 477) received six additional months to begin record-keeping and reporting; they were not exempted.
    Advanced Methods to Target and Eliminate Unlawful Robocalls, Second Report and Order (FCC 18-177, CG Docket 17-59) · FCC 18-177 paragraphs 43-44 (text rendition numbering) · Checked 2026-10-14
  44. 48
    SomosGov, Inc. is the Reassigned Numbers Database Administrator, a role awarded by the FCC together with the NANPA and Pooling Administrator roles in December 2020.
    Consumer and Governmental Affairs Bureau Announces Interim Usage Charges for the Reassigned Numbers Database (DA 21-1240) · DA 21-1240, footnote citing the October 1, 2021 letter from the Director of the Reassigned Numbers Database, SomosGov, Inc. · Checked 2026-10-14
  45. 49
    Providers submit the monthly incremental disconnect file from the 11th through 11:59 a.m. Eastern on the 15th, covering disconnects through at least the 10th, with later disconnects carried to the next month's file.
    Reassigned Numbers Database FAQ · Service Provider FAQ, monthly report due date and incremental answer · Checked 2026-10-14
  46. 50
    The RND terms of use provide the service as is, disclaim RNDA and FCC liability for errors and outages, and state that activity is recorded and subject to FCC audit.
    Reassigned Numbers Database Terms of Use · Terms of Use introduction and Section 8 · Checked 2026-10-14
  47. 51
    The RND terms of use limit callers to using the service solely to determine whether numbers were permanently disconnected as of a date, and prohibit marketing use and data mining or scraping.
    Reassigned Numbers Database Terms of Use · Terms of Use Sections 5 and 6 · Checked 2026-10-14
  48. 52
    In FCC 23-107 the Commission granted a 12-month waiver, extendable by the Consumer and Governmental Affairs Bureau, letting mobile wireless providers query the RND to check whether a number named in an illegal-text blocking notice was reassigned, a use outside the database's original scope.
  49. 53
    The database answers each query with one of three responses only: yes, no, or no data.
    Advanced Methods to Target and Eliminate Unlawful Robocalls, Second Report and Order (FCC 18-177, CG Docket 17-59) · FCC 18-177 paragraph 19 (text rendition numbering) · Checked 2026-10-14
  50. 54
    A disconnected toll free number must stay in disconnect (or disconnect plus transitional) status for no less than 45 days and no more than 4 months, with no extensions of the 4-month interval.
    47 CFR 52.103 Lag times (toll free number status) · 47 CFR 52.103(d) · Checked 2026-10-14
  51. 55
    Permanent disconnections of toll free numbers are reported to the database by the Toll Free Numbering Administrator, not by individual Responsible Organizations or service providers.
    Advanced Methods to Target and Eliminate Unlawful Robocalls, Second Report and Order (FCC 18-177, CG Docket 17-59) · FCC 18-177 paragraph 23 (text rendition numbering) · Checked 2026-10-14
  52. 56
    A subscriber can top off by paying 10% of its subscription charge for 10% more queries without changing the subscription term, and can upgrade mid-term to a higher tier while keeping the original term.
  53. 57
    Provider reporting is mandatory, but callers choose whether to use the database; use is not required.
    Advanced Methods to Target and Eliminate Unlawful Robocalls, Second Report and Order (FCC 18-177, CG Docket 17-59) · FCC 18-177 paragraphs 11 and 26 (text rendition numbering) · Checked 2026-10-14
  54. 58
    Database access is limited to callers that agree in writing that they and their agents will use it solely to determine whether a number has been permanently disconnected since a date, for making lawful calls or sending lawful texts.
    Advanced Methods to Target and Eliminate Unlawful Robocalls, Second Report and Order (FCC 18-177, CG Docket 17-59) · FCC 18-177 paragraph 26 and Appendix C paragraph 27 (text rendition numbering) · Checked 2026-10-14
  55. 59
    The database returns yes when the number is in the database and the supplied date is on or before its permanent disconnect date, meaning it was disconnected after consent; a yes response is not eligible for the safe harbor.

Documents

tier 1 standards and regulators

12 CFR 1006.6 Communications in connection with debt collection (Regulation F)

Office of the Federal Register / GPO (eCFR) · 2026-10-01 · accessed 2026-10-14

tier 1 standards and regulators

47 CFR 52.103 Lag times (toll free number status)

Office of the Federal Register / GPO (eCFR) · 2026-10-01 · accessed 2026-10-14

tier 1 standards and regulators

47 CFR 52.15 Central office code administration

Office of the Federal Register / GPO (eCFR) · 2026-10-01 · accessed 2026-10-14

tier 1 standards and regulators

47 CFR 64.1200 Delivery restrictions (paragraphs (l) and (m))

Office of the Federal Register / GPO (eCFR) · 2026-10-01 · accessed 2026-10-14

tier 1 standards and regulators

Advanced Methods To Target and Eliminate Unlawful Robocalls (announcement of compliance date for reporting), 86 FR 8558

Office of the Federal Register / GPO (govinfo) · 2021-02-08 · accessed 2026-10-14

tier 1 standards and regulators

Advanced Methods To Target and Eliminate Unlawful Robocalls (announcement of compliance date), 85 FR 38334

Office of the Federal Register / GPO (govinfo) · 2020-06-26 · accessed 2026-10-14

tier 1 standards and regulators

Advanced Methods To Target and Eliminate Unlawful Robocalls (final rule), 84 FR 11226

Office of the Federal Register / GPO (govinfo) · 2019-03-26 · accessed 2026-10-14

tier 1 standards and regulators

Advanced Methods to Target and Eliminate Unlawful Robocalls, Second Report and Order (FCC 18-177, CG Docket 17-59)

Federal Communications Commission · 2018-12-13 · accessed 2026-10-14

tier 1 standards and regulators

Consumer and Governmental Affairs Bureau Announces Interim Usage Charges for the Reassigned Numbers Database (DA 21-1240)

Federal Communications Commission · 2021-10-01 · accessed 2026-10-14

tier 1 standards and regulators

Consumer and Governmental Affairs Bureau Announces Interim Usage Charges for the Reassigned Numbers Database, 86 FR 61077

Office of the Federal Register / GPO (govinfo) · 2021-11-05 · accessed 2026-10-14

tier 1 standards and regulators

Consumer and Governmental Affairs Bureau Provides Additional Guidance for Users of the Reassigned Numbers Database (DA 22-378)

Federal Communications Commission · 2022-04-07 · accessed 2026-10-14

tier 1 standards and regulators

Consumer and Governmental Affairs Bureau Supplements Guidelines for Operation of the Reassigned Numbers Database (DA 21-1649)

Federal Communications Commission · 2021-12-29 · accessed 2026-10-14

tier 1 standards and regulators

Targeting and Eliminating Unlawful Text Messages; Implementation of the TCPA; Advanced Methods To Target and Eliminate Unlawful Robocalls (FCC 23-107), final rule

Office of the Federal Register / GPO (govinfo) · 2024-01-26 · accessed 2026-10-14

tier 2 current vendor documentation

Reassigned Numbers Database FAQ

Reassigned Numbers Database Administrator (SomosGov) · accessed 2026-10-14

tier 2 current vendor documentation

Reassigned Numbers Database Pricing

Reassigned Numbers Database Administrator (SomosGov) · accessed 2026-10-14

tier 2 current vendor documentation

Reassigned Numbers Database Terms of Use

Reassigned Numbers Database Administrator (SomosGov) · 2021-04-01 · accessed 2026-10-14

Cite this page

APA

WarmTransfer. (2026, October 14). The FCC Reassigned Numbers Database. WarmTransfer. https://warmtransfer.net/knowledge/reassigned-numbers-database

BibTeX

@misc{warmtransfer-reassigned-numbers-database,
  title  = {The FCC Reassigned Numbers Database},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/reassigned-numbers-database},
  note   = {Verified 2026-10-14}
}