Robocall Mitigation Database: New FCC Fines and Yearly Recertification
On January 6, 2026, the Federal Register published the FCC’s order tightening the Robocall Mitigation Database, the FCC list a phone company must be on before other carriers take its calls. Voice providers, including VoIP companies, face a $10,000 base fine for false or inaccurate filings and $1,000 for late updates, starting February 5, 2026. A yearly recertification and a $100 fee come later. Businesses whose calls ride on those providers have a stake, because a carrier that loses its listing loses its outbound traffic.
What did the FCC adopt, and when does each piece start?
The FCC adopted the Report and Order in WC Docket No. 24-213 (FCC 24-135) on December 30, 2024. The order was released on January 8, 2025. Almost a year passed before the Federal Register printed a summary at 91 Fed. Reg. 343 on January 6, 2026. Most of it takes effect 30 days after that. The full order is on the FCC’s site as FCC 24-135.
The biggest change is a pair of base fines that start February 5, 2026. The order states, “we establish a base forfeiture of $10,000 for each violation for filers that submit false or inaccurate information to the Database,” according to the Federal Register text. A second base fine of $1,000 applies when a filer doesn’t update its entry within 10 business days of a change.
Each fine runs daily until the filer fixes the problem, under the Commission’s continuing-violation finding. The FCC wrote that “forfeitures shall be assessed on a daily basis up to the statutory maximum for continuing violations,” in the same Federal Register summary. A stale address that sits uncorrected for months is a daily problem, not a single one. Fix it fast.
Three other pieces don’t take effect on February 5. The order states that “Sections 1.8002(b)(2) and 64.6305(h) will not become effective until any necessary OMB review is complete,” per the published order. The $100 fee in § 1.1105 also waits on notice to Congress and system updates, and the FCC said it will publish the start dates in a later notice.
| Change | Rule | Start date in the January 6 publication |
|---|---|---|
| $10,000 base fine for false or inaccurate filings, continuing until cured | 47 C.F.R. § 1.80(b)(11) | February 5, 2026 |
| $1,000 base fine for missing the 10-business-day update window | 47 C.F.R. § 1.80(b)(11) | February 5, 2026 |
| Yearly recertification, on or before March 1 | 47 C.F.R. § 64.6305(h) | Waits on OMB review, start date to be announced |
| Update FCC registration (CORES) data within 10 business days | 47 C.F.R. § 1.8002(b)(2) | Waits on OMB review, start date to be announced |
| $100 fee for initial filings and each recertification | 47 C.F.R. § 1.1105 | Waits on notice to Congress, start date to be announced |
The recertification rule, word for word
New paragraph (h) of § 64.6305 is one sentence. It says “all providers shall certify annually, on or before March 1, that any information submitted to the Robocall Mitigation Database is true and correct,” in the rule text as published. An officer signs it under 47 C.F.R. § 1.16, the same penalty-of-perjury declaration that backs the original filing.
A missed March 1 recertification can cost a provider its listing. The order says “Failure to fulfill the annual recertification requirement will result in referral to the Enforcement Bureau, which may subject the filer to forfeiture or removal from the Database,” per the FCC’s published order. The FCC also applied its red-light rule, which holds up filings from anyone who owes the agency money. It wrote that “we will consider acceptance of filings into the Robocall Mitigation Database conditional and subject to rescission in the event a filer fails the red-light check,” in the same publication.
Why a listing matters to companies that only place calls
Carriers can’t take calls directly from an unlisted provider under 47 C.F.R. § 64.6305(g)(1), which says they “shall accept calls directly from a domestic voice service provider only if that voice service provider’s filing appears in the Robocall Mitigation Database.” The FCC put it more bluntly in the order’s summary: “Voice service providers, including terminating providers, and intermediate providers must refuse traffic sent directly from any provider that does not appear in the Robocall Mitigation Database.”
Enterprise callers inherit that risk even though the Commission’s rules don’t ask them to file. A collection agency, a health system, or a sales team on a hosted phone platform relies on its provider’s listing. If that provider is removed for a bad filing, the calls stop going through, and the caller finds out when customers stop answering. No FCC rule requires anyone to warn it first.
Every filing also describes how the provider screens its own customers. Each voice service provider’s certification must explain its mitigation steps, “including a description of how it complies with its obligation to know its customers,” under § 64.6305(d)(2)(ii). Higher fines for inaccurate filings give providers a reason to ask business customers harder questions about who they call and why. Expect more onboarding questionnaires and more audits of calling campaigns in 2026. Answer them carefully.
Under § 64.6305(d)(2)(iii), each provider’s filing commits it to answer traceback requests within 24 hours. A business that receives a carrier’s question about a batch of calls should understand how traceback requests and state attorney general inquiries unfold before it answers.
What the order leaves alone
FCC 24-135 governs what providers file, not how anyone places calls. It doesn’t change the STIR/SHAKEN call-authentication duties or the rules on what caller ID a business may send, which are covered in this guide to business caller ID and spoofing rules. Companies that rotate outbound numbers should still review local presence dialing and its caller ID risk on its own terms.
The Commission also turned down several proposals in the order. It declined to let carriers block traffic from filers with facially deficient plans who fail to fix them within 48 hours. It declined to require a PIN for each filing. And it declined, for now, to adopt automated data-validation tools. The Wireline Competition Bureau was told to build a reporting channel for deficient filings, publish guidance, and add two-factor authentication to the Database.
Consumers get no new private claim from the order, because its fines are FCC enforcement. A consumer’s TCPA claim still depends on consent, the Do Not Call rules, and the company’s own opt-out records, including whether a customer who texted STOP can opt back in. A perfectly accurate carrier filing won’t defend a single text sent without permission. Those are separate fights.
Providers worried about honest mistakes can take some comfort from the Commission’s reasoning. It agreed “inadvertent errors or minor lapses in compliance should not result in the same penalties as willful misconduct,” in the Federal Register text. That’s why the late-update fine is a tenth of the false-filing fine. Still, a $1,000 base fine assessed daily adds up fast, and a provider shouldn’t count on the FCC treating a months-old error as minor.
Steps for providers and the businesses that use them
- Preserve the records behind each filing: the certification, the mitigation plan, the officer’s signature page, and every update with its date. A business caller should keep its call logs, platform data, and consent records for the numbers it dials.
- Pull the change history. Address changes, a new robocall-mitigation contact, new business names, and STIR/SHAKEN status changes each trigger the 10-business-day update rule, so match each change to its update date. Callers should do the same with their opt-out and internal do-not-call logs.
- Pull the National Do Not Call Registry scrub records and the version dates used for recent campaigns, because a traceback or carrier audit often asks for them.
- Collect carrier and platform contracts and onboarding questionnaires, along with call scripts and any recorded or AI-voice message files. A caller’s contract should require prompt notice if its provider’s listing is challenged or removed.
- Talk to a lawyer before answering an FCC letter, a traceback request that hints at a TCPA claim, or a consumer’s demand letter.
Companies that face consumer claims alongside carrier scrutiny can find more on TCPA litigation defense, including how demand letters and class actions proceed.
If your company is defending the calls
If your company is accused of robocalls placed through a VoIP or hosted calling provider, the consent records and the provider’s call data usually decide the case. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving robocalls and calls carried by VoIP providers. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.
Sources
The order is the FCC’s Report and Order on improving the effectiveness of the Robocall Mitigation Database, WC Docket No. 24-213, FCC 24-135 (adopted Dec. 30, 2024; released Jan. 8, 2025), published at 91 Fed. Reg. 343 (Jan. 6, 2026). The Robocall Mitigation Database rule is 47 C.F.R. § 64.6305.
This post is general information about the Telephone Consumer Protection Act and related laws as of January 16, 2026. It is not legal advice, and reading it does not create an attorney-client relationship. Courts and the FCC change the rules in this area often, and the outcome of any claim depends on its facts. Past results do not guarantee future outcomes.